Bug 1848146 - [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.6.0
Assignee: Mike Fedosin
QA Contact: Wei Duan
URL:
Whiteboard:
Depends On:
Blocks: 1848203
TreeView+ depends on / blocked
 
Reported: 2020-06-17 19:05 UTC by Mike Fedosin
Modified: 2020-10-27 16:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1848203 (view as bug list)
Environment:
Last Closed: 2020-10-27 16:07:36 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 37 0 None closed Bug 1848146: Rename operator package to manila-csi-driver-operator 2020-11-29 10:03:33 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:07:56 UTC

Description Mike Fedosin 2020-06-17 19:05:26 UTC 
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:43:35 UTC 
Operator has been renamed to manila-csi-driver-operator.
Comment 5 errata-xmlrpc 2020-10-27 16:07:36 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 (OpenShift Container Platform 4.6 GA Images), 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:4196
Note You need to log in before you can comment on or make changes to this bug.