Bug 2047173

Summary:	[RFE] Change controller-manager pod name in odf-lvm-operator to more relevant name to lvm
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Shay Rozen <srozen>
Component:	lvm-operator	Assignee:	Nitin Goyal <nigoyal>
Status:	CLOSED ERRATA	QA Contact:	Shay Rozen <srozen>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	etamir, jolmomar, lgangava, mmuench, muagarwa, nberry, ocs-bugs, odf-bz-bot, sapillai
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	ODF 4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.11.0-66	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-24 13:48:26 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 Shay Rozen 2022-01-27 10:53:42 UTC

Description of problem (please be detailed as possible and provide log
snippests):
Lvm operator has a pod name controller manager in namespace openshift-storage. I recommend to change it to a more relevant name like odf-lvm-controller-manager like we use in ODF pods (rook-ceph-osd etc)


Version of all relevant components (if applicable):
All

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 3 Mudit Agarwal 2022-02-14 15:50:56 UTC

Acking for 4.11

Comment 4 Nitin Goyal 2022-03-11 11:26:05 UTC

Moving it to modified as PR is merged in main and we do not have a separate branch for 4.11

Comment 7 Shay Rozen 2022-05-23 08:59:38 UTC

Verified on quay.io/rhceph-dev/ocs-registry:4.11.0-67

Comment 10 errata-xmlrpc 2022-08-24 13:48:26 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 (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix update), 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/RHSA-2022:6156