4 Checking Upgrade Plan Status and Progress
Note:
This function is available when the appliance is running software version 3.0.2-b892153 or later.
During the execution of the pre-upgrade command, an upgrade plan is also generated. The plan is based on a comparison of the currently installed components on the rack, and the target component versions and latest packages downloaded to shared storage during the preparation of the upgrade environment. The resulting upgrade plan shows for which components a patching procedure needs to be executed in the next phase.
All components except firmware must be patched in a prescribed order. The upgrade plan will prevent a component patch procedure from starting if the preceding patch operations have not been completed. An error message informs the administrator which components need to be patched first.
Note:
In general, firmware may be patched whenever new versions are made available for your system. Firmware patches can be applied in no particular order and independently of other components.
However, there is an extra requirement: when patching to appliance software version 3.0.2-b1081557 or later, the ZFS Storage Appliance firmware must be patched before all other components.
This is the order of operations enforced through the upgrade plan:
-
Prepare upgrade environment (Upgrade PreConfig)
-
Upgrade the Upgrader (PreUpgrade)
-
ZFS Storage Appliance firmware (version 3.0.2-b1081557 or later)
-
Compute nodes
-
Host operating system of management nodes
-
MySQL cluster database
-
Secret service (including Etcd and Vault)
-
Kubernetes container orchestration packages (platform layer)
-
Containerized microservices
-
Oracle Cloud Infrastructure images
Once the patching environment has been prepared, all patch operations required to bring the system up-to-date are listed in the upgrade plan. Whenever a patch procedure has been completed successfully, the upgrade plan is updated with the latest status: for patched components the source and target versions are identical and the "upgrade required" flag is disabled.
At any point in time you can check how far the system has progressed through the upgrade plan. It indicates which components are already up-to-date and which still require patching.
The upgrade plan can be viewed in two ways:
-
In the Service Web UI, go to Maintenance in the navigation menu and select Upgrade Plan.
-
In the Service CLI, enter the following command:
PCA-ADMIN> getUpgradePlan Data: id component currentBuild targetBuild currentVersion targetVersion requireReboot timeEstimation (min) requireUpgrade impactedInfra -- --------- ------------ ----------- -------------- ------------- ------------- -------------------- -------------- ------------- generic zfssa 3.0.2-b1053709 3.0.2-b1053709 2013.06.05.8.57.1-2.57.5501.4 2013.06.05.8.57.1-2.57.5501.4 false 45 false host,compute 100.96.2.64 compute 3.0.2-b1053709 3.0.2-b1053709 3.0.2-691 3.0.2-691 false 20 false compute 100.96.2.65 compute 3.0.2-b1053709 3.0.2-b1053709 3.0.2-691 3.0.2-691 false 20 false compute 100.96.2.66 compute 3.0.2-b1053709 3.0.2-b1053709 3.0.2-691 3.0.2-691 false 20 false compute 100.96.2.67 compute 3.0.2-b1053709 3.0.2-b1053709 3.0.2-691 3.0.2-691 false 20 false compute 100.96.2.68 compute 3.0.2-b1053709 3.0.2-b1053709 3.0.2-691 3.0.2-691 false 20 false compute 100.96.2.33 host 3.0.2-b1053709 3.0.2-b1053709 oraclelinux-release-7.9-1.0.9 oraclelinux-release-7.9-1.0.9 false 35 false host 100.96.2.34 host 3.0.2-b1053709 3.0.2-b1053709 oraclelinux-release-7.9-1.0.9 oraclelinux-release-7.9-1.0.9 false 35 false host 100.96.2.35 host 3.0.2-b1053709 3.0.2-b1053709 oraclelinux-release-7.9-1.0.9 oraclelinux-release-7.9-1.0.9 false 35 false host generic mysql 3.0.2-b1053709 3.0.2-b1053709 8.0.33-1.1 8.0.33-1.1 false 15 false host generic etcd 3.0.2-b1053709 3.0.2-b1053709 3.3.10 3.3.10 false 5 false host generic vault 3.0.2-b1053709 3.0.2-b1053709 v1.7.1-3 v1.7.1-3 false 5 false host generic kubernetes 3.0.2-b1053709 3.0.2-b1053709 1.25.7-1 1.25.7-1 false 80 false host,compute generic platform 3.0.2-b1053709 3.0.2-b1053709 None None false 50 false host,compute Oracle-Linux-7.9 ociImages 3.0.2-b1053709 3.0.2-b1053709 2023.09.26_0 2023.09.26_0 false 5 false host Oracle-Linux-8 ociImages 3.0.2-b1053709 3.0.2-b1053709 2023.09.26_0 2023.09.26_0 false 5 false host Oracle-Linux-9 ociImages 3.0.2-b1053709 3.0.2-b1053709 2023.09.26_0 2023.09.26_0 false 5 false host Oracle-Linux8-OKE-1.26.6 ociImages 3.0.2-b1053709 3.0.2-b1053709 20240210 20240210 false 5 false host Oracle-Linux8-OKE-1.27.7 ociImages 3.0.2-b1053709 3.0.2-b1053709 20240209 20240209 false 5 false host Oracle-Linux8-OKE-1.28.3 ociImages 3.0.2-b1053709 3.0.2-b1053709 20240210 20240210 false 5 false host Oracle-Solaris-11 ociImages 3.0.2-b1053709 3.0.2-b1053709 2023.10.16_0 2023.10.16_0 false 5 false host 100.96.0.33 ilom 3.0.2-b1053709 3.0.2-b1053709 5.1.1.21 5.1.1.21 false 10 false host,compute 100.96.0.34 ilom 3.0.2-b1053709 3.0.2-b1053709 5.1.1.21 5.1.1.21 false 10 false host,compute 100.96.0.35 ilom 3.0.2-b1053709 3.0.2-b1053709 5.1.1.21 5.1.1.21 false 10 false host,compute 100.96.0.64 ilom 3.0.2-b1053709 3.0.2-b1053709 5.1.2.20.a 5.1.2.20.a false 10 false host,compute 100.96.0.65 ilom 3.0.2-b1053709 3.0.2-b1053709 5.1.1.21 5.1.1.21 false 10 false host,compute 100.96.0.66 ilom 3.0.2-b1053709 3.0.2-b1053709 5.1.1.21 5.1.1.21 false 10 false host,compute 100.96.0.67 ilom 3.0.2-b1053709 3.0.2-b1053709 5.1.2.20.a 5.1.2.20.a false 10 false host,compute 100.96.0.68 ilom 3.0.2-b1053709 3.0.2-b1053709 5.1.1.21 5.1.1.21 false 10 false host,compute leaf switch 3.0.2-b926028 3.0.2-b1053709 10.2.3 10.3.4a false 60 true host,compute mgmt switch 3.0.2-b926028 3.0.2-b1053709 10.2.3 10.3.4a false 60 true host,compute spine switch 3.0.2-b926028 3.0.2-b1053709 10.2.3 10.3.4a false 60 true host,compute