-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.12
-
None
-
No
-
CNF Network Sprint 240, CNF Network Sprint 241
-
2
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-16019. The following is the description of the original issue:
—
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-17656 Multiple cni-sysctl-allowlist-ds were created in openshift-multus namespace
- Verified
- clones
-
OCPBUGS-16019 Multiple cni-sysctl-allowlist-ds were created in openshift-multus namespace
- Closed
- is blocked by
-
OCPBUGS-16019 Multiple cni-sysctl-allowlist-ds were created in openshift-multus namespace
- Closed
- is cloned by
-
OCPBUGS-17656 Multiple cni-sysctl-allowlist-ds were created in openshift-multus namespace
- Verified
- links to
-
RHBA-2023:4905 OpenShift Container Platform 4.13.z bug fix update