-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.13
-
None
-
Moderate
-
None
-
False
-
-
N/A
-
Bug Fix
-
Done
Description of problem:
During end2end test (see report [1]) multus-networkpolicy pods don't translate MultiNetworkPolicies to IPTables. Logs contains many entries like: E0131 00:13:56.492610 1 pod.go:348] failed to get pod(openshift-monitoring/prometheus-adapter-7b6bb56874-k52ht) network namespace: cannot get containerStatus: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
Version-Release number of selected component (if applicable):
4.13
How reproducible:
Some clusters have 100% chance to reproduce the issue, see additional info
Steps to Reproduce:
1. Enable MultiNetworkPolicy [2] 2. deploy attached scenario [3] oc apply -f simple-v4-ingress.yml 3. Find logs of any pod in multus-networkpolicy daemonset
Actual results:
No error like: failed to get pod(openshift-monitoring/prometheus-adapter-7b6bb56874-k52ht) network namespace: cannot get containerStatus: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
Expected results:
errors present
Additional info:
Clusters where this issue can be reproduced has CRI-O version `1.26.1-6.rhaos4.13.git159cc9c.el8`. On clusters with 1.25.1-2.rhaos4.12.gitafa0c57.el8 version the problem is not present.