Description of problem: Tim and I had a short discussion on this. Is it possible to add host logs as well under oc adm for networking? Specially we are running OVS on host now, it would make sense to collect host logs. If its not a candidate for `oc adm must-gather`, then i guess its definitely a candidate for just networking logs `oc adm must-gather –keep -- /usr/bin/gather_network_logs` Version-Release number of selected component (if applicable):4.6 and back How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Per Tim Rozet, logs are munged and hard to read, we should have per worker files.
Anurag, when you say host logs can you be more specific? Stuff from /var/log and/or something else?
host OVS logs. "Specially we are running OVS on host now, it would make sense to collect host logs." openvswitch.service ovsdb-server.service ovs-vswitchd.service and probably just regular journalctl logs
Gotcha, thanks. I'll try to have the PR up.
Verified on 4.6.0-0.nightly-2020-09-24-074159 ./network_logs/qe-o46g4a-8ks9s-master-1.c.openshift-qe.internal_ovsdb_log ./network_logs/qe-o46g4a-8ks9s-master-0.c.openshift-qe.internal_ovsdb_log ./network_logs/qe-o46g4a-8ks9s-master-1.c.openshift-qe.internal_ovs_vswitchd_log ./network_logs/qe-o46g4a-8ks9s-master-0.c.openshift-qe.internal_ovs_vswitchd_log ./network_logs/qe-o46g4a-8ks9s-master-2.c.openshift-qe.internal_ovs_vswitchd_log ./network_logs/qe-o46g4a-8ks9s-master-2.c.openshift-qe.internal_ovsdb_log ./network_logs/qe-o46g4a-8ks9s-worker-a-n5lzl.c.openshift-qe.internal_ovs_vswitchd_log ./network_logs/qe-o46g4a-8ks9s-worker-a-n5lzl.c.openshift-qe.internal_ovsdb_log ./network_logs/qe-o46g4a-8ks9s-worker-b-kqzpx.c.openshift-qe.internal_ovs_vswitchd_log ./network_logs/qe-o46g4a-8ks9s-worker-b-kqzpx.c.openshift-qe.internal_ovsdb_log ./network_logs/qe-o46g4a-8ks9s-worker-c-7kdm8.c.openshift-qe.internal_ovs_vswitchd_log ./network_logs/qe-o46g4a-8ks9s-worker-c-7kdm8.c.openshift-qe.internal_ovsdb_log
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 (OpenShift Container Platform 4.6 GA Images), 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:4196