NSX-T NCP nsx-node-agent goes into CrashLoopBackOff state after Openshift upgrade from 4.8 to 4.9

Products

• VMware NSX Networking

Issue/Introduction

Symptoms:

• After upgrading Openshift from version 4.8 to 4.9, your nsx-node-agents pods go into CrashLoopBackOff state.
• View the pods logs:

kubectl logs -c nsx-ovs <nsx-node-agent> -n nsx-system

• You see the following error:

2022-10-17T11:52:46Z ocp-worker-test01.local NSX 1 - [nsx@6876 comp="nsx-container-node" subcomp="NSX-OVS" level="INFO"] .usr.local.bin.start_ovs DHCP connection profile is active on ens192 with connection id 'Wired connection 1'. Adding br-int and activating DHCP on it
Error: Failed to add 'br-int' connection: ipv6.addr-gen-mode: property is invalid
no such bridge
ovs-appctl: ovs-vswitchd: server returned an error
no such bridge

Environment

VMware NSX-T Data Center
VMware NSX-T Data Center 3.x

Cause

The issue is due to a change in the NetworkManager service used by Openshift versions 4.9 or greater.

Resolution

This is resolved in NSX-T 4.0.1 available at VMware downloads .

Workaround:
Revert the node Openshift version used on the nodes, to the original version (prior to the upgrade).