-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.z, 4.19.z, 4.20.z, 4.21.z
-
None
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
- In this [documentation|
https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html-single/updating_clusters/index#migrating-clusters-to-multi-payload] , step 1 of the procedure, the command is wrong, and returns empty, even when RetreievedUpdates can be found in the clusterversion/version, and is true:
$ oc get clusterversion/version -o=jsonpath="{.status.conditions[?(.type=='RetrievedUpdates')].status}"
$ oc get clusterversion/version -o json "conditions": [ { "lastTransitionTime": "2026-02-05T10:33:02Z", "status": "True", "type": "RetrievedUpdates" },
2. oc adm upgrade in the verification step doesn't show the "working towards" line that is given in the example output
$ oc adm upgrade Cluster version is 4.18.30 Upgradeable=False Reason: AdminAckRequired Message: Kubernetes 1.32 and therefore OpenShift 4.19 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/7112216 for details and instructions. This cluster is GCP or AWS but lacks a boot image configuration. OCP will automatically opt this cluster into boot image management in 4.19. Please add a configuration to disable boot image updates if this is not desired. See https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/machine_configuration/mco-update-boot-images#mco-update-boot-images-disable_machine-configs-configure for more details. Upstream is unset, so the cluster will use an appropriate default. Channel: stable-4.18 Recommended updates: VERSION IMAGE 4.18.30 quay.io/openshift-release-dev/ocp-release@sha256:7426d9127060bd953be7f65b2b7bb2ad0b84dc366a320c789d3dbd9401864c03
3. The recommendation to use "oc adm upgrade status" is no longer correct
$ oc adm upgrade status error: unknown command "status" See 'oc adm upgrade -h' for help and examples
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Spin up a cluster in x86 on AWS
2. Follow the documentation steps
3.
Actual results:
Errors in the outputs
Expected results:
outputs suggested by the documentation should reflect the reality of what a user could get on the command line
Additional info:
