Skip to content

[enterprise-4.9] OCPBUGS#9448: Add a note regarding checking the cluster version #57454

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
snarayan-redhat merged 1 commit into from
Mar 21, 2023
Merged

[enterprise-4.9] OCPBUGS#9448: Add a note regarding checking the cluster version #57454

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions modules/update-upgrading-cli.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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]
----
Expand All @@ -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:
+
Expand Down