openshift-ovn-kubernetes pod is Back-off restarting failed caused by Dynatrace

Solution Unverified - Updated -

Environment

  • Red Hat OpenShift Service on AWS (ROSA)
    • 4

Issue

  • The following error occurs in the openshift-ovn-kubernetes pod:

    [root@ip-XX-XXX-XXX-XX ~]# oc get pod
NAME                   READY   STATUS             RESTARTS      AGE
ovnkube-master-xxxxx   6/6     Running            0             52m
ovnkube-master-xxxxx   6/6     Running            0             52m
ovnkube-master-xxxxx   6/6     Running            0             52m
ovnkube-node-xxxxx     5/5     Running            0             171m
ovnkube-node-xxxxx     5/5     Running            3 (45m ago)   46m
ovnkube-node-xxxxx     4/5     CrashLoopBackOff   7 (69s ago)   12m

    Generated from kubelet on ip-XX-XXX-XXX-XX.ap-northeast-1.compute.internal
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox 
k8s_XXXXXXXXX(XXXXX): 
error adding pod <pod-name> to CNI network "multus-cni-network": 
plugin type="multus" name="multus-cni-network" failed (add): [<pod-name>:ovn-kubernetes]: 
error adding container to network "ovn-kubernetes": failed to send CNI request: Post "http://dummy/": 
dial unix /var/run/ovn-kubernetes/cni//ovn-cni-server.sock: connect: connection refused

Resolution

Disabled the monitoring settings of Dynatrace OneAgent, the relevant pods resumed the running state.

Root Cause

Under investigation.
Suppose this should be affected by Dynatrace, Dynatrace support has reported a problem with a specific version of Dynatrace Operator, but no final results yet.

Diagnostic Steps

  • Check if the pod's IP in the work node is blocked somehow in the proxy.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments