Bug 2044481 - collect sharedresource cluster scoped instances with must-gather
Summary: collect sharedresource cluster scoped instances with must-gather
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: Gabe Montero
QA Contact: Jitendar Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-24 17:01 UTC by Gabe Montero
Modified: 2022-03-10 16:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:42:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-storage-operator pull 257 0 None open Bug 2044481: add relatedObjects to ClusterOperator def in manifest to collect sharedresource CRD instances when availabl... 2022-01-24 17:06:38 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:42:34 UTC

Description Gabe Montero 2022-01-24 17:01:02 UTC
As the shared resource operator is not a CVO, we cannot set relatedObjects on it for must gather to analyze.

We can set it on cluster-storage-operator, as it is a CVO

Maciej from CLI confirmed for me that if we are running on a non tech preview cluster and the shared resource CRDs are not defined, must-gather can tolerator that error condition and move on to the other types it collects.

Comment 6 errata-xmlrpc 2022-03-10 16:42: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 (Moderate: OpenShift Container Platform 4.10.3 security 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:0056


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