Description of problem (please be detailed as possible and provide log snippests): I see the default channel is pointing to stable-4.3 so our automation deploy 4.2 with 4.3 build at the moment. End of the packageManifest: name: Red Hat, Inc version: 4.3.0-369.ci name: stable-4.3 defaultChannel: stable-4.2 packageName: ocs-operator provider: name: Red Hat Version of all relevant components (if applicable): OCS: 4.3.0-369.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Yes Can this issue reproduce from the UI? Haven't tried If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Add catalog source for 4.3 2. Subscribe to the OCS with the default channel taken from packageManifest 3. Actual results: Default channel is stable-4.2 instead of stable-4.3 Expected results: Default channel for 4.3 should be stable-4.3 Additional info:
Assigning to Boris, as discussed.
This should be fixed in latest 4.3 build (see fixed in field). I have found a way to get the latest supported stable version from the manifests dir and updated the automation to do that when building the ocs-olm-operator container.
Since this is already verified, it should be ACK-ed for the release...
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, 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:1437