-
Bug
-
Resolution: Done-Errata
-
Major
-
4.14.0
-
None
-
No
-
Approved
-
False
-
Marko Luksa mentioned multus missing '/etc/cni/multus/net.d' mount in OCP4.14 and here's the repro step (verivied in multus team)
Our original reproducer would be too complex, so I had to write a simple one for you:
Use a 4.14 OpenShift cluster
Create the CNI plugin installer DaemonSet in namespace test:
oc apply -f https://gist.githubusercontent.com/luksa/c4d444e918124604839c424339c29a62/raw/1454bd389138980ea3f93bcfaf6026d4821e3543/noop-cni-plugin-installer.yaml
Create the test Deployment:
oc apply -f https://gist.githubusercontent.com/luksa/4c7c144ef88b1b0d8f772d6eacdeec14/raw/06b161fdb8c71406f4531d35550bd507a6a25200/test-deployment.yaml
Describe the test pod:
oc -n test describe po test
The last event shows the following:
ERRORED: error configuring pod [test/test-6cf67dcfb6-hgszq] networking: Multus: [test/test-6cf67dcfb6-hgszq/3e8a6f0d-ce84-4885-a7a7-43506669339f]: error loading k8s delegates k8s args: TryLoadPodDelegates: error in getting k8s network for pod: GetNetworkDelegates: failed getting the delegate: GetCNIConfig: err in GetCNIConfigFromFile: No networks found in /etc/cni/multus/net.d
The same reproducer runs fine on OCP 4.13
- causes
-
OSSM-4698 [OCP 4.14]CNI request failed with status 400 when a pod with envoy is created
- Closed
- relates to
-
OSSM-4957 istio CNI should be in /var/lib/cni/bin (old title: Regression: multus-thick doesn't look for CNI binaries in /opt/multus/bin)
- Closed
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update