-
Bug
-
Resolution: Done-Errata
-
Major
-
4.16.0, 4.17.0
-
Important
-
No
-
0.5
-
OTA 253, OTA 254
-
2
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-33898. The following is the description of the original issue:
—
The mockup output does not contain the version the cluster is being upgraded to. Existing CVO condition shows it, so we should find a place for it in the output (or explicitly decide we dont want it)
Definition of Done:
oc adm upgrade status tells that cluster is upgrading from x'.y'.z' (to partial intermediate version...) to x.y.z version.
For example, with a history like:
- Completed 4.15.0
- Partial 4.15.2
- Partial 4.15.3
- Completed 4.15.5
we might show something that mentioned 4.15.0, 4.15.2, 4.15.3, and 4.15.5. Or we could decide that those mid-update retargets are rare enough to not be worth spending code-time on, and only mention 4.15.0 and 4.15.5?
- clones
-
OCPBUGS-33898 status: include information about version currently upgraded to
- Closed
- is blocked by
-
OCPBUGS-33898 status: include information about version currently upgraded to
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update