Description of problem: On a 4.3 cluster, local storage operator is still using version 4.2 Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-02-092336 (cluster) 4.2.0-201910101614 (local storage operator) How reproducible: Always Steps to Reproduce: 1. Set up 4.3 cluster. 2. Login into web console. 3. Go to "Operators"->"OperatorHub" and select local storage. Actual results: Local storage operator is using version 4.2 Expected results: Local storage operator is using version 4.3
Tagging in Thiago as he is most up to date with OML operations.
Closing this as this is not a bug. Will be resolved once the latest version of the operator is released.
Can this be assigned to a different component then? Perhaps the local storage operator? I don't believe an operator pipeline component exists in bugzilla, but OLM and the OperatorHub are working as intended here.
The operator is updated, but still with version 4.2 4.3.0-0.nightly-2019-11-12-204120 (cluster) 4.2.5-201911080432 (local storage operator)
I'm able to get 4.3 local storage operator now. 4.3.0-0.nightly-2019-11-24-183610 (cluster) 4.3.0-201911220712 (local storage operator)
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:0062