primary udn, l2 not configuring ipv6 at management port.

[qinqon]

What happened?

At dual stack cluster and primary UDN l2 nad the management port should have a .2 ipv6 address too, but looks like this is not the case

$ docker exec ovn-worker ip a show dev ovn-k8s-mp1
12: ovn-k8s-mp1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1400 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether be:b4:ea:36:82:29 brd ff:ff:ff:ff:ff:ff
    inet 10.100.200.2/24 brd 10.100.200.255 scope global ovn-k8s-mp1
       valid_lft forever preferred_lft forever
    inet6 fe80::bcb4:eaff:fe36:8229/64 scope link 
       valid_lft forever preferred_lft forever

What did you expect to happen?

The primary UDN mp interface should have a ipv6 address.

How can we reproduce it (as minimally and precisely as possible)?

$ ./contrib/kind.sh -i6  -nse -mne -ic 
$ kubectl apply -f - <<EOF
---
apiVersion: v1
kind: Namespace
metadata:
  name: poc1
---
apiVersion: k8s.cni.cncf.io/v1                                                  
kind: NetworkAttachmentDefinition                                               
metadata:                                                                       
  namespace: poc1
  name: l2
spec:                                                                           
  config: |2                                                                    
    {                                                                           
            "cniVersion": "0.3.0",                                              
            "name": "l2-network",                                               
            "type": "ovn-k8s-cni-overlay",                                      
            "topology":"layer2",                                                
            "subnets": "10.100.200.0/24,2014:100:200::0/60",                                       
            "netAttachDefName": "poc1/l2",                               
            "allowPersistentIPs": true,
            "role": "primary"
    }
EOF

Anything else we need to know?

No response

OVN-Kubernetes version

$ ovnkube --version
# paste output here

Kubernetes version

$ kubectl version
# paste output here

OVN version

$ oc rsh -n ovn-kubernetes ovnkube-node-xxxxx (pick any ovnkube-node pod on your cluster)
$ rpm -q ovn
# paste output here

OVS version

$ oc rsh -n ovn-kubernetes ovs-node-xxxxx (pick any ovs pod on your cluster)
$ rpm -q openvswitch
# paste output here

Platform

Is it baremetal? GCP? AWS? Azure?

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)