-
Bug
-
Resolution: Unresolved
-
Critical
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
3
-
Critical
-
None
-
Done
-
Bug Fix
-
-
None
-
None
-
None
-
None
Description of problem:
As described in OCPBUGS-59722, in Openshift versions prior to 4.15, the MCO deployed MCN CRDs even though the feature was in techpreview. To safeguard against clusters failing to upgrade to a version where MCN is GAed, we should add a mechnaism to delete the faulty v1alpha1 CRDs.
Version-Release number of selected component (if applicable):
Fix needs to be between 4.16 and 4.18.
How reproducible:
Always.
Steps to Reproduce:
Upgrade or launch any default <=4.15 cluster and the v1alpha1 MCN CRDs will exist.
Actual results:
We should not have CRDs in a cluster where they are unneeded.
Expected results:
v1alpha1 MCN CRD should not exist in default clusters when the the feature is not GA (currently 4.19 and prior, but it will GA in 4.19 as tracked in MCO-1720.
Additional info:
- blocks
-
OCPBUGS-60265 Add mechanism to delete MCN v1alpha1 CRD in 4.16+ clusters
-
- Closed
-
- is cloned by
-
OCPBUGS-60265 Add mechanism to delete MCN v1alpha1 CRD in 4.16+ clusters
-
- Closed
-
- is incorporated by
-
OCPBUGS-59567 [4.14-4.20]/[4.15-4.20] upgrade stuck at crd machineconfignodes.machineconfiguration.openshift.io
-
- Closed
-
- links to