Hide Forgot
Description of problem: After bundle containers are built, they go through a round of validation. This is failing for some, and stage pushes are not allowed until they pass. Also of course we can't ship them. This bug is to support upstream PRs where needed to fix this. It can be considered done when all bundles are rebuilt and pass the tests.
*** Bug 1883951 has been marked as a duplicate of this bug. ***
I am verifying this fix on Cluster version 4.6.0-0.nightly-2020-10-03-051134, still seeing old logging csv $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-10-03-051134 True False 63m Cluster version is 4.6.0-0.nightly-2020-10-03-051134 $ oc get csv NAME DISPLAY VERSION REPLACES PHASE clusterlogging.4.6.0-202009240527.p0 Cluster Logging 4.6.0-202009240527.p0 Succeeded elasticsearch-operator.4.6.0-202009232303.p0 Elasticsearch Operator 4.6.0-202009232303.p0 Succeeded
@Luke I have followed the steps mentioned in the doc https://docs.engineering.redhat.com/display/MULTIARCH/How+To+Test+Red+Hat+ART+Operators and created the CatalogSource as below: apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: redhat-operators-art-stage namespace: openshift-marketplace spec: sourceType: grpc publisher: redhat displayName: Red Hat Operators v4.6 Stage image: brew.registry.redhat.io/rh-osbs/iib-pub-pending:v4.6 I still see old csv's: oc get csv NAME DISPLAY VERSION REPLACES PHASE clusterlogging.4.6.0-202009240527.p0 Cluster Logging 4.6.0-202009240527.p0 Succeeded elasticsearch-operator.4.6.0-202009232303.p0 Elasticsearch Operator 4.6.0-202009232303.p0 Succeeded I have also tried with image: registry-proxy.engineering.redhat.com/rh-osbs/iib-pub-pending:v4.6
@Luke Meyer Below are the operators I got after successfully performed all the steps from the doc https://docs.engineering.redhat.com/display/MULTIARCH/How+To+Test+Red+Hat+ART+Operators oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-10-07-022140 True False 90m Cluster version is 4.6.0-0.nightly-2020-10-07-022140 oc get csv NAME DISPLAY VERSION REPLACES PHASE clusterlogging.4.6.0-202010010620.p0 Cluster Logging 4.6.0-202010010620.p0 Succeeded elasticsearch-operator.4.6.0-202010010929.p0 Elasticsearch Operator 4.6.0-202010010929.p0 Succeeded CatalogSource spec: spec: displayName: My Operator Catalog image: registry-proxy.engineering.redhat.com/rh-osbs/iib-pub-pending:v4.6 publisher: grpc sourceType: grpc
Having successfully pushed VPA-operator to stage once, tests began failing, revealing that the CSV name replacement that was supposed to happen to give it a unique name for each build - wasn't matching. So it gets the same name every time which fails the test. https://github.com/openshift/vertical-pod-autoscaler-operator/pull/38 should make the match work. This is required to ship VPA-operator.
Verified this bug, able to get the latest builds for logging operators.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196