Upgrading Compute Nodes

The compute node upgrade ensures that the latest Oracle Linux kernel and user space packages are installed, as well as the appliance-specific tools and optimizations. Compute nodes must be locked and upgraded one at a time; concurrent upgrades are not supported. Before performing a compute node upgrade, ensure that you understand its key operations and their impact on system operation. Refer to the section End-to-End Compute Node Upgrade.

To upgrade one or more compute nodes outside of the full rack upgrade workflow, follow these instructions. You can either upgrade a single compute node by providing its host IP address, or all compute nodes installed in the appliance.

Upgrading a Single Compute Node

Using the Service Web UI

  1. Get the IP address of the compute node you intend to upgrade.

  2. In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.

  3. Click Upgrade & Patching to display the Upgrade Jobs page.

  4. 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.

  5. Select the appropriate upgrade request type: Upgrade Rack.

  6. 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 compute node, select Compute.

    • Qualifier: Enter the compute 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.

  7. Click Create Request.

    The new upgrade request appears in the Upgrade Jobs table.

  8. Confirm that the upgrade workflow is completed without errors.

    For more information, see Browse the Job Framework.

    After successful rediscovery, reprovisioning, and reboot, the compute node runs the updated version of the operating system and tools, and is fully operational again.

Using the Service CLI

  1. Get the IP address of the compute node you intend to upgrade.

    To obtain the host IP address and other information relevant to the upgrade procedure, use the Service CLI command provided in the following example. You can run the command as often as needed to check and confirm status as you proceed through the upgrade of all compute nodes. 

    PCA-ADMIN> list computeNode fields hostname,ipAddress,ilomIp,state,firmwareVersion,provisioningLocked,maintenanceLocked orderby hostname ASCENDING
Data:
  id                                     Hostname   Ip Address    ILOM Ip Address   State   Firmware Version           Provisioning Locked   Maintenance Locked
  --                                     --------   ----------    ---------------   -----   ----------------           -------------------   ------------------
  cf488903-fef8-4a51-8a41-c6990e4755c5   pcacn001   100.96.2.64   100.96.0.64       On      PCA Hypervisor:3.0.2-859   false                 false             
  42a7594d-1173-4dbd-4755-07810cc2d527   pcacn002   100.96.2.65   100.96.0.65       On      PCA Hypervisor:3.0.2-859   false                 false             
  bc0f37d5-ba77-423e-bc11-017704b47e59   pcacn003   100.96.2.66   100.96.0.66       On      PCA Hypervisor:3.0.2-859   false                 false             
  2e5ac527-01f5-4230-ae41-0522fcb57c9a   pcacn004   100.96.2.67   100.96.0.67       On      PCA Hypervisor:3.0.2-859   false                 false             
  5a6b61cf-7e99-4df2-87e4-b37c5fb0bfb8   pcacn005   100.96.2.68   100.96.0.68       On      PCA Hypervisor:3.0.2-859   false                 false             
  885f2aa4-f017-41e8-b2bc-e588cc0c6162   pcacn006   100.96.2.69   100.96.0.69       On      PCA Hypervisor:3.0.2-859   false                 false

  2. Enter the compute node upgrade command.

    Syntax (entered on a single line):

    upgradeRack type=ISO action=APPLY component=COMPUTE qualifier=<compute-node-ip>

    Example:

    PCA-ADMIN> upgradeRack type=ISO action=APPLY component=COMPUTE qualifier=100.96.2.66
JobId: 375371c3-1cf6-4866-9293-315e3de4966a
Data: Service request has been submitted. Upgrade Job Id = 1737619948523-compute-598228 Upgrade Request Id = UWS-ebdef142-db7a-478a-9f95-fe10714d8f44

  3. Use the job ID to check the status of the upgrade process.

    PCA-ADMIN> getUpgradeJob upgradeJobId=1737619948523-compute-598228
Data:
  Upgrade Request Id = UWS-ebdef142-db7a-478a-9f95-fe10714d8f44
  Name = compute
  Pid = 598228
  Host = pcamn01
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_compute_pcacn003_2025_01_23-08.12.28.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.66","log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":null,"request_id":"UWS-ebdef142-db7a-478a-9f95-fe10714d8f44","uln":null,"patch":"false"}
  Status = Passed
  Execution Time(sec) = 3130
[...]

  4. Ensure that the upgrade job passes the initial checks performed before the actual node upgrade starts.

    • If the Upgrader detects that the node is not in an appropriate state for upgrade, take corrective measures and run the upgrade command again.

    • If the Upgrader detects instances that cannot be migrated, shut down these instances and run the upgrade command again.

  5. Confirm that the upgrade is completed without errors.

    For more information, see Browse the Job Framework.

    After successful rediscovery, reprovisioning, and reboot, the compute node runs the updated version of the operating system and tools, and is fully operational again.

Upgrading All Compute Nodes

Using the Service Web UI

  1. In the navigation menu, go to the Maintenance section and click Upgrade Plan. This provides an overview of current and target component versions.

  2. Click Upgrade & Patching to display the Upgrade Jobs page.

  3. 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.

  4. Select the appropriate upgrade request type: Upgrade Rack.

  5. 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 installed compute nodes, select All Computes.

    • Qualifier: This parameter is not required when upgrading all compute 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.

  6. Click Create Request.

    The new upgrade request appears in the Upgrade Jobs table.

  7. Confirm that the upgrade workflow is completed without errors.

    For more information, see Browse the Job Framework.

    After successful rediscovery, reprovisioning, and reboot, the compute nodes run the updated version of the operating system and tools, and are fully operational again.

Using the Service CLI

  1. Enter the compute upgrade command.

    PCA-ADMIN> upgradeRack type=ISO action=APPLY component=ALL_COMPUTES
JobId: 60f72145-deb9-469e-8d46-b449a7da11fe
Data: Service request has been submitted. Upgrade Request Id = UWS-606c2c4e-c94e-4607-b1df-f4cbd4b0edff

  2. Use the request ID to check the status of this multi-component upgrade process.

    PCA-ADMIN> getUpgradeStatus requestId=UWS-606c2c4e-c94e-4607-b1df-f4cbd4b0edff
Data:
  Request id = UWS-606c2c4e-c94e-4607-b1df-f4cbd4b0edff
  Status = Running
  Composition ID = all_computes
  Type = ISO
  Previous Build = 3.0.2-b1300385
  Target Build = 3.0.2-b1301270
  Jobs 1 = 1737621345177-compute-860804
  Jobs 2 = 1737621353957-compute-861842
  Jobs 3 = 1737621415558-compute-868540
  Completed Components 1 = compute(100.96.2.64)
  Pending Components 1 = compute(100.96.2.65)
  Pending Components 2 = compute(100.96.2.66)

  3. Optionally, check the details of an individual compute node upgrade job.

    PCA-ADMIN> getUpgradeJobs requestId=UWS-606c2c4e-c94e-4607-b1df-f4cbd4b0edff
Data:
  id                             Upgrade Request Id                         Command Name   Result
  --                             ------------------                         ------------   ------
  1737621415558-compute-868540   UWS-606c2c4e-c94e-4607-b1df-f4cbd4b0edff   compute        None
  1737621353957-compute-861842   UWS-606c2c4e-c94e-4607-b1df-f4cbd4b0edff   compute        Passed
  1737621345177-compute-860804   UWS-606c2c4e-c94e-4607-b1df-f4cbd4b0edff   compute        Passed

PCA-ADMIN> getUpgradeJob upgradeJobId=1737621345177-compute-860804
Data:
  Upgrade Request Id = UWS-606c2c4e-c94e-4607-b1df-f4cbd4b0edff
  Composition Id = all_computes
  Name = compute
  Pid = 860804
  Host = pcamn01
  Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_compute_pcacn001_2025_01_23-08.35.45.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.64","log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":"all_computes","request_id":"UWS-606c2c4e-c94e-4607-b1df-f4cbd4b0edff","uln":null,"patch":"false"}
  Status = Passed
  Execution Time(sec) = 2976
[...]

  4. Ensure that each upgrade job passes the initial checks performed before the actual node upgrade starts.

    • If the Upgrader detects that the node is not in an appropriate state for upgrade, take corrective measures and run the upgrade command again.

    • If the Upgrader detects instances that cannot be migrated, shut down these instances and run the upgrade command again.

  5. Confirm that the entire upgrade is completed without errors. Use the getUpgradeStatus and getUpgradeJob commands.

    For more information, see Browse the Job Framework.

    After successful rediscovery, reprovisioning, and reboot, the compute nodes run the updated version of the operating system and tools, and are fully operational again.