Skip to content

Commit fb0d246

Browse files
committed
OCPBUGS#9448: Add a note regarding checking clusterversion
1 parent d4e32c4 commit fb0d246

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

modules/update-upgrading-cli.adoc

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ updated to the new version:
107107
+
108108
[source,terminal]
109109
----
110-
$ oc adm upgrade
110+
$ oc get clusterversion
111111
----
112112
+
113113
.Example output
@@ -122,6 +122,15 @@ Channel: stable-4.10 (available channels: candidate-4.10, candidate-4.11, eus-4.
122122
No updates available. You may force an upgrade to a specific release image, but doing so might not be supported and might result in downtime or data loss.
123123
----
124124
+
125+
[NOTE]
126+
====
127+
If the `oc get clusterversion` command displays the following error while the `PROGRESSING` status is `True`, you can ignore the error.
128+
[source,terminal]
129+
----
130+
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
131+
version 4.10.26 True True 24m Unable to apply 4.11.0-rc.7: an unknown error has occurred: MultipleErrors
132+
----
133+
====
125134
. If you are upgrading your cluster to the next minor version, such as version X.y to X.(y+1), it is recommended to confirm that your nodes are upgraded before deploying workloads that rely on a new feature:
126135
+
127136
[source,terminal]

0 commit comments

Comments
 (0)