Bug 1848203 - [manila-csi-driver-operator] csi-driver-manila-operator should be renamed to manila-csi-driver-operator
Summary: [manila-csi-driver-operator] csi-driver-manila-operator should be renamed to ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.0
Assignee: Mike Fedosin
QA Contact: Wei Duan
URL:
Whiteboard:
Depends On: 1848146
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-17 23:13 UTC by Mike Fedosin
Modified: 2020-07-13 17:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1848146
Environment:
Last Closed: 2020-07-13 17:44:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift csi-driver-manila-operator pull 39 0 None closed Bug 1848203: Rename operator package to manila-csi-driver-operator 2020-11-29 10:03:53 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:44:40 UTC

Description Mike Fedosin 2020-06-17 23:13:34 UTC 
+++ This bug was initially created as a clone of Bug #1848146 +++

Currently the operator package is called csi-driver-manila-operator. This creates some problems...
First, this name is taken by a community operator, second, it doesn't comply with red hat's naming conventions.

The package should be called manila-csi-driver-operator.
Comment 3 Wei Duan 2020-06-19 03:33:49 UTC 
Operator has been renamed to manila-csi-driver-operator.
Comment 4 errata-xmlrpc 2020-07-13 17:44:18 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-2020:2409
Note You need to log in before you can comment on or make changes to this bug.