Bug 1733116

Summary:	Operator local-storage does not exist in OperatorHub.
Product:	OpenShift Container Platform	Reporter:	Liang Xia <lxia>
Component:	Release	Assignee:	Luke Meyer <lmeyer>
Status:	CLOSED ERRATA	QA Contact:	Qin Ping <piqin>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.0	CC:	aos-bugs, aos-storage-staff, chaoyang, hekumar, jiazha, jokerman, lbednar, piqin, ppitonak, scuppett, vlaad, xtian, ycui
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:33:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Liang Xia 2019-07-25 09:06:33 UTC

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:

Comment 1 Hemant Kumar 2019-07-25 15:46:45 UTC

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.

Comment 2 Jian Zhang 2019-08-01 10:23:40 UTC

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.

Comment 3 Luke Meyer 2019-08-01 19:57:43 UTC

Right, we don't have operator metadata handled for 4.2 yet :(

Comment 4 Hemant Kumar 2019-08-13 14:40:34 UTC

*** Bug 1740504 has been marked as a duplicate of this bug. ***

Comment 5 Liang Xia 2019-08-14 02:06:12 UTC

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.

Comment 12 errata-xmlrpc 2019-10-16 06:33:28 UTC

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