-
Bug
-
Resolution: Done
-
Major
-
0.2.0
-
None
-
None
-
3
-
False
-
-
False
-
-
-
MON Sprint 252
-
Important
-
No
When triggering CVP tests for COO 0.2.0,
operator-accidental-unpublishing-of-released-operators-bundle-image tests fails when trying to validate the replaces with the following
===== Test: operator-accidental-unpublishing-of-released-operators-bundle-image ===== Red Hat Operators should not be accidentally unpublishing released operator versions when shipping a new operator version. What this test does: * Parses the value of 'skipRange' and 'replaces' values if present in the operator CSV file. * Checks if 'skipRange' is used without 'replaces'. If it is, then checks if this is the first bundle in a new channel This test will pass with SUCCESS if: * 'skipRange' is used with 'replaces' OR * 'skipRange' is used without 'replaces' but the bundle is the first one in a new channel OR * 'skipRange' is used without 'replaces' but all the bundles in the targeted channels are listed in 'skips' OR * no 'skipRange' is used [INVALID] [cluster-observability-operator.0.1.1, cluster-observability-operator.0.1.2] are missing from spec.skips for channel development in the v4.12 index and "spec.replaces" is not used either. The bundle will prune existing upgrade graph in the channel "development". [INVALID] [cluster-observability-operator.0.1.1, cluster-observability-operator.0.1.2] are missing from spec.skips for channel development in the v4.13 index and "spec.replaces" is not used either. The bundle will prune existing upgrade graph in the channel "development". [INVALID] [cluster-observability-operator.0.1.1, cluster-observability-operator.0.1.2] are missing from spec.skips for channel development in the v4.14 index and "spec.replaces" is not used either. The bundle will prune existing upgrade graph in the channel "development". [INVALID] [cluster-observability-operator.0.1.1, cluster-observability-operator.0.1.2] are missing from spec.skips for channel development in the v4.15 index and "spec.replaces" is not used either. The bundle will prune existing upgrade graph in the channel "development". [TEST RESULT] The bundle will prune the existing upgrade graph of the operator. The test operator-accidental-unpublishing-of-released-operators-bundle-image FAILED ------------------- Execution Reference: -> /cvp/cvp-redhat-operator-bundle-image-validation-test/cluster-observability-operator-bundle-container-0.2.0-4/cf9a7b92-f3ac-49e2-a10d-4471bb3682b0/
This looks to me related to https://gitlab.cee.redhat.com/coo-midstream/cluster-observability-operator-cpaas/-/blob/cluster-observability-operator-0.2-rhel-8/distgit/containers/cluster-observability-operator-bundle/render_vars.in?ref_type=heads#L8 and may just be a quick fix of bumping that, but I'm wondering if this took into consideration 0.1.Z + 0.2.Z streams.
- links to
-
RHEA-2024:129305 Cluster Observability Operator 0.2.0 for OpenShift
- mentioned on