Bug 2090730 - must-gather should include multus logs.
Summary: must-gather should include multus logs.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.0
Assignee: Nikhil Simha
QA Contact: Weibin Liang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-26 12:50 UTC by Douglas Smith
Modified: 2022-08-10 11:14 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:14:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift must-gather pull 306 0 None open Bug 2090730: Adds collection of Multus log files 2022-05-26 12:52:19 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:14:54 UTC

Description Douglas Smith 2022-05-26 12:50:58 UTC 
Description of problem: While Multus is not typically deployed with debug-level logging, in the case that on-disk Multus debug logs are present, they should be collected with must-gather.
Comment 3 Weibin Liang 2022-06-02 15:03:15 UTC 
Tested and verified in 4.11.0-0.nightly-2022-06-01-200905

[weliang@weliang tmp]$ oc adm must-gather –dest-dir=/tmp/must-gather
[weliang@weliang tmp]$ cd /tmp/must-gather
[weliang@weliang must-gather]$ ls
event-filter.html
quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-75770505043c3109643632b7d5db087b922dc6baf184ac2273a153d18000d9e3
timestamp
[weliang@weliang must-gather]$ cd quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-75770505043c3109643632b7d5db087b922dc6baf184ac2273a153d18000d9e3/
[weliang@weliang quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-75770505043c3109643632b7d5db087b922dc6baf184ac2273a153d18000d9e3]$ ls
cluster-scoped-resources  event-filter.html  ingress_controllers  monitoring  network_logs  timestamp  web_hooks
etcd_info                 host_service_logs  insights-data        namespaces  static-pods   version
[weliang@weliang quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-75770505043c3109643632b7d5db087b922dc6baf184ac2273a153d18000d9e3]$ cd network_logs/
[weliang@weliang network_logs]$ ls
cluster_scale  ippools  multi_networkpolicy  multus_logs  net_attach_def  overlappingrangeipreservations
[weliang@weliang network_logs]$ 
[weliang@weliang network_logs]$ cd multus_logs/
[weliang@weliang multus_logs]$ ls
multus-log-weliang-621-k762j-master-0.c.openshift-qe.internal.log
multus-log-weliang-621-k762j-master-1.c.openshift-qe.internal.log
multus-log-weliang-621-k762j-master-2.c.openshift-qe.internal.log
[weliang@weliang multus_logs]$ 
[weliang@weliang multus_logs]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-06-01-200905   True        False         67m     Cluster version is 4.11.0-0.nightly-2022-06-01-200905
[weliang@weliang multus_logs]$
Comment 5 errata-xmlrpc 2022-08-10 11:14:33 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: OpenShift Container Platform 4.11.0 bug fix and 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:5069
Note You need to log in before you can comment on or make changes to this bug.