-
Bug
-
Resolution: Unresolved
-
Undefined
-
2.9.3
Description of problem:
Restricted providers fail to list their own Network Attachment Definitions (NADs) in the inventory. A NAD created in a restricted namespace is not visible when using a command with the -n [restricted-namespace] flag, but it appears when the command is run from an unrestricted namespace.
Version-Release number of selected component (if applicable):
2.9.3
How reproducible:
Always
Steps:
1. VM Setup
- VM Name: mtv-feature-win2022-staticips
- Platform: vCenter 7
- Configuration: 1 disk, 2 NICs
2. Network Attachment Definition (NAD) Creation
Created a NAD file named nad-mtv.yaml with the following configuration:
apiVersion: "k8s.cni.cncf.io/v1" kind: NetworkAttachmentDefinition metadata: name: mybridge namespace: msafra spec: config: '{ "cniVersion": "0.3.1", "type": "cnv-bridge", "bridge": "mybridge" }'
Applied the configuration using:
oc apply -f nad-mtv.yaml
3. UI Mapping Attempt
Attempted to map the Mgmt network to the new NAD in the UI, but "mybridge" did not appear as an option alongside "Pod network".
4. CLI Verification Performed CLI checks with the following results:
kubectl-mtv get inventory network host -n msafra
NAME NAMESPACE ID CREATED nad-incredible-limpet default 31f22809-a8b6-4d12-b4d4-843f9d88d694 2025-09-10T11:57:27Z nad-mad-parakeet default 50e0944b-456f-418f-b7c3-f60f1770a531 2025-09-10T11:57:32Z
kubectl-mtv get inventory network host -n openshift-mtv
NAME NAMESPACE ID CREATED nad-incredible-limpet default 31f22809-a8b6-4d12-b4d4-843f9d88d694 2025-09-10T11:57:27Z nad-mad-parakeet default 50e0944b-456f-418f-b7c3-f60f1770a531 2025-09-10T11:57:32Z mybridge msafra 2e145531-401f-4826-9d73-379dc2390722 2025-09-07T13:33:44Z mybridge1 msafra 1107a6c3-e7e4-48fc-a22d-48b7309d832d 2025-09-09T07:51:36Z mybridge2 msafra c01c9ad7-ec35-4822-84d1-bb0c2e2dd94f 2025-09-09T08:55:01Z mybridge5 msafra 8c06a119-727b-45b0-aaa6-54b9da7439bc 2025-09-11T13:44:14Z mybridge mtv-test 3eaab0b5-4c45-49fd-8e92-5613f38a3a1a 2025-09-10T08:37:51Z mybridge1 mtv-test e139933d-24ff-41bf-aa7e-99818786ff34 2025-09-10T08:37:48Z mybridge5 openshift-mtv db6f0fb4-3ce6-433d-883a-c415ee067541 2025-09-11T13:41:23Z nad-steep-tortoise openshift-mtv 5d792bfa-9386-4500-9b81-c9672ddf37a2 2025-09-10T11:56:26Z nad-willing-possum openshift-mtv d4995946-0182-48a0-95df-c200d5c2903c 2025-09-10T11:56:30Z
Expected results:
- The "mybridge" NAD should be listed as an option in the UI
- The kubectl-mtv command should display the NAD when executed from the namespace where it was created (msafra)
Additional info:
This issue appears to be related to a similar bug that was previously addressed in pull request #2615
- is cloned by
-
-
- Closed
-
