Upgrading the Management Node Operating System
The management nodes operate in a cluster, distributing the load of requests, services, and many different types of operations across the three nodes. While the host OS of a management node is upgraded, the operation of the cluster is affected: the node is temporarily unavailable, the cluster configuration might be changed, core appliance functions (database, platform and infrastructure services) are reduced in availability and performance, and so on. The Upgrader ensures that the management cluster remains operational during an upgrade, using the orchestration logic of its workflow service.
To upgrade the Oracle Linux host OS of the management nodes outside of the full rack upgrade workflow, follow these instructions. You can either upgrade the host OS of a single management node by providing its host IP address, or all three management nodes in a single workflow.
Upgrading the OS of a Single Management Node
- Using the Service Web UI
-
-
Get the IP address of the management node for which you intend to upgrade the host OS.
-
In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.
-
Click Upgrade & Patching to display the Upgrade Jobs page.
-
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 Rack.
-
Fill out the upgrade request parameters:
-
Action: To perform the upgrade or patch operation, select Apply.
-
Type: For upgrade, select ISO. The ULN option applies to patching.
-
Component: For a single management node, select Host.
-
Qualifier: 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.
-
Verify Only: Enable this option to run the operation in verification only mode.
-
Force: Enable this option to force the operation. Use only when instructed by Oracle.
-
-
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.
-
Confirm that the upgrade process is completed without errors.
For more information, see Browse the Job Framework.
After successful OS installation, reboot, and cluster reconstruction, the management node returns to normal operation. All three management nodes must run the same versions of host OS, services, and tools to ensure optimal cluster operation.
-
- Using the Service CLI
-
-
Get the IP address of the management node for which you intend to upgrade the host OS.
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
-
Enter the host OS upgrade command.
Syntax (entered on a single line):
upgradeRack type=ISO action=APPLY component=HOST qualifier=<management-node-ip>
Example:
PCA-ADMIN> upgradeRack type=ISO action=APPLY component=HOST qualifier=100.96.2.35 JobId: f2b6e533-a0a5-4423-9a49-1cb21ed0eb9e Data: Service request has been submitted. Upgrade Job Id = 1737620045150-host-616754 Upgrade Request Id = UWS-9e03c924-628b-4584-a77d-75ae71bf8b8b
-
Use the job ID to check the status of the upgrade process.
PCA-ADMIN> getUpgradeJob upgradeJobId=1737620045150-host-616754 Data: Upgrade Request Id = UWS-9e03c924-628b-4584-a77d-75ae71bf8b8b Name = host Pid = 616754 Host = pcamn01 Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_host_os_pcamn03_2025_01_23-08.14.05.log Arguments = {"component_names":null,"diagnostics":false,"display_task_plan":false,"dry_run_tasks":false,"expected_iso_checksum":null,"fail_halt":false,"fail_upgrade":null,"image_location":null,"online_upgrade":null,"precheck_status":false,"repo_config_override":null,"result_override":null,"task_time":0,"test_run":false,"upgrade":false,"upgrade_to":null,"user_uln_base_url":null,"verify_only":false,"host_ip":"100.96.2.35","log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":null,"request_id":"UWS-9e03c924-628b-4584-a77d-75ae71bf8b8b","uln":null,"patch":"false"} Status = Passed Execution Time(sec) = 1736 [...]
-
Confirm that the upgrade process is completed without errors.
For more information, see Browse the Job Framework.
After successful OS installation, reboot, and cluster reconstruction, the management node returns to normal operation. All three management nodes must run the same versions of host OS, services, and tools to ensure optimal cluster operation.
-
Upgrading the OS of All Management Nodes
- Using the Service Web UI
-
-
In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.
-
Click Upgrade & Patching to display the Upgrade Jobs page.
-
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 Rack.
-
Fill out the upgrade request parameters:
-
Action: To perform the upgrade or patch operation, select Apply.
-
Type: For upgrade, select ISO. The ULN option applies to patching.
-
Component: For all three management nodes, select All Hosts.
-
Qualifier: This parameter is not required when upgrading the OS of all management nodes.
-
Verify Only: Enable this option to run the operation in verification only mode.
-
Force: Enable this option to force the operation. Use only when instructed by Oracle.
-
-
Click Create Request.
The new upgrade request appears in the Upgrade Jobs table.
-
Confirm that the upgrade workflow is completed without errors.
For more information, see Browse the Job Framework.
After successful OS installation and reboot of all three management nodes, the management cluster is fully restored and returns to normal operation.
-
- Using the Service CLI
-
-
Enter the host upgrade command.
PCA-ADMIN> upgradeRack type=ISO action=APPLY component=ALL_HOSTS JobId: 2792a532-7190-4919-9bc1-8c64f30126d8 Data: Service request has been submitted. Upgrade Request Id = UWS-a5403cc7-90c8-4224-9e05-06f132561522
-
Use the request ID to check the status of this multi-component upgrade process.
PCA-ADMIN> getUpgradeStatus requestId=UWS-a5403cc7-90c8-4224-9e05-06f132561522 Data: Request id = UWS-a5403cc7-90c8-4224-9e05-06f132561522 Status = Passed Composition ID = all_hosts Type = ISO Previous Build = 3.0.2-b1300385 Target Build = 3.0.2-b1301270 Jobs 1 = 1737622450559-host-1066058 Jobs 2 = 1737622464489-host-1069024 Jobs 3 = 1737622527066-host-1080160 Completed Components 1 = host(100.96.2.33) Pending Components 2 = host(100.96.2.34) Pending Components 3 = host(100.96.2.35)
-
Optionally, check the details of an individual management node upgrade job.
PCA-ADMIN> getUpgradeJobs requestId=UWS-a5403cc7-90c8-4224-9e05-06f132561522 Data: id Upgrade Request Id Command Name Result -- ------------------ ------------ ------ 1737622527066-host-1080160 UWS-a5403cc7-90c8-4224-9e05-06f132561522 host None 1737622464489-host-1069024 UWS-a5403cc7-90c8-4224-9e05-06f132561522 host Passed 1737622450559-host-1066058 UWS-a5403cc7-90c8-4224-9e05-06f132561522 host Passed PCA-ADMIN> getUpgradeJob upgradeJobId=1737622450559-host-1066058 Data: Upgrade Request Id = UWS-a5403cc7-90c8-4224-9e05-06f132561522 Composition Id = all_hosts Name = host Pid = 1066058 Host = pcamn02 Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_host_os_pcamn01_2025_01_23-08.54.24.log Arguments = {"component_names":null,"diagnostics":false,"display_task_plan":false,"dry_run_tasks":false,"expected_iso_checksum":null,"fail_halt":false,"fail_upgrade":null,"image_location":null,"online_upgrade":null,"precheck_status":false,"repo_config_override":null,"result_override":null,"task_time":0,"test_run":false,"upgrade":false,"upgrade_to":null,"user_uln_base_url":null,"verify_only":false,"host_ip":"100.96.2.33","log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":"all_hosts","request_id":"UWS-a5403cc7-90c8-4224-9e05-06f132561522","uln":null,"patch":"false"} Status = Passed Execution Time(sec) = 1750 [...]
-
Confirm that the entire upgrade is completed without errors. Use the
getUpgradeStatus
andgetUpgradeJob
commands.For more information, see Browse the Job Framework.
After successful OS installation and reboot of all three management nodes, the management cluster is fully restored and returns to normal operation.
-