-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem: Pod does not get the User Defined Network in HCP kubevirt cluster.
Version-Release number of selected component (if applicable): 4.18.7
How reproducible: Always
Summary:
- Create NS as follows:
apiVersion: v1 kind: Namespace metadata: name: hchaturv-udn-test labels: k8s.ovn.org/primary-user-defined-network: "
- Create UDN as follows:
apiVersion: k8s.ovn.org/v1 kind: UserDefinedNetwork metadata: creationTimestamp: '2025-04-06T12:48:54Z' finalizers: - k8s.ovn.org/user-defined-network-protection generation: 1 name: udn-1 namespace: aygarg-udn-test resourceVersion: '61152' uid: 39c23e4e-8e52-481c-a2fa-7d55150aec01 spec: layer3: joinSubnets: - 100.67.0.0/16 role: Primary subnets: - cidr: 192.171.0.0/16 topology: Layer3 status: conditions: - lastTransitionTime: '2025-04-06T12:48:54Z' message: NetworkAttachmentDefinition has been created reason: NetworkAttachmentDefinitionCreated status: 'True' type: NetworkCreated
- Nad are created as follows:
$ oc get net-attach-def NAME AGE udn-1 6m59s
- However, pods are not created
$ oc get pods NAME READY STATUS RESTARTS AGE httpbin-9fb6548f-dfk48 0/1 ContainerCreating 0 7m2s
- Events shows that NAD is not processed
$ oc get events LAST SEEN TYPE REASON OBJECT MESSAGE 7m30s Normal Scheduled pod/httpbin-9fb6548f-dfk48 Successfully assigned aygarg-udn-test/httpbin-9fb6548f-dfk48 to himank-test-nodepool-bbddp-t695r 82s Warning ErrorReconcilingPod pod/httpbin-9fb6548f-dfk48 primary UDN "udn-1" exists in namespace aygarg-udn-test, but NAD has not been processed yet 7m30s Warning ErrorUpdatingResource pod/httpbin-9fb6548f-dfk48 addLogicalPort failed for aygarg-udn-test/httpbin-9fb6548f-dfk48: primary UDN "udn-1" exists in namespace aygarg-udn-test, but NAD has not been processed yet
