Verified. OCP Version - 4.10.6. kubernetes-nmstate-handler v4.10.1-2. Created veth device on node: [core@n-adiz-410-8d2hr-worker-0-ff9wp ~]$ sudo ip link add 0e12345 type dummy [core@n-adiz-410-8d2hr-worker-0-ff9wp ~]$ sudo ip link set 0e12345 up NNS Succesfully updated without nmstate-handler pod crashing: [cnv-qe-jenkins@n-adiz-410-8d2hr-executor ~]$ oc get nns n-adiz-410-8d2hr-worker-0-ff9wp -o yaml ... interfaces: - ipv4: address: [] enabled: false ipv6: address: - ip: fe80::2ccb:44ff:fe72:b1f4 prefix-length: 64 enabled: true mac-address: 2E:CB:44:72:B1:F4 mtu: 1500 name: "0e12345" state: up type: dummy ... routes: running: - destination: fe80::/64 metric: 256 next-hop-address: '::' next-hop-interface: "0e12345" table-id: 254
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Virtualization 4.10.1 Images security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:4668