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

Released operator versions are disappearing (at least in brew.registry.redhat.io/rh-osbs/iib-pub-pending:v4.xx)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Undefined
    • None
    • 4.13, 4.12, 4.14
    • cert-manager
    • Critical
    • CFE Sprint 239
    • 1
    • No
    • Proposed
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:
      I knew there was OCPBUGS-6066 before. Now cert-manager has z-stream version, thus I remember OCPBUGS-6066 in mind to have a test, found cert-manager has same issue.

      Quick info about why OCPBUGS-6066 was an issue:
      "This has a large impact on customers who are using staging environments to test operator-based products before promoting a new version to production"
      Also, https://issues.redhat.com/browse/OCPBUGS-6066?focusedId=21667672&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21667672 explains "because sometimes the latest release is buggy or there are other reasons why a customer wants to install the older version" for the question why people "reattempt to install the operator in version A needed?"

      And https://issues.redhat.com/browse/OCPBUGS-6066?focusedId=21671092&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21671092 tested brew.registry.redhat.io/rh-osbs/iib-pub-pending with different operators, some is good, some is bad. Now I tested cert-manager brew.registry.redhat.io/rh-osbs/iib-pub-pending, it is the same as the "bad" there. Detailed steps are:

      Steps to Reproduce:

      1

      $ oc create -f ~/my/imagecontentsourcepolicy.yaml

      $ oc create -f ~/my/catalogsource-brew-4.13.yaml # brew.registry.redhat.io/rh-osbs/iib-pub-pending:v4.13

      catalogsource.operators.coreos.com/rh-stage-operators-catalog created

      2

      $ oc create ns cert-manager-operator

      $ oc create -f my-operatorgroup.yaml
      operatorgroup.operators.coreos.com/cert-manager-operator-og created

      $ oc create -f my-subscription-released-1.11.1.yaml
      subscription.operators.coreos.com/openshift-cert-manager-operator created

      $ cat my-subscription-released-1.11.1.yaml

      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: openshift-cert-manager-operator
        namespace: cert-manager-operator
      spec:
        channel: stable-v1
        installPlanApproval: Manual
        name: openshift-cert-manager-operator
        source: rh-stage-operators-catalog
        sourceNamespace: openshift-marketplace
        startingCSV: cert-manager-operator.v1.11.1

      4

      $ oc get sub openshift-cert-manager-operator -n cert-manager-operator -o yaml

      ...
        - message: 'constraints not satisfiable: no operators found with name cert-manager-operator.v1.11.1
            in channel stable-v1 of package openshift-cert-manager-operator in the catalog
            referenced by subscription openshift-cert-manager-operator, subscription openshift-cert-manager-operator
            exists'
          reason: ConstraintsNotSatisfiable
          status: "True"
          type: ResolutionFailed

      This error pattern is exactly the symptom described in OCPBUGS-6066 multiple comments.

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

      4.12 4.13 4.14

      How reproducible:

      Always

      Expected results:

      I'm not sure if official redhat-operators will have the issue. But at least brew.registry.redhat.io/rh-osbs/iib-pub-pending has the issue. If redhat-operators will have, let's fix it. If redhat-operators will not have, that is our hope, but let's fix brew.registry.redhat.io/rh-osbs/iib-pub-pending as well.

      Additional info:

       

      Attachments

        Issue Links

          Activity

            People

              thn@redhat.com Thejas N (Inactive)
              xxia-1 Xingxing Xia
              Xingxing Xia Xingxing Xia
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h