-
Feature Request
-
Resolution: Done
-
Minor
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
1. Proposed title of this feature request
Add information indicating the severity of the problem to the message output by "oc adm must-gater"
2. What is the nature and description of the request?
Under a cluster, oc adm must-gather may produce the following outputs:
~~~
error: errors ocurred while gathering data:
[skipping gathering EgressFirewall.k8s.ovn.org due to error: the server doesn't have a resource type "EgressFirewall",
skipping gathering EgressIP.k8s.ovn.org due to error: the server doesn't have a resource type "EgressIP",
skipping gathering namespaces/openshift-manila-csi-driver due to error: namespaces "openshift-manila-csi-driver" not found]
~~~
According to the RHBZ#2048898#c2[2], I think we can ignore some messages.
| must-gather has a fallback mechanism in case it has issues gathering data, so it will do its best to gather anything which it does.
| Whatever is not it will report, but those are not errors you should be worried about, that's how must-gather is designed.
|
| So it should be something that could be safely ignored.
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2048898#c2
However, it is difficult for the customers to determine if the message is really worth ignoring.
So, could we add a feature from must-gather to also display the level of the message (Error, Informational, Debug ),
or to message a suggestion on how to judge?
3. Why does the customer need this? (List the business requirements here)
refer to 2 above.
4. List any affected packages or components.
oc