-
Epic
-
Resolution: Unresolved
-
Undefined
-
ACM 2.11.0, ACM 2.12.0, ACM 2.13.0
-
None
-
[Tech debt] How to manage OpenShift version when the installation/upagding attempt fails
-
False
-
None
-
False
-
Not Selected
-
To Do
OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
The initial installation or previous upgrade attempt of an OpenShift cluster may fail. See the status of the ClusterVersion resource below for an example.
history: - completionTime: null image: quay.io/openshift-release-dev/ocp-release:4.15.10-multi-x86_64 startedTime: "2024-06-04T07:50:26Z" state: Partial verified: false version: 4.15.10 observedGeneration: 1
It is unclear how to determine the OpenShift version in such situations. Currently, the logic is to disregard incomplete installation or upgrade attempts, which could result in a missing or incorrect OpenShift version for a cluster that has not been fully installed/upgraded.
Related bug: https://issues.redhat.com/browse/ACM-12011
Why is this important?
...
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.
