VMware NSX Container Plugin 4.1.0.2 Release Notes

VMware NSX Container Plugin 4.1.0.2 \| 10 AUG 2023 \| Build 22150091 Check for additions and updates to these release notes.

VMware NSX Container Plugin 4.1.0.2 | 10 AUG 2023 | Build 22150091

Check for additions and updates to these release notes.

What's New

NSX Container Plugin 4.1.0.2 is an update release that resolves issues found in earlier releases. For other details about this release, see NSX Container Plugin 4.1.0 Release Notes.

Resolved Issues

Issue 3154583: nsx-node-agent does not run after upgrading kernel on Kubernetes node

After upgrading the kernel version on Kubernetes node to 5.15 or later, nsx-node-agent fails to run. Nsx-node-agent has a dependent package, pyroute2, that may not be compatible with the OS kernel and will fail to operate network interfaces. If the kernel version is 5.15 or later, the nsx-node-agent pod may crash, and pods scheduled on the node may be stuck at the ContainerCreating status. The nsx-node-agent logs will show errors such as the following:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/nsx_ujo/agent/agent.py", line 218, in create_interface_linux
    ip.link('del', index=index_list[0])
  File "/usr/local/lib/python3.8/dist-packages/pyroute2/iproute/linux.py", line 1358, in link
    ret = self.nlm_request(msg,
  File "/usr/local/lib/python3.8/dist-packages/pyroute2/netlink/nlsocket.py", line 376, in nlm_request
    return tuple(self._genlm_request(*argv, **kwarg))
  File "/usr/local/lib/python3.8/dist-packages/pyroute2/netlink/nlsocket.py", line 867, in nlm_request
    for msg in self.get(msg_seq=msg_seq,
  File "/usr/local/lib/python3.8/dist-packages/pyroute2/netlink/nlsocket.py", line 379, in get
    return tuple(self._genlm_get(*argv, **kwarg))
  File "/usr/local/lib/python3.8/dist-packages/pyroute2/netlink/nlsocket.py", line 704, in get
    raise msg['header']['error']
pyroute2.netlink.exceptions.NetlinkError: (95, 'Operation not supported')

Workaround< None. If you upgrade the kernel version, you must also upgrade the NCP version.

Issue 3215514: Hyperbus channel is down after cfgAgent restart on ESXi host

Sometimes after a cfgAgent restart on ESXi host, hyperbus connection remains down. cfgAgent cannot reconnect with nsx-node-agent because nsxrpc thread in nsx-node-agent is stuck at closing the previous connection. The nsx-node-agent log has the message "Cannot convert greenlet.greenlet to gevent._gevent_c_greenlet_primitives.SwitchOutGreenletWithLoop." Hyperbus CLI command on ESXi host shows the status as "MISS_VERSION_HANDSHAKE," which means the connection is unhealthy. The nsx-node-agent CLI command "get node-agent-hyperbus status" on ContainerHost returns the message "HyperBus status: Unhealthy."

Workaround: Restart nsx-node-agent.