Description of problem: Operator local-storage does not exist in OperatorHub. Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-07-21-222447 How reproducible: Always Steps to Reproduce: 1. Set up 4.2 cluster. 2. Login into web console as kubeadmin and check OperatorHub. Actual results: Operator local-storage does not exist in OperatorHub. Expected results: Operator local-storage exist in OperatorHub and can be installed. Additional info:
I believe storage team has done all that was needed to be done to make the operator available in the OperatorHub. From my conversation with Luke - I gathered that they haven't yet started pushing new operators into 4.2 builds yet. I am going to move this BZ over to them since there is nothing that needs to be done from storage side.
Hi, Hemant Thanks for your report! Per comment 1, move on it to ART team since it's not an OLM bug. Correct me if I'm wrong.
Right, we don't have operator metadata handled for 4.2 yet :(
*** Bug 1740504 has been marked as a duplicate of this bug. ***
This is blocking partial of local volume testing. E.g, as stated in https://bugzilla.redhat.com/show_bug.cgi?id=1740504, if there are issues in the images, we may not have enough time to fix/rebuild/test the new images.
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-2019:2922