Upgrading the Management Node Operating System

Caution:

Follow this procedure only when the appliance is running software version 3.0.2-b892153 or later. Otherwise, additional steps are required to move the primary role in the cluster between node upgrades. Follow this procedure instead: Upgrading the Management Node Operating System with Appliance Software 3.0.2-b852928 or Earlier

Caution:

Ensure that all preparation steps for system upgrade have been completed. For instructions, see Preparing the Upgrade Environment.

The Oracle Linux host operating system of the management nodes must be upgraded one node at a time; a rolling upgrade of all management nodes is not possible. This upgrade process, which involves updating the kernel and system packages, detects which of the nodes in the three-management-node cluster owns the virtual IP and the primary role. When the current primary node is upgraded, the primary role is first transferred to another node in the cluster. This configuration change occurs in the background and requires no separate or additional intervention from an administrator.

Note:

In case the ILOM also needs to be upgraded, you can integrate it into this procedure by executing the optional steps. The combined procedure eliminates the need to evacuate and reboot the same node twice.

You must upgrade management nodes one at a time, using each one's internal IP address as a command parameter. The following example uses a Service CLI command that retrieves the management node IP addresses, as well as other information relevant to the upgrade procedure.

PCA-ADMIN> list managementNode fields hostname,ipAddress,ilomIp,state,firmwareVersion orderby hostname ASCENDING
Data:
  id                                     Hostname   Ip Address    ILOM Ip Address   State   Firmware Version
  --                                     --------   ----------    ---------------   -----   ----------------
  22ae47d8-a57a-433c-988d-df62fd3548e1   pcamn01    100.96.2.33   100.96.0.33       On      5.0.2.23
  042693b6-3ddb-4fb0-914d-f3deea838c8f   pcamn02    100.96.2.34   100.96.0.34       On      5.0.2.23
  bd2563b8-e310-4fca-ba1b-0e19b8040fc6   pcamn03    100.96.2.35   100.96.0.35       On      5.0.2.23

Using the Service Web UI

In the navigation menu, click Upgrade & Patching.
Optionally, upgrade the server ILOM first.
1. In the top-right corner of the Upgrade Jobs page, click Create Upgrade or Patch. The Create Request window appears.
2. Choose Upgrade as the Request Type. Select the appropriate upgrade request type: Upgrade ILOM.
  
  Fill out the server's assigned IP address in the ILOM network. This is an IP address in the internal 100.96.0.0/23 range.
3. Click Create Request. The new upgrade request appears in the Upgrade Jobs table.
4. Wait 5 minutes to allow the ILOM upgrade job to complete. Then proceed to the host upgrade.
In the top-right corner of the Upgrade Jobs page, click Create Upgrade or Patch.

The Create Request window appears. Choose Upgrade as the Request Type.
Select the appropriate upgrade request type: Upgrade Host.
Fill out the upgrade request parameters:
- Advanced Options JSON: Optionally, add a JSON string to provide additional command parameters.
- Host IP: Enter the management node's assigned IP address in the internal administration network. This is an IP address in the internal 100.96.2.0/23 range.
- Log Level: Optionally, select a specific log level for the upgrade log file. The default log level is "Information". For maximum detail, select "Debug".
Click Create Request.

The new upgrade request appears in the Upgrade Jobs table.

Note:

After upgrade, if the upgrade plan specifies that the management nodes must be rebooted for the changes to take effect, a reboot is performed as part of the upgrade process. No administrator action is required.

If the appliance is running software version 3.0.2-b892153 or earlier, all management nodes are rebooted as part of the upgrade process.

Using the Service CLI

Get the IP address of the management node for which you intend to upgrade the host operating system.

Optionally, upgrade the server ILOM first.

Enter the ILOM upgrade command.

Syntax (entered on a single line):

upgradeIlom
hostIp=<ilom-ip>

Example:

PCA-ADMIN> upgradeIlom hostIp=100.96.0.35
Data:
  Service request has been submitted. Upgrade Job Id = 1632990827394-ilom-23871 Upgrade Request Id = UWS-1a97a8d9-9f06-478d-a0c0-d093bee4672

PCA-ADMIN> getUpgradeJob upgradeJobId=1632990827394-ilom-23871

Wait 5 minutes to allow the ILOM upgrade job to complete. Then proceed to the host upgrade.

Enter the management node host upgrade command.

Syntax (entered on a single line):

upgradeHost 
hostIp=<management-node-ip>

Example:

PCA-ADMIN> upgradeHost hostIp=100.96.2.35
Command: upgradeHost hostIp=100.96.2.35 
Status: Success
Time: 2021-09-25 05:47:02,735 UTC
Data:
  Service request has been submitted. Upgrade Job Id = 1632990827394-host-56156 Upgrade Request Id = UWS-1a97a8d9-54ef-478d-a0c0-348a17ba6755

Use the request ID and the job ID to check the status of the upgrade process.

PCA-ADMIN> getUpgradeJobs
  id                               upgradeRequestId                           commandName   result
  --                               ----------------                           -----------   ------
  1632990827394-host-56156         UWS-1a97a8d9-54ef-478d-a0c0-348a17ba6755   host          Passed

PCA-ADMIN> getUpgradeJob upgradeJobId=1632990827394-host-56156
Command: getUpgradeJob upgradeJobId=1632990827394-host-56156
Status: Success
Time: 2021-09-25 05:54:28,054 UTC
Data:
  Upgrade Request Id = UWS-1a97a8d9-54ef-478d-a0c0-348a17ba6755
  Composition Id = 1
  Name = host
  Start Time = 2021-09-25T05:47:02
  End Time = 2021-09-25T05:48:38
  Pid = 56156
  Host = pcamn02
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_host_os_2021_09_25-05.47.02.log
  Arguments = {"verify_only":false,"upgrade":false,"diagnostics":false,"host_ip":"100.96.2.35","result_override":null,"log_level":null,"switch_type":null,"precheck_status":false,"task_time":0,"fail_halt":false,"fail_upgrade":null,"component_names":null,"upgrade_to":null,"image_location":"http://host.example.com/pca-3.0.1-b535176.iso","epld_image_location":null,"expected_iso_checksum":null,"checksum":"240420cfb9478f6fd026f0a5fa0e998e086275fc45e207fb5631e2e99732e192e8e9d1b4c7f29026f0a5f58dadc4d792d0cfb0279962838e95a0f0a5fa31dca7","composition_id":"1","request_id":"UWS-1a97a8d9-54ef-478d-a0c0-348a17ba6755","display_task_plan":false,"dry_run_tasks":false}
  Status = Passed
  Execution Time(sec) = 96
  Tasks 1 - Name = Validate Image Location
  Tasks 1 - Description = Verify that the image exists at the specified location and is correctly named
  Tasks 1 - Time = 2021-09-25T05:47:02
  Tasks 2 - Name = Validate Image Location
[...]

When the first management node host operating system upgrade has completed successfully, execute the same command for the second management node. When that upgrade has completed successfully, execute the same command for the third management node.
```
PCA-ADMIN> upgradeHost hostIp=100.96.2.33
PCA-ADMIN> upgradeHost hostIp=100.96.2.34
```
When all three operating system upgrades have completed successfully, the management node cluster is up-to-date.

Note:

After upgrade, if the upgrade plan specifies that the management nodes must be rebooted for the changes to take effect, a reboot is performed as part of the upgrade process. No administrator action is required.

If the appliance is running software version 3.0.2-b892153 or earlier, all management nodes are rebooted as part of the upgrade process.