Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-60265

Add mechanism to delete MCN v1alpha1 CRD in 4.16+ clusters

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • Critical
    • None
    • None
    • None
    • MCO Sprint 275
    • 1
    • In Progress
    • Bug Fix
    • Hide
      Before this update, an upgrade to a version prior to 4.15 or a new install of 4.15 deployed `MachineConfigNode`Custom Resource Definitions (CRDs) despite being in techpreview. As a result, clusters failed to upgrade due to unneeded CRDs. With this release, techpreview `MachineConfigNode` CRDs were removed from default clusters ensuring smooth upgrades. (link:https://issues.redhat.com/browse/OCPBUGS-60265[OCPBUGS-60265])
      Show
      Before this update, an upgrade to a version prior to 4.15 or a new install of 4.15 deployed `MachineConfigNode`Custom Resource Definitions (CRDs) despite being in techpreview. As a result, clusters failed to upgrade due to unneeded CRDs. With this release, techpreview `MachineConfigNode` CRDs were removed from default clusters ensuring smooth upgrades. (link: https://issues.redhat.com/browse/OCPBUGS-60265 [ OCPBUGS-60265 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-59723. The following is the description of the original issue:
      —
      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:

      • See debugging Slack thread here.
      • MCO-712 may outline a pattern for completing this work.

              djoshy David Joshy
              rh-ee-ijanssen Isabella Janssen
              None
              None
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: