Difference between revisions of "Timed out waiting for the condition"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
| − | default 8m51s Warning [[FailedScheduling]] pod/myprometheus-alertmanager-5967d4ff85-5glkh | + | default 8m51s Warning [[FailedScheduling]] pod/myprometheus-alertmanager-5967d4ff85-5glkh [[running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition]] |
Revision as of 12:54, 27 December 2022
default 8m51s Warning FailedScheduling pod/myprometheus-alertmanager-5967d4ff85-5glkh running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition
kube-system 9m44s Warning FailedMount pod/kube-dns-85df8994db-v8qdg MountVolume.SetUp failed for volume "kube-dns-config" : failed to sync configmap cache: timed out waiting for the condition
default 18m Warning FailedMount pod/sentry-worker-c4c7c9bb8-5k2r5 MountVolume.SetUp failed for volume "config" : failed to sync configmap cache: timed out waiting for the condition
Related
Operation timeout: context deadline exceeded FailedScheduling
See also
kubectl get events, OOMKilling, FailedKillPod, SuccessfulDelete, SuccessfulCreate, NoPods, Warning, Critical, NodeSysctlChange, FailedAttachVolume, FailedMount, UnAvailableLoadBalancer, FailedCreatePodSandBox, InvalidDiskCapacity, Scheduled, NetworkNotReady, Evict, Killing, SuccessfulReconcilied, FailedToUpdateEndpointSlices, BackendNotFound, FailedScheduling, ProvisioningFailed
Advertising:
