-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.12
-
None
Description of problem:
Hello, one of our customers had several cni-sysctl-allowlist-ds created (around 10.000 pods) in openshift-multus namespace. That caused several issues in the cluster, as nodes were full of pods an run out of IPs. After deleting them, the situation has improved. But we want to know the root cause of this issue. Searching in the network-operator pod logs, it seems that the customer faced some networking issues. After this issue, we can see that the cni-sysctl-allowlist pods started to be created. Could we know why the cni-sysctl-allowlist-ds pods were created?
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- blocks
-
OCPBUGS-17457 Multiple cni-sysctl-allowlist-ds were created in openshift-multus namespace
- Closed
- is cloned by
-
OCPBUGS-17457 Multiple cni-sysctl-allowlist-ds were created in openshift-multus namespace
- Closed
- is documented by
-
OCPBUGS-29537 [enterprise-4.14] Issue in file release_notes/ocp-4-14-release-notes.adoc
- Closed
- is related to
-
OCPBUGS-29468 [enterprise-4.14] Issue in file release_notes/ocp-4-14-release-notes.adoc
- Closed
- links to
-
RHEA-2023:5006 rpm