Patching the Management Node Operating System with Appliance Software 3.0.2-b852928 or Earlier

Caution:

Ensure that all preparation steps for system patching have been completed. For instructions, see Prepare for Patching.

The Oracle Linux host operating system of the management nodes must be patched one node at a time; a rolling patch of all management nodes is not possible. This patching process, which involves updating the kernel and system packages, must always be initiated from the management node that holds the cluster virtual IP. Thus, in a three-management-node cluster, when you have patched two management nodes, you must reassign the cluster virtual IP to one of the patched management nodes and execute the final patch command from that node. Each management node must be rebooted after a patch is applied.

You must patch management nodes one at a time, using each one's internal IP address as a command parameter. To obtain the host IP addresses, use the Service CLI command show ManagementNode name=<pcamn01> and look for the Ip Address in the output.

You cannot complete all of the patching tasks required in the Service Web UI for this component. Use the Service CLI to patch the management nodes.

Using the Service CLI

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

Run the Service CLI from the management node that holds the management cluster virtual IP.

Log on to one of the management nodes and check the status of the cluster.

# ssh root@pcamn01
# pcs status
Cluster name: mncluster
Stack: corosync
Current DC: pcamn02 (version 1.1.23-1.0.1.el7-9acf116022) - partition with quorum

Online: [ pcamn01 pcamn02 pcamn03 ]

Full list of resources:

 scsi_fencing         (stonith:fence_scsi):          Stopped (disabled)
 Resource Group: mgmt-rg
     vip-mgmt-int     (ocf::heartbeat:IPaddr2):      Started    pcamn02
     vip-mgmt-host    (ocf::heartbeat:IPaddr2):      Started    pcamn02
     vip-mgmt-ilom    (ocf::heartbeat:IPaddr2):      Started    pcamn02
     vip-mgmt-lb      (ocf::heartbeat:IPaddr2):      Started    pcamn02
     vip-mgmt-ext     (ocf::heartbeat:IPaddr2):      Started    pcamn02
     l1api            (systemd:l1api):               Started    pcamn02
     haproxy          (ocf::heartbeat:haproxy):      Started    pcamn02
     pca-node-state   (systemd:pca_node_state):      Started    pcamn02
     dhcp             (ocf::heartbeat:dhcpd):        Started    pcamn02
     hw-monitor       (systemd:hw_monitor):          Started    pcamn02

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled

In this example, the command output indicates that the node with host name pcamn02 currently holds the cluster virtual IP.

Enter the patch command.

Choose one of the management nodes that is not currently hosting the virtual IP. In the prior example, pcamn02 holds the cluster virtual IP, so choose either pcamn01 or pcamn03 as your patch target.

Syntax (entered on a single line):

patchHost
hostIp=<management-node-ip>

Example:

PCA-ADMIN> patchHost hostIp=100.96.2.33
Command: patchHost hostIp=100.96.2.33
Status: Success
Time: 2022-01-01 21:06:56.849 UTC
Data: Service request has been submitted.  Upgrade Job ID = 1632990827394-host-56156 \
Upgrade Request ID = UWS-1a97a8d9-54ef-478d-a0c0-348a17ba6755

Use the job ID to check the status of the patch process. The job ID is listed in the output of the patch command.
```
PCA-ADMIN> getUpgradeJob upgradeJobId=1632990827394-host-56156
```
At the end of the patching process, the management node is rebooted automatically. Wait approximately 5 minutes until the management node restarts.
When the first management node host operating system patch has completed successfully, execute the same command for the next management node.
```
PCA-ADMIN> patchHost hostIp=100.96.2.35
```
At the end of the patching process, the management node is rebooted automatically. Wait approximately 5 minutes until the management node restarts.

When the second management node host operating system patch has completed successfully, move the cluster virtual IP to one of the upgraded management nodes.

# ssh root@pcamn01
root@pcamn01's password:
Last login: Mon Jan 10 20:50:28 2022
# pcs resource move mgmt-rg pcamn01
# pcs status
Cluster name: mncluster
Stack: corosync
[...]
 scsi_fencing   (stonith:fence_scsi):   Stopped (disabled)
 Resource Group: mgmt-rg
     vip-mgmt-int       (ocf::heartbeat:IPaddr2):       Started pcamn01
     vip-mgmt-host      (ocf::heartbeat:IPaddr2):       Started pcamn01
[...]

Moving the cluster virtual IP to another management node should only take a number of seconds and will close your current connection.

Log in to the management node virtual IP and launch the Service CLI to execute the host operating system patch for the final management node.
```
# ssh -l admin 100.96.2.32 -p 30006
PCA-ADMIN> patchHost hostIp=100.96.2.34
```
At the end of the patching process, the management node is rebooted automatically. Wait approximately 5 minutes until the management node restarts.

When this patch has completed successfully, the operating system on all management nodes is up-to-date.