*** Bug 2101826 has been marked as a duplicate of this bug. ***
*** Bug 2101859 has been marked as a duplicate of this bug. ***
What version should this be in? I scaled an AWS ARM cluster to 75 nodes and am seeing this issue 4.11.0-0.nightly-arm64-2022-06-28-160338 % oc get pods -A | grep Creating openshift-multus network-metrics-daemon-ffx8p 0/2 ContainerCreating 0 42m openshift-multus network-metrics-daemon-vzsdr 0/2 ContainerCreating 0 40m openshift-network-diagnostics network-check-target-ldghb 0/1 ContainerCreating 0 40m openshift-network-diagnostics network-check-target-zdtbd 0/1 ContainerCreating 0 42m % oc get co NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE authentication 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 51m baremetal 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 73m cloud-controller-manager 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 82m cloud-credential 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 82m cluster-autoscaler 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 72m config-operator 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 79m console 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 59m csi-snapshot-controller 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 73m dns 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 72m etcd 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 77m image-registry 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 63m ingress 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 62m insights 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 74m kube-apiserver 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 68m kube-controller-manager 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 76m kube-scheduler 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 76m kube-storage-version-migrator 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 74m machine-api 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 69m machine-approver 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 73m machine-config 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 42m marketplace 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 73m monitoring 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 60m network 4.11.0-0.nightly-arm64-2022-06-28-160338 True True False 82m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 73m openshift-apiserver 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 69m openshift-controller-manager 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 70m openshift-samples 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 71m operator-lifecycle-manager 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 73m operator-lifecycle-manager-catalog 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 73m operator-lifecycle-manager-packageserver 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 71m service-ca 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 79m storage 4.11.0-0.nightly-arm64-2022-06-28-160338 True False False 73m
*** Bug 2101860 has been marked as a duplicate of this bug. ***
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 (Important: OpenShift Container Platform 4.11.0 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-2022:5069