Step E: Upgrade nodes - AWS Elemental Conductor File

Step E: Upgrade nodes

Perform these steps on each node in the cluster, after you've removed all the nodes from the cluster. Before you start, make sure that you've performed the steps in Step B: Prepare each AWS Elemental Conductor File node for migration.

  1. Set the boot mode on the node to UEFI.

  2. Perform a kickstart to upgrade the operating system to RHEL 9.

  3. From the Linux command line, log in to the node. Use the elemental user credentials.

  4. Check routing table by running the following command in the command line:

    ip r show

    The system returns something similar to the following:

    default via 10.x.x.x dev eth0 proto dhcp src 10.x.x.x metric 103
10.x.x.x/x dev eth1 proto kernel scope link src 10.12.107.43 metric 102
...

    To proceed with the upgrade, your management interface must be listed for the first route. To find which network interface is your system's management interface, see: Note the network adapter for the management interface.

  5. If your management interface isn't listed for the first route, you must update the default route.

  6. Run the installer. Use the appropriate command:

    • For GPU versions of the software (for Conductor File only):

      [elemental@hostname ~]$ sudo sh ./elemental_production_server_2.18.n.nnnn.run --skip-all --start --xeula

    • For CPU-only versions of the software:

      [elemental@hostname ~]$ sudo sh ./elemental_production_server_cpu_2.18.n.nnnn.run --skip-all --start --xeula

    Where:

    --skip-all skips all the prompts. There is no need to view prompts about configuration because when you restore the database to the node, all the configuration data is copied over and overwrites any configuration data already on the node.

    --start restarts the software after installation.

    --xeula skips the display of the license agreement. There is no need to view this prompt because you have previously accepted the agreement.

  7. When the installation is complete, restart the node:

    [elemental@hostname ~] sudo reboot