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

Add mechanism to delete MCN v1alpha1 CRD in 4.16+ clusters

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • Critical
    • None
    • None
    • MCO Sprint 274, MCO Sprint 275
    • 2
    • Done
    • Bug Fix
    • Hide
      Because the Machine Config Node feature, which was introduced in 4.16, when updating from a {product-title} a version prior to 4.15, the Machine Config Node CRDs were added as Technology Preview. This caused the update to fail. With this fix, the update no longer deploy the Technology Preview CRDs, ensuring a successful upgrade. (link:https://issues.redhat.com/browse/OCPBUGS-59723[OCPBUGS-59723])
      Show
      Because the Machine Config Node feature, which was introduced in 4.16, when updating from a {product-title} a version prior to 4.15, the Machine Config Node CRDs were added as Technology Preview. This caused the update to fail. With this fix, the update no longer deploy the Technology Preview CRDs, ensuring a successful upgrade. (link: https://issues.redhat.com/browse/OCPBUGS-59723 [ OCPBUGS-59723 ])
    • 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:

      • 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:
              8 Start watching this issue

                Created:
                Updated: