$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.0-0.nightly-2020-06-21-210301 True False 31m Cluster version is 4.4.0-0.nightly-2020-06-21-210301 $ oc get nodes NAME STATUS ROLES AGE VERSION ip-10-0-134-175.us-east-2.compute.internal Ready worker 38m v1.17.1+9d33dd3 ip-10-0-153-156.us-east-2.compute.internal Ready master 51m v1.17.1+9d33dd3 ip-10-0-165-188.us-east-2.compute.internal Ready master 51m v1.17.1+9d33dd3 ip-10-0-174-121.us-east-2.compute.internal Ready worker 38m v1.17.1+9d33dd3 ip-10-0-221-122.us-east-2.compute.internal Ready master 51m v1.17.1+9d33dd3 ip-10-0-222-3.us-east-2.compute.internal Ready worker 38m v1.17.1+9d33dd3 $ oc debug node/ip-10-0-153-156.us-east-2.compute.internal Starting pod/ip-10-0-153-156us-east-2computeinternal-debug ... ... sh-4.4# journalctl -u kubelet | grep -i pod-infra-container-image Jun 22 06:26:36 ip-10-0-153-156 hyperkube[1393]: I0622 06:26:36.940346 1393 flags.go:33] FLAG: --pod-infra-container-image="quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c3575794b54ddace8648aceb51c456070078aaf8c1949be8f2e8670872053a17" Jun 22 06:26:36 ip-10-0-153-156 hyperkube[1393]: W0622 06:26:36.942473 1393 server.go:191] Warning: For remote container runtime, --pod-infra-container-image is ignored in kubelet, which should be set in that remote runtime instead sh-4.4# journalctl -u kubelet | grep -e "k8s.gcr.io" -e pause sh-4.4#
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:2713