-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.19.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem: label CUDN network after create RA, ra cannot select this network and CUDN network cannot be advertised to external
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. create CUDN L2
$ oc get clusteruserdefinednetwork.k8s.ovn.org/l2-network-cudn1 --show-labels NAME AGE LABELS l2-network-cudn1 63s <none>
2. create RA to advertise CUDN L2
spec: advertisements: - PodNetwork networkSelector: matchLabels: app: udn-l2 $ oc get ra NAME STATUS udn-l2 Not Accepted: configuration pending: no networks selected
3. label this CUDN network with networkSelector match label
$ oc get clusteruserdefinednetwork.k8s.ovn.org/l2-network-cudn1 --show-labels NAME AGE LABELS l2-network-cudn1 2m24s app=udn-l2
4. verify RA successfully select this CUDN network and verify advertisement
// wait up to 10 mins and RA still cannot select this CUDN network status: conditions: - lastTransitionTime: "2025-04-02T03:54:28Z" message: 'configuration pending: no networks selected' observedGeneration: 1 reason: ConfigurationPending status: "False" type: Accepted status: 'Not Accepted: configuration pending: no networks selected'
Actual results: ra cannot select this network after label CUDN and CUDN network cannot be advertised to external
Expected results: ra should select this network after label CUDN and router advertisement should generate.