Bug 1769768 - RelatedObjects in clusteroperator monitoring references non-existent monitoring resource
Summary: RelatedObjects in clusteroperator monitoring references non-existent monitori...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.3.0
Assignee: Frederic Branczyk
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-07 12:23 UTC by Maciej Szulik
Modified: 2020-01-23 11:11 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:11:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 553 0 'None' 'closed' 'Bug 1741685: pkg/client: add more relatedObjects to improve data from must-gather' 2019-11-25 07:46:34 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:11:49 UTC

Description Maciej Szulik 2019-11-07 12:23:08 UTC
This line:

https://github.com/openshift/cluster-monitoring-operator/blob/e515ed03618466b6a1b9d2fcf12192191bfd90f8/pkg/client/status_reporter.go#L46

is adding non-existing resource to related objects, please revise the related objects and upadate per what you might need when debugging your operator. 

The value of relatedObjects are input for oc adm must-gather and oc adm inspect commands. 

See https://github.com/openshift/cluster-kube-controller-manager-operator/blob/a74352c81f9c60f25bd4450a929475052fa70c65/pkg/operator/starter.go#L113-L119 as an example what kcm-o is setting in relatedobjects.

Comment 5 errata-xmlrpc 2020-01-23 11:11:28 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:0062


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