-
Bug
-
Resolution: Done
-
Normal
-
None
-
openshift-4.16, openshift-4.17
-
None
-
None
Description of problem:
after disconnected VM reboot the dhcp-daemon-fqncl pod is not started with `ImagePullBackOff` error.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1.install RPM based Microshift instance with optional multus rpm (should be reproduced on ostree also). 1.make sure all the pods are running . 2.disconnect Microshift running VM from the external network 3.reboot the VM
Actual results:
dhcp-daemon-fqncl pod dont come up.
Expected results:
all the pods should come up
Additional info:
[root@microshift-local ~]# oc get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system csi-snapshot-controller-bb7cb654b-5xqlh 1/1 Running 4 6d21h kube-system csi-snapshot-webhook-95f475949-pn6lv 1/1 Running 4 6d21h openshift-dns dns-default-7m9sj 2/2 Running 8 6d21h openshift-dns node-resolver-kgxtk 1/1 Running 6 6d21h openshift-gitops argocd-application-controller-0 0/1 ImagePullBackOff 0 3h4m openshift-gitops argocd-redis-7488b56d65-vsjdj 0/1 ImagePullBackOff 0 3h4m openshift-gitops argocd-repo-server-68cc8d89b6-7w4q4 0/1 ImagePullBackOff 0 3h4m openshift-ingress router-default-5b48b55f48-nnvj7 1/1 Running 4 6d21h openshift-multus dhcp-daemon-fqncl 0/1 ImagePullBackOff 2 (158m ago) 6d21h openshift-multus multus-82bfx 1/1 Running 5 6d21h openshift-operator-lifecycle-manager catalog-operator-56d67b6988-4zcv5 1/1 Running 4 6d21h openshift-operator-lifecycle-manager olm-operator-68db4bdcf7-pn4vv 1/1 Running 4 6d21h openshift-ovn-kubernetes ovnkube-master-6fptn 4/4 Running 26 6d21h openshift-ovn-kubernetes ovnkube-node-thnpx 1/1 Running 7 6d21h openshift-service-ca service-ca-5d7bd9db6-tflxl 1/1 Running 5 6d21h openshift-storage lvms-operator-656cd9b59b-8f6xn 1/1 Running 4 6d21h openshift-storage vg-manager-n6tqz 1/1 Running 8 (30m ago) 6d21h
- links to
