-
Bug
-
Resolution: Done
-
Minor
-
None
-
4.13, 4.12, 4.11, 4.10, 4.14
-
Low
-
None
-
3
-
OSDOCS Sprint 243
-
1
-
Unspecified
-
N/A
-
Release Note Not Required
Section Number and Name:
Updating a cluster by using the CLI
Describe the issue:
The output of oc adm upgrade and oc get clusterversion -o json|jq ".items[0].status.history" is not proper.
Suggestions for improvement:
1) With 4.10 oc client, the output of oc adm upgrade is like:
- oc adm upgrade
Cluster version is 4.9.23
Upstream is unset, so the cluster will use an appropriate default.
Channel: stable-4.10
Recommended updates:
VERSION IMAGE
4.10.0 quay.io/openshift-release-dev/ocp-release@sha256:9c5f0df8b192a0d7b46cd5f6a4da2289c155fd5302dec7954f8f06c878160b8b
2) The example output of oc get clusterversion -o json|jq ".items[0].status.history" needs update. The version 4.8.13 should be replaced with 4.9.23
[
,
{ "completionTime": "2021-01-28T20:30:50Z", "image": "quay.io/openshift-release-dev/ocp-release@sha256:b8fa13e09d869089fc5957c32b02b7d3792a0b6f36693432acc0409615ab23b7", "startedTime": "2021-01-28T17:38:10Z", "state": "Completed", "verified": false, "version": "4.8.13" }]
Additional information: