Set Up New Software Sources for Upgrade
The code of the Upgrader is changed regularly, as is the case with any other system service. The setup phase of the upgrade preparation ensures that the Upgrader is up-to-date first, so that all upgrade commands are run with the latest version. Upgrade operations will not be allowed to run if the system detects that the Upgrader is not the latest available version.
When the latest version of the Upgrader is up and running, the sources of the new appliance software are set up for use in the system upgrade procedures. The current software image is backed up, and the new software ISOs are unpacked on the management cluster shared storage in the appropriate directory structure: OS base image, appliance software RPM packages, new compute instance images, new firmware, and so on.
At the end of the setup phase, an upgrade plan is generated. The upgrade plan is based on a comparison between the current installation and the new version that was unpacked. It determines which upgrade procedures need to be performed in the next phase. For more information, see Check Upgrade Plan Status and Progress.
This entire setup process is launched by an appliance administrator with a single command.
Caution:
Ensure that the preconfiguration process has been completed first. See Preconfigure the Upgrade Environment.
To prevent inconsistencies while executing the upgrade plan later on, it is critical that
both commands in the preparation process, upgradePreConfig
(preconfiguration) and preUpgrade (setup), are completed together in the
specified order. If at any time you need to rerun the preUpgrade command,
you must rerun the preceding command first.
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: preUpgrade.
-
For the upgrade request type, enter ISO. The required files are retrieved from the unpacked ISO images.
-
Click Create Request.
The new upgrade request appears in the Upgrade Jobs table. When the job has completed successfully, the Upgrader is up-to-date and the new software version sources are ready for use.
Using the Service CLI
-
Start the installation of the latest Upgrader version, and setup of the new appliance software sources.
PCA-ADMIN> preUpgrade type=ISO Status: Running JobId: aa33246e-fd79-460f-a191-cc97f8be04be Data: in progress
Upgrader operations performed with this command:
-
Install the new Upgrader version on the management nodes, then restart the Upgrader systemd service for the changes to take effect.
-
Update the Service CLI and Service Web UI to make the latest commands and functions available.
Setup operations performed with this command:
-
Back up the current software image.
-
Unpack the ISO images, store new software RPMs and installation files (images, firmware) in correct directories.
-
Remove obsolete backups and images from the appliance internal shared storage.
-
Generate the upgrade plan.
-
-
Check the status of the preUpgrade process at any time using this command:
PCA-ADMIN> getPreUpgradeStatus Data: status = IN-PROGRESS message = PREUPGRADE-c0f0b38d-64d2-42bb-8d96-de39d1218b24: A pre-upgrade task is running! PCA-ADMIN> getPreUpgradeStatus Data: status = SUCCESS message = The previous pre-upgrade task succeeded!
-
Confirm that the latest version of the Upgrader has been installed successfully.
PCA-ADMIN> getUpgradeJobs Data: id Upgrade Request Id Command Name Result -- ------------------ ------------ ------ 1737484792498-setup-42073 PREUPGRADE-44ec9a80-b3b5-4029-bd77-8178d62173a8 setup Passed 1737483518274-prepare-28393 UWS-e37208d4-d433-4e16-8140-de38c0757c9d prepare Passed
In case the preUpgrade process fails, check the upgrade job for troubleshooting information.
PCA-ADMIN> getUpgradeJob upgradeJobId=1737484792498-setup-42073 Data: Upgrade Request Id = PREUPGRADE-44ec9a80-b3b5-4029-bd77-8178d62173a8 Name = setup Pid = 25325 Host = pcamn02 Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_setup_upgrade_environment_2025_01_21-18.39.52.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":null,"log_level":null,"switch_type":null,"epld_image_location":null,"checksum":null,"composition_id":null,"request_id":"PREUPGRADE-44ec9a80-b3b5-4029-bd77-8178d62173a8","uln":null,"patch":null} Status = Failed Execution Time(sec) = 1069 Tasks 1 - Name = Validate Setup Image Location Tasks 2 - Name = Validate Upgrader Version Tasks 3 - Name = Validate Upgrade Order [...] Tasks 22 - Name = Delete Old backups Tasks 22 - Message = [Errno 2] No such file or directory: '/nfs/shared_storage/yum/pca_upgrader' Tasks 22 - Status = Failed -
Ensure that the system is in ready state. Then, proceed with the rack upgrade workflow.
-
Check which components need to be upgraded by displaying the upgrade plan. Verify that the target build number matches the appliance software version you are planning to upgrade to.
PCA-ADMIN> getUpgradePlan Data: id component currentBuild targetBuild currentVersion targetVersion requireReboot timeEstimation (min) requireUpgrade impactedInfra -- --------- ------------ ----------- -------------- ------------- ------------- -------------------- -------------- ------------- generic zfssa 3.0.2-b1300385 3.0.2-b1300385 2013.06.05.8.73.1-2.73.5701.1 2013.06.05.8.73.1-2.73.5701.1 false 45 false host,compute 100.96.2.64 compute 3.0.2-b1300130 3.0.2-b1300385 oraclelinux-release-7.9-1.0.9 3.0.202.3.11.0.0.0.5.7ea3f4ccbf3e17fc... true 50 true compute 100.96.2.65 compute 3.0.2-b1300130 3.0.2-b1300385 oraclelinux-release-7.9-1.0.9 3.0.202.3.11.0.0.0.5.7ea3f4ccbf3e17fc... true 50 true compute 100.96.2.66 compute 3.0.2-b1300130 3.0.2-b1300385 oraclelinux-release-7.9-1.0.9 3.0.202.3.11.0.0.0.5.7ea3f4ccbf3e17fc... true 50 true compute 100.96.2.33 host 3.0.2-b1300130 3.0.2-b1300385 oraclelinux-release-7.9-1.0.13 3.0.202.3.11.0.0.0.5.7ea3f4ccbf3e17fc... true 40 true host 100.96.2.34 host 3.0.2-b1300130 3.0.2-b1300385 oraclelinux-release-7.9-1.0.13 3.0.202.3.11.0.0.0.5.7ea3f4ccbf3e17fc... true 40 true host 100.96.2.35 host 3.0.2-b1300130 3.0.2-b1300385 oraclelinux-release-7.9-1.0.13 3.0.202.3.11.0.0.0.5.7ea3f4ccbf3e17fc... true 40 true host generic mysql 3.0.2-b1300385 3.0.2-b1300385 8.0.36-1.1 8.0.36-1.1 false 15 false host generic etcd 3.0.2-b1300385 3.0.2-b1300385 3.5.6 3.5.6 false 5 false host generic vault 3.0.2-b1300385 3.0.2-b1300385 v1.7.1-3.10.0.0.0.4.g5f2d5af v1.7.1-3.10.0.0.0.4.g5f2d5af false 5 false host generic kubernetes 3.0.2-b1300385 3.0.2-b1300385 1.25.16-2 1.25.16-2 false 60 false host,compute generic platform 3.0.2-b1300130 3.0.2-b1300385 None None false 40 true host,compute Oracle-Linux-7.9 ociImages 3.0.2-b1300130 3.0.2-b1300385 None 2024.07.31_0 false 5 true host Oracle-Linux8-OKE-1.28.8 ociImages 3.0.2-b1300130 3.0.2-b1300385 None 20241201 false 5 true host Oracle-Solaris-11 ociImages 3.0.2-b1300130 3.0.2-b1300385 None 2024.08.26_0 false 5 true host Oracle-Linux8-OKE-1.27.12 ociImages 3.0.2-b1300130 3.0.2-b1300385 None 20241201 false 5 true host Oracle-Linux8-OKE-1.26.15 ociImages 3.0.2-b1300130 3.0.2-b1300385 None 20241201 false 5 true host Oracle-Linux-9 ociImages 3.0.2-b1300130 3.0.2-b1300385 None 2024.07.31_0 false 5 true host Oracle-Linux-8 ociImages 3.0.2-b1300130 3.0.2-b1300385 None 2024.07.31_0 false 5 true host 100.96.0.33 ilom 3.0.2-b1300130 3.0.2-b1300385 5.1.4.20 5.1.4.25 true 10 true host,compute 100.96.0.34 ilom 3.0.2-b1300130 3.0.2-b1300385 5.1.4.20 5.1.4.25 true 10 true host,compute 100.96.0.35 ilom 3.0.2-b1300130 3.0.2-b1300385 5.1.4.20 5.1.4.25 true 10 true host,compute 100.96.0.64 ilom 3.0.2-b1300130 3.0.2-b1300385 5.1.4.20 5.1.4.25 true 10 true host,compute 100.96.0.65 ilom 3.0.2-b1300130 3.0.2-b1300385 5.1.4.20 5.1.4.25 true 10 true host,compute 100.96.0.66 ilom 3.0.2-b1300130 3.0.2-b1300385 5.1.4.20 5.1.4.25 true 10 true host,compute leaf switch 3.0.2-b1300385 3.0.2-b1300385 10.3.4a 10.3.4a false 60 false host,compute spine switch 3.0.2-b1300385 3.0.2-b1300385 10.3.4a 10.3.4a false 60 false host,compute mgmt switch 3.0.2-b1300385 3.0.2-b1300385 10.3.4a 10.3.4a false 60 false host,compute