+++ This bug was initially created as a clone of Bug #2071799 +++
Description of problem: On the CNI DEL path, Multus CNI should exit cleanly, otherwise, pods can wind up in a crash loop.
How reproducible: Difficult, requires API server to be unreachable.
Need a cherry pick approval and QE run on openshift/multus-cni/pull/132, thanks!
Move this to POST status since it still not be merged yet.
Tested and verified in 4.10.0-0.nightly-2022-11-24-131934
sh-4.4# journalctl -xe -u crio | grep 'but continue to delete'
Nov 28 16:41:05 weliang-1128b-t8ghl-compute-0 crio: 2022-11-28T16:41:05Z [error] Multus: getPod failed: Multus: [test/hello-pod/ea6c9fd1-a8be-4351-ae39-c77c2e7b7b48]: error getting pod: Get "https://[api-int.weliang-1128b.qe.devcluster.openshift.com]:6443/api/v1/namespaces/test/pods/hello-pod?timeout=1m0s": dial tcp 10.0.96.38:6443: i/o timeout, but continue to delete
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 (OpenShift Container Platform 4.10.45 bug fix 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.