After successfully creating a NAD of type: "OVN Kubernetes secondary localnet network", when viewing the object in the GUI, it will say that it is of type "OVN Kubernetes L2 overlay network".

When examining the objects YAML, it is still correctly configured as a NAD type of localnet.

Version-Release number of selected component:
OCP Virtualization 4.15.1

How reproducible:100%

Steps to Reproduce:
1. Create appropriate NNCP and apply
for example:

apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
  name: nncp-br-ex-vlan-101
spec:
  nodeSelector:
    node-role.kubernetes.io/worker: '' 
  desiredState:
    ovn:
      bridge-mappings:
      - localnet: vlan-101 
        bridge: br-ex
        state: present 

2. Create localnet type NAD (from GUI or YAML)
For example:

apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
  name: vlan-101
  namespace: default
spec:
  config: |2 
    {
           "name":"br-ex",
           "type":"ovn-k8s-cni-overlay",
           "cniVersion":"0.4.0",
           "topology":"localnet",
           "vlanID":101,
           "netAttachDefName":"default/vlan-101"
     } 

3. View through the GUI by clicking on Networking–>NetworkAttachementDefinitions–>NAD you just created

4.  When you look under type it will incorrectly display as Type: OVN Kubernetes L2 overlay Network

Actual results:

Type is displayed as OVN Kubernetes L2 overlay Network

If you examine the YAML for the NAD you will see that it is indeed still of type localnet

Please see attached screenshots for display of NAD type and the actual YAML of NAD.

At this point in time it looks as though this is just a display error.

Expected results:
Type should be displayed as OVN Kubernetes secondary localnet network