-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
Yes
-
x86_64
-
None
-
None
-
CORENET Sprint 276
-
1
-
Customer Escalated
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
After upgrading the cluster from version 4.16.28 to 4.18.16, PODs suddenly became stuck in the ContainerCreating status. This issue was observed on two of the six clusters and affected both user-deployed PODs as well as OpenShift system PODs. The problem was resolved by restarting the ovnkube-node component, as outlined in KCS 7085628. Although KCS notes that this issue was fixed in version 4.16.0, it continued to occur on version 4.18.16.
https://access.redhat.com/solutions/7085628
The error is exactly the same as OCPBUGS-23519, except it does not include the StdinData (ASCII-encoded JSON).
openshift-monitoring 2h27m Warning FailedCreatePodSandBox pod/metrics-server-548cf9867b-tstb6 (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_metrics-server-548cf9867b-tstb6_openshift-monitoring_3f3f4acd-ac9b-4d91-9991-ce4b56b2cb9b_0(211a6d6b07b65a87fb7dc4227f9ca1a2b4e1d1482aecdeac1b5840dd2c502a41): error adding pod openshift-monitoring_metrics-server-548cf9867b-tstb6 to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"211a6d6b07b65a87fb7dc4227f9ca1a2b4e1d1482aecdeac1b5840dd2c502a41" Netns:"/var/run/netns/b1b3267d-bf78-41f5-93f2-b7d3b781495b" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=openshift-monitoring;K8S_POD_NAME=metrics-server-548cf9867b-tstb6;K8S_POD_INFRA_CONTAINER_ID=211a6d6b07b65a87fb7dc4227f9ca1a2b4e1d1482aecdeac1b5840dd2c502a41;K8S_POD_UID=3f3f4acd-ac9b-4d91-9991-ce4b56b2cb9b" Path:"" ERRORED: error configuring pod [openshift-monitoring/metrics-server-548cf9867b-tstb6] networking: [openshift-monitoring/metrics-server-548cf9867b-tstb6/3f3f4acd-ac9b-4d91-9991-ce4b56b2cb9b:ovn-kubernetes]: error adding container to network "ovn-kubernetes": CNI request failed with status 400: '[openshift-monitoring/metrics-server-548cf9867b-tstb6 211a6d6b07b65a87fb7dc4227f9ca1a2b4e1d1482aecdeac1b5840dd2c502a41 network default NAD default] [openshift-monitoring/metrics-server-548cf9867b-tstb6 211a6d6b07b65a87fb7dc4227f9ca1a2b4e1d1482aecdeac1b5840dd2c502a41 network default NAD default] failed to get pod annotation: timed out waiting for annotations: context deadline exceeded...
Version-Release number of selected component (if applicable):
4.18.16
How reproducible:
No clear reproducibility scenario (intermittently)
Actual results:
PODs stuck in ContainerCreating state
Expected results:
PODs should not be stuck in ContainerCreating state and be scheduled correctly.
- depends on
-
-
- Verified
-
- is cloned by
-
-
- Verified
-
-
-
- Closed
-
- links to
