Set Up New Software Sources for Patching
The code of the Upgrader is changed regularly, as is the case with any other system service. The setup phase of the patch preparation ensures that the Upgrader is up-to-date first, so that all patch commands are run with the latest version. Patch operations will not be allowed to run if the system detects that the Upgrader is not the latest available version.
Assuming the active software version before upgrade is at least 3.0.2-b1185392, 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 patch procedures. The package repository configuration is updated, required new container images and RPMs are installed, and access to the latest appliance software packages is enabled.
Note:
If the active software version is older than 3.0.2-b1185392, a different package setup was already completed during preconfiguration.
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 available from the ULN mirror. It determines which patch 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 Patching 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.
-
Fill out the upgrade request parameters:
-
Action: This parameter is no longer available in version 3.0.2-b1185392 and newer. Enter start to retrieve the new version of the upgrader. (To check the status of the previous preUpgrade job, enter status instead.)
-
Type: Enter ULN. The upgrader packages are picked from the appropriate mirrored ULN channel.
-
-
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.
-
Active version 3.0.2-b1185392 and newer:
PCA-ADMIN> preUpgrade type=ULN Status: Running JobId: 1714591883904-setup-25325 Data: in progress
-
Active version older than 3.0.2-b1185392:
PCA-ADMIN> preUpgrade action=start type=ULN Data: Successfully triggered the pre-upgrade task.
Upgrader operations performed with this command:
-
Configure the yum repository for the new Upgrader files.
-
Install the new Upgrader version on the management nodes, then restart the Upgrader systemd service for the changes to take effect.
Setup operations performed with this command:
-
Configure the patch repositories to enable access to the new software version sources.
-
Install the necessary container images and RPMs.
-
Generate the upgrade plan.
Note:
If the active software version is older than 3.0.2-b1185392, a different package setup was already completed during preconfiguration. The upgrade plan is always generated with version 3.0.2-b892153 and newer.
-
-
Check the status of the preUpgrade process at any time using this command:
-
Active version 3.0.2-b1185392 and newer:
PCA-ADMIN> getPreUpgradeStatus Data: status = IN-PROGRESS message = A pre-upgrade task is running! PCA-ADMIN> getPreUpgradeStatus Data: status = SUCCESS message = The previous pre-upgrade task succeeded!
-
Active version older than 3.0.2-b1185392:
PCA-ADMIN> preUpgrade action=status Data: The previous pre-upgrade task succeeded! Pre upgrade status = SUCCESS
-
-
Confirm that the latest version of the Upgrader has been installed successfully.
Active version 3.0.2-b1185392 and newer: in case the preUpgrade process fails, check the upgrade job for troubleshooting information.
PCA-ADMIN> getUpgradeJob upgradeJobId=1714591883904-setup-25325 Data: Upgrade Request Id = PREUPGRADE-7b5d6235-fdfa-4830-8824-349a5e1b9d47 Name = setup Pid = 25325 Host = pcamn02 Log File = /nfs/shared_storage/pca_upgrader/log/pca-upgrader_setup_upgrade_environment_2024_05_01-19.31.23.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-7b5d6235-fdfa-4830-8824-349a5e1b9d47","uln":null,"patch":null} Status = Failed Execution Time(sec) = 1069 Tasks 1 - Name = Configure MN Yum Repo Tasks 2 - Name = Validate Image Location Tasks 3 - Name = Validate Upgrader Version Tasks 4 - 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 Tasks 27 - Name = UpdateHistoryTask Tasks 27 - Message = Failed to update the history of upgrade Tasks 27 - Status = Failed -
Ensure that the system is in ready state. Then, proceed with the component upgrades.
-
Optionally, check which components need to be patched by displaying the upgrade plan.
PCA-ADMIN> getUpgradePlan Data: id componentType currentBuild targetBuild currentVersion targetVersion requireReboot timeEstimation requireUpgrade impactedInfra -- ------------- ------------ ----------- -------------- ------------- ------------- -------------- -------------- ------------- generic zfssa 3.0.2-b892153 3.0.2-b1052646 2013.06.05.8.57.1-2.57.5392.2 2013.06.05.8.57.1-2.57.5501.4 false 45 true host,compute 100.96.2.64 compute 3.0.2-b892153 3.0.2-b1052646 3.0.2-640 3.0.2-691 true 20 true compute 100.96.2.65 compute 3.0.2-b892153 3.0.2-b1052646 3.0.2-640 3.0.2-691 true 20 true compute 100.96.2.66 compute 3.0.2-b892153 3.0.2-b1052646 3.0.2-640 3.0.2-691 true 20 true compute 100.96.2.67 compute 3.0.2-b892153 3.0.2-b1052646 3.0.2-640 3.0.2-691 true 20 true compute 100.96.2.68 compute 3.0.2-b892153 3.0.2-b1052646 3.0.2-640 3.0.2-691 true 20 true compute 100.96.2.33 host 3.0.2-b892153 3.0.2-b1052646 oraclelinux-release-7.9-1.0.9 oraclelinux-release-7.9-1.0.9 true 35 true host 100.96.2.34 host 3.0.2-b892153 3.0.2-b1052646 oraclelinux-release-7.9-1.0.9 oraclelinux-release-7.9-1.0.9 true 35 true host 100.96.2.35 host 3.0.2-b892153 3.0.2-b1052646 oraclelinux-release-7.9-1.0.9 oraclelinux-release-7.9-1.0.9 true 35 true host generic mysql 3.0.2-b892153 3.0.2-b1052646 8.0.28-1.1 8.0.33-1.1 false 15 true host generic etcd 3.0.2-b892153 3.0.2-b1052646 3.3.10 3.3.10 false 5 false host generic vault 3.0.2-b892153 3.0.2-b1052646 v1.7.1-3 v1.7.1-3 false 5 false host generic kubernetes 3.0.2-b892153 3.0.2-b1052646 1.20.6-1 1.25.7-1 false 350 true host,compute generic platform 3.0.2-b892153 3.0.2-b1052646 None None false 50 true host,compute Oracle-Linux-7.9 ociImages 3.0.2-b892153 3.0.2-b1052646 2022.08.29_0 2023.09.26_0 false 5 true host Oracle-Linux-8 ociImages 3.0.2-b892153 3.0.2-b1052646 2022.08.29_0 2023.09.26_0 false 5 true host Oracle-Linux-9 ociImages 3.0.2-b892153 3.0.2-b1052646 None 2023.09.26_0 false 5 true host Oracle-Linux8-OKE-1.26.6 ociImages 3.0.2-b892153 3.0.2-b1052646 None 20240210 false 5 true host Oracle-Linux8-OKE-1.27.7 ociImages 3.0.2-b892153 3.0.2-b1052646 None 20240209 false 5 true host Oracle-Linux8-OKE-1.28.3 ociImages 3.0.2-b892153 3.0.2-b1052646 None 20240210 false 5 true host Oracle-Solaris-11 ociImages 3.0.2-b892153 3.0.2-b1052646 2023.04.18_0 2023.10.16_0 false 5 true host 100.96.0.33 ilom 3.0.2-b892153 3.0.2-b1052646 5.0.2.23 5.1.1.21 true 10 true host,compute 100.96.0.34 ilom 3.0.2-b892153 3.0.2-b1052646 5.0.2.23 5.1.1.21 true 10 true host,compute 100.96.0.35 ilom 3.0.2-b892153 3.0.2-b1052646 5.0.2.23 5.1.1.21 true 10 true host,compute 100.96.0.64 ilom 3.0.2-b892153 3.0.2-b1052646 5.0.2.23 5.1.2.20.a true 10 true host,compute 100.96.0.65 ilom 3.0.2-b892153 3.0.2-b1052646 5.0.2.23 5.1.1.21 true 10 true host,compute 100.96.0.66 ilom 3.0.2-b892153 3.0.2-b1052646 5.0.2.23 5.1.2.21 true 10 true host,compute 100.96.0.67 ilom 3.0.2-b892153 3.0.2-b1052646 5.0.2.23 5.1.2.20.a true 10 true host,compute 100.96.0.68 ilom 3.0.2-b892153 3.0.2-b1052646 5.0.2.23 5.1.2.21 true 10 true host,compute leaf switch 3.0.2-b892153 3.0.2-b1052646 10.2.5 10.3.4a false 60 true host,compute mgmt switch 3.0.2-b892153 3.0.2-b1052646 10.2.5 10.3.4a false 60 true host,compute spine switch 3.0.2-b892153 3.0.2-b1052646 10.2.5 10.3.4a false 60 true host,compute