Bug 2005843 - [DR] odfmo-controller-manager pod label should be set based on Deployment name
Summary: [DR] odfmo-controller-manager pod label should be set based on Deployment name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ODF 4.9.0
Assignee: gowtham
QA Contact: Sidhant Agrawal
URL:
Whiteboard:
Depends On:
Blocks: 2010188
TreeView+ depends on / blocked
 
Reported: 2021-09-20 10:23 UTC by Pratik Surve
Modified: 2023-08-09 17:00 UTC (History)
8 users (show)

Fixed In Version: v4.9.0-158.ci
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-13 17:46:30 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-multicluster-orchestrator pull 43 0 None open Bug 2005843: Label ODF multicluster operator pod based on deployment name 2021-09-21 18:56:28 UTC
Github red-hat-storage odf-multicluster-orchestrator pull 44 0 None Merged Bug 2005843: Label ODF multicluster operator pod based on deployment name 2021-09-23 08:59:52 UTC
Red Hat Product Errata RHSA-2021:5086 0 None None None 2021-12-13 17:46:50 UTC

Description Pratik Surve 2021-09-20 10:23:41 UTC
Description of problem (please be detailed as possible and provide log
snippests):
[DR] odfmo-controller-manager pod label should be set based on pod name 

Version of all relevant components (if applicable):

odf-operator.v4.9.0-138.ci

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)?
1

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. Deploy DR on 2 Cluster
2. check multicluster operator pod label on hub cluster
3.


Actual results:
oc get pods -n openshift-operators --show-labels
NAME                                        READY   STATUS    RESTARTS        AGE     LABELS
odfmo-controller-manager-7b647fc74d-8jp2q   1/1     Running   1 (3d23h ago)   5d19h   control-plane=controller-manager,pod-template-hash=7b647fc74d


Expected results:
pod label should have pod name or deployment name 

Additional info:

Comment 10 errata-xmlrpc 2021-12-13 17:46:30 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 (Moderate: Red Hat OpenShift Data Foundation 4.9.0 enhancement, security, and bug fix 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-2021:5086


Note You need to log in before you can comment on or make changes to this bug.