Bug 1839984

Summary:	[manila-csi-driver-operator] Release the operator through appregistry
Product:	OpenShift Container Platform	Reporter:	Qin Ping <piqin>
Component:	Storage	Assignee:	Mike Fedosin <mfedosin>
Status:	CLOSED ERRATA	QA Contact:	Wei Duan <wduan>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.5	CC:	aos-bugs, jhou, jsafrane
Target Milestone:	---
Target Release:	4.5.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:	2020-07-15 10:17:52 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:
Bug Depends On:
Bug Blocks:	1834160, 1835654, 1837210

Description Qin Ping 2020-05-26 07:32:16 UTC

Create this bug to track if manila csi operator appregistry is ready.

Comment 3 Wei Duan 2020-06-11 08:51:49 UTC

Verified fail.

When using the registryNamespace: rh-osbs-operators to create catalogsource and deploying the operator:
 
[wduan@MINT OCP]$ oc get csv csi-driver-manila-operator.v4.5.0 -o yaml | grep image
image: registry.redhat.io/openshift4/ose-csi-driver-manila-rhel7-operator@sha256:4dbd69aba5adf45477a1bc84f61573a9e01cc4359fdabc6229190dfa7ad9ae0f:latest

1. operator image digest is the not same as in errata https://errata.devel.redhat.com/advisory/54130.
2. ":latest" should be removed I think.

Comment 5 Wei Duan 2020-06-17 13:16:06 UTC

Verified pass with image in https://errata.devel.redhat.com/advisory/54130

[wduan@MINT manila]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2020-06-16-045437   True        False         10h     Cluster version is 4.5.0-0.nightly-2020-06-16-045437

After creating operatorsource with registryNamespace: rh-osbs-operators, we can deploy the operator.

Comment 7 errata-xmlrpc 2020-07-15 10:17:52 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/RHEA-2020:2925