Description of problem: Running must-gather against a baremetal deployment does not collect the logs from the KNI infra static pods. This makes debugging problematic. Version-Release number of selected component (if applicable): 4.5 How reproducible: Always Steps to Reproduce: 1. Run oc adm must-gather against baremetal cluster Actual results: No logs for the containers in openshift-kni-infra Expected results: Logs for containers in openshift-kni-infra (coredns, mdns-publisher, keepalived, haproxy)
]# oc adm must-gather [must-gather ] OUT unable to resolve the imagestream tag openshift/must-gather:latest [must-gather ] OUT [must-gather ] OUT Using must-gather plugin-in image: quay.io/openshift/origin-must-gather:latest [must-gather ] OUT namespace/openshift-must-gather-f8tdw created [must-gather ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-nzrfb created [must-gather ] OUT pod for plug-in image quay.io/openshift/origin-must-gather:latest created [must-gather-wxqwm] OUT gather did not start: unable to pull image: ErrImagePull: rpc error: code = Unknown desc = error pinging docker registry quay.io: Get https://quay.io/v2/: dial tcp 52.1.239.254:443: connect: network is unreachable [must-gather ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-nzrfb deleted [must-gather ] OUT namespace/openshift-must-gather-f8tdw deleted error: gather did not start for pod must-gather-wxqwm: unable to pull image: ErrImagePull: rpc error: code = Unknown desc = error pinging docker registry quay.io: Get https://quay.io/v2/: dial tcp 52.1.239.254:443: connect: network is unreachable
I'm guessing you ran that on an ipv6 deployment? By default, must-gather pulls an image from quay.io, which doesn't work with ipv6. I believe this is a known issue. To make it work, you either need to deploy with ipv4 or pass a must-gather image to the command that exists in an ipv6-accessible registry.
Hi, I've ran it on titan37 Ran this version: version 4.5.0-0.nightly-2020-05-03-051551 all logs created as expected.
Expected results: Logs for containers in openshift-kni-infra (coredns, mdns-publisher, keepalived, haproxy) actual results : all logs created, including the above, etc, too many to list here. OUT namespaces/openshift-kni-infra/pods/coredns-worker-0-0/coredns-monitor/coredns-monitor/logs/current.log OUT namespaces/openshift-kni-infra/pods/coredns-worker-0-0/coredns-monitor/coredns-monitor/logs/current.log OUT namespaces/openshift-kni-infra/pods/keepalived-worker-0-0/keepalived/keepalived/logs/current.log OUT namespaces/openshift-kni-infra/pods/haproxy-master-0-0/haproxy/haproxy/logs/current.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, 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:2409