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

Using Boxcutter, two clusterextensionrevisions are generated for existing ClusterExtension

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          Before open Boxcutter, install ClusterExtension. Then enable TP, and open Boxcutter feature gate, two clusterextensionrevisions are generated for the existing ClusterExtension 

      Version-Release number of selected component (if applicable):

          4.21.0-0.nightly-2025-10-07-171402

      How reproducible:

          always

      Steps to Reproduce:

       1. install some clusterextension
      xzha@xzha1-mac ocp-84929 % oc get clusterextension                 
      NAME                INSTALLED BUNDLE         VERSION   INSTALLED   PROGRESSING   AGE
      extension-80117     nginx80117.v1.0.1        1.0.1     True        True          39m
      extension-84930     nginx84930.v1.0.0        1.0.0     True        True          3h38m
      extension-logging   cluster-logging.v6.2.5   6.2.5     True        True          3h41m
      
      
          2. enable TP, and open Boxcutter feature gate
      2.1 create ClusterRoleBinding
      xzha@xzha1-mac boxcutter % cat rb 
      apiVersion: rbac.authorization.k8s.io/v1
      kind: ClusterRoleBinding
      metadata:
        name: operator-controller-boxcutter-cluster-admin
      roleRef:
        apiGroup: rbac.authorization.k8s.io
        kind: ClusterRole
        name: cluster-admin
      subjects:
        - kind: ServiceAccount
          name: operator-controller-controller-manager
          namespace: openshift-operator-controller
      
      2.2 enable TP
      2.3 modify deployment operator-controller-controller-manager, add --feature-gates=BoxcutterRuntime=true 
      
      oc patch
      clusterversion version --type=merge -p '{"spec":
      {"overrides":[{"kind": "Deployment",
      "name": "cluster-olm-operator", "namespace":
      "openshift-cluster-olm-operator", "unmanaged": true,
      "group": "apps"}]}}' 
      
      
      oc delete
      deploy/cluster-olm-operator -n openshift-cluster-olm-operator 
      
      
      oc edit deployment
      -n openshift-operator-controller operator-controller-controller-manager 
      
        
      3. check clusterextensionrevision
      xzha@xzha1-mac boxcutter % oc get clusterextensionrevision
      NAME                  AGE
      extension-80117-1     14m
      extension-80117-2     14m
      extension-84930-1     14m
      extension-84930-2     14m
      extension-logging-1   14m
      extension-logging-2   14m      
      
       

      Actual results:

      two clusterextensionrevisions are generated 

      Expected results:

      only one clusterextensionrevisions

      Additional info:

      If those two clusterextensionrevisions are deleted, only one will be generated automatically
      
      xzha@xzha1-mac boxcutter % oc delete clusterextensionrevision extension-84930-1 extension-84930-2 
      clusterextensionrevision.olm.operatorframework.io "extension-84930-1" deleted
      clusterextensionrevision.olm.operatorframework.io "extension-84930-2" deleted
      xzha@xzha1-mac boxcutter % oc get clusterextensionrevision                                       
      NAME                  AGE
      extension-84930-1     3s
      
          

              rh-ee-cchantse Catherine Chan-Tse
              rhn-support-xzha Xia Zhao
              None
              None
              Xia Zhao Xia Zhao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: