Version: $ openshift-install version 4.4.5 Platform: Baremetal IPI What happened? Metal3 container will not go to running state in proxy environment Specifically the journal on the metal3 master node shows: Oct 02 19:33:21 openshift-master-2 hyperkube[2257]: + Name: "metal3-machine-os-downloader", Oct 02 19:33:21 openshift-master-2 hyperkube[2257]: + State: v1.ContainerState{Running: s"&ContainerStateRunning{StartedAt:2020-10-02 19:32:33 +0000 UTC,}"}, Oct 02 19:33:21 openshift-master-2 hyperkube[2257]: + LastTerminationState: v1.ContainerState{ Oct 02 19:33:21 openshift-master-2 hyperkube[2257]: + Terminated: s"&ContainerStateTerminated{ExitCode:7,Signal:0,Reason:Error,Message:,StartedAt:2020-10-02 19:25:23 +0000 UTC,FinishedAt:2020-> And metal3-machine-os-downloader shows: [kni@provisioner clusterconfigs]$ oc logs -n openshift-machine-api metal3-684f9f9b95-gqf55 -c metal3-machine-os-downloader+ export http_proxy=+ http_proxy=+ export https_proxy=+ https_proxy=+ export 'RHCOS_IMAGE_URL=https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz?sha256=f8a44e0ea8cc45882dc22eb632a63afb90b414839b8aa92f3836ede001dfe9cf'+ RHCOS_IMAGE_URL='https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz?sha256=f8a44e0ea8cc45882dc22eb632a63afb90b414839b8aa92f3836ede001dfe9cf'+ '[' -z 'https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz?sha256=f8a44e0ea8cc45882dc22eb632a63afb90b414839b8aa92f3836ede001dfe9cf' ']'++ echo 'https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz?sha256=f8a44e0ea8cc45882dc22eb632a63afb90b414839b8aa92f3836ede001dfe9cf'++ cut -f 1 -d '?'+ RHCOS_IMAGE_URL_STRIPPED=https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz+ [[ https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz =~ qcow2.[gx]z$ ]]++ basename https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz+ RHCOS_IMAGE_FILENAME_RAW=rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz+ RHCOS_IMAGE_FILENAME_OPENSTACK=rhcos-44.81.202004250133-0-openstack.x86_64.qcow2+ IMAGE_FILENAME_EXTENSION=.gz++ dirname https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz+ IMAGE_URL=https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64+ RHCOS_IMAGE_FILENAME_COMPRESSED=rhcos-44.81.202004250133-0-compressed.x86_64.qcow2+ FFILENAME=rhcos-ootpa-latest.qcow2+ mkdir -p /shared/html/images /shared/tmp++ mktemp -d -p /shared/tmp+ TMPDIR=/shared/tmp/tmp.KwV1Z3u8t1+ cd /shared/tmp/tmp.KwV1Z3u8t1+ '[' -s /shared/html/images/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2/rhcos-44.81.202004250133-0-compressed.x86_64.qcow2.md5sum ']'+ curl -g --insecure --compressed -L -o rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202004250133-0/x86_64/rhcos-44.81.202004250133-0-openstack.x86_64.qcow2.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:36 --:--:-- 0[ What did you expect to happen? Expected metal3 pod to go to running state and then provision workers. How to reproduce it (as minimally and precisely as possible)? Anything else we need to know?
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 (Moderate: OpenShift Container Platform 4.8.2 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-2021:2438