Step D: Upgrade Node B - AWS Elemental Delta

This is version 2.3 of the AWS Elemental Delta documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Delta Documentation.

Step D: Upgrade Node B

The node must be in a working state prior to upgrade. If the node is in a degraded state (for example, the web interface isn't responding), the upgrade fails.

If you're not using a health checker, remove the reference to node B from the load balancer prior to upgrade. For assistance, see product documentation specific to the load balancer.

Perform these steps at the hardware unit for node B.

  1. From a Linux prompt, log in with the elemental user credentials. Once you're logged in, the initial directory is /home/elemental.

  2. Run the installer with the skip-all option:

    [elemental@hostname ~]$ sudo sh ./elemental_production_delta_<version>.run –-skip-all

    The installer automatically stops the software, if it's still running. The following prompts are skipped:

    • You are not prompted to change the network setup (eth0 and eth1) or the Ethernet partitioning (setup of eth0 as a management interface).

    • You are not prompted to choose the time zone.

    • You are not prompted to enable or disable user authentication.

    You are prompted to accept the EULA (end user license agreement).

    The new software is installed and all services except elemental_se are automatically restarted.

  3. Once installation is complete, you might be prompted to reboot:

    Installation and configuration complete! . . . NOTE: You must reboot your system to finish the installation!

    Do not reboot yet. Instead, switch to node A, as described below.

    Warning

    You must not reboot node B yet because doing so would cause node B to become a Leader (along with node A), which would cause serious conflicts.

  4. If you're not prompted to reboot, you are prompted to start elemental_se:

    Would you like to start the Elemental service now? [Y]

    Do not respond to this prompt! Instead, switch to node A, as described below.

    Warning

    You must not restart node B yet because doing so would cause node B to become a leader (along with node A), which would cause serious conflicts.