Hide Forgot
Description of problem: backport https://github.com/openshift/must-gather/pull/94 https://jira.coreos.com/browse/SDN-428
https://github.com/openshift/must-gather/pull/101 is tracking this.
using the latest 4.1 nightly build 4.1.0-0.nightly-2019-06-26-044128 when using `oc adm must-gather` , did not find the network related information.
*** Bug 1724746 has been marked as a duplicate of this bug. ***
hi, I tried this issue on 4.1.0-0.nightly-2019-06-27-204847 and 4.1.0-0.nightly-2019-06-30-214248. Both of them are not fixed this bug. from https://github.com/openshift/must-gather/pull/101/files, it's using 'must-gather' as the folder. but when run 'oc adm must-gather', it will create random folder like named 'must-gather.local.4807231115650811082', I'm not sure if it causes the issue. FYI. it can work if I run this shell script 'https://raw.githubusercontent.com/openshift-cherrypick-robot/must-gather/1638ec49bc976a65c3f41bc5d5ce3b8bc2813959/collection-scripts/gather_network_logs' separately.
(In reply to zhaozhanqi from comment #7) > > FYI. it can work if I run this shell script > 'https://raw.githubusercontent.com/openshift-cherrypick-robot/must-gather/ > 1638ec49bc976a65c3f41bc5d5ce3b8bc2813959/collection-scripts/ > gather_network_logs' separately. The script is not run by default! So running it separately is how this should be tested.
The 'gather_network_logs' script is not invoked on 'gather', which is the script run by 'oc adm must-gather'. That is due to gather_network_logs is expected to consume a list of nodes, instead of been a general collection script. In looking by this I saw a tangential issue, the 'gather_network_logs' won't create correctly /must-gather, check PR https://github.com/openshift/must-gather/pull/108 .
*** Bug 1726144 has been marked as a duplicate of this bug. ***
Verified this bug on 4.1.0-0.nightly-2019-07-29-171515 with command: oc adm must-gather --keep -- /usr/bin/gather_network_logs
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-2019:2010