-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19.z
-
None
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
In the OpenShift Web Console, the Type column for a NetworkAttachmentDefinition (NAD) displays as "Not Available" if the resource was created via a YAML manifest (either through the "Import YAML" button or via oc apply). Conversely, if the NAD is created using the guided form in the UI, the type displays correctly. Despite the UI error, the underlying networking functionality works as expected, and pods can successfully attach to the network, indicating a front-end parsing or display issue.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Create a NAD using the CLI. e.g [1]
Then, navigate to the web console --> Networking --> NetworkAttachmentDefinitions and verify the Type section for the newly created NAD.
[1]
apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
annotations:
description: vlan123
name: vlan123
namespace: default
spec:
config: '{"name":"vlan123","cniVersion":"0.3.1","plugins":[{"type":"cnv-bridge","bridge":"br123","ipam":{}},{"type":"cnv-tuning"}]}'
Actual results:
The Type column for the newly created NAD displays as "Not Available".
Expected results:
The Type column should display the value defined in the type field within the config.
Additional info:
- is triggered by
-
OCPBUGS-77176 Web console displays NAD type as "Not Available" when created via YAML
-
- Closed
-