From 3e6e2e5edb8631558a51b6ff8768ad93c92c5f68 Mon Sep 17 00:00:00 2001 From: Servesha Dudhgaonkar Date: Tue, 21 Mar 2023 07:56:34 +0530 Subject: [PATCH] OCPBUGS#9448: Add a note regarding checking the cluster version --- modules/update-upgrading-cli.adoc | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/modules/update-upgrading-cli.adoc b/modules/update-upgrading-cli.adoc index 75ae7d77ba09..660780915c92 100644 --- a/modules/update-upgrading-cli.adoc +++ b/modules/update-upgrading-cli.adoc @@ -155,8 +155,7 @@ date, where the newest update is first in the list. Updates in the history have state `Completed` if the rollout completed and `Partial` if the update failed or did not complete. -. After the update completes, you can confirm that the cluster version has -updated to the new version: +. After the update completes, you can confirm that the cluster version has updated to the new version: + [source,terminal] ---- @@ -169,6 +168,16 @@ $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0 True False 2m Cluster version is 4.9.0 ---- ++ +[NOTE] +==== +If the `oc get clusterversion` command displays the following error while the `PROGRESSING` status is `True`, you can ignore the error. +[source,terminal] +---- +NAME VERSION AVAILABLE PROGRESSING SINCE STATUS +version 4.10.26 True True 24m Unable to apply 4.11.0-rc.7: an unknown error has occurred: MultipleErrors +---- +==== . If you are upgrading your cluster to the next minor version, like version 4.y to 4.(y+1), it is recommended to confirm your nodes are updated before deploying workloads that rely on a new feature: +