ovnkube-controller goes in crashloopbackoff state with the error "user: "system:ovn-node:worker-01" is not allowed to set k8s.ovn.org/node-chassis-id on node"

Issue

• OVNKube-Controller container goes in crashloopbackoff state after the node was rebuild with the error user: "system:ovn-node:worker-01" is not allowed to set k8s.ovn.org/node-chassis-id on node.
• Receiving error ovsdb_idl|WARN|transaction error: {"details":"Transaction causes multiple rows in "Encap" table to have identical values (geneve and "xxx.xxx.xxx.xxx") for index on columns "type" and "ip". First row, with UUID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, existed in the database before this transaction and was not modified by the transaction. Second row, with UUID yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy, was inserted by this transaction.","error":"constraint violation"}
• Node stuck with NotReady state.

• Observing below events while describe the NotReady node:

  $ oc describe node/worker-2.test.redhat.com
  
  Ready            False   Wed, 26 Jun 2024 23:51:12 -0400   Wed, 26 Jun 2024 04:58:29 -0400   KubeletNotReady              container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: No CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?
  

• Error encountered by the ovnkube-controller container within the ovnkube-node pod on respective NotReady node:

  $ omc logs ovnkube-node-xxxxx -n openshift-ovn-kubernetes  -c ovnkube-controller
  
  2026-02-27T05:30:08.106509930Z F0227 05:30:08.106496 2065308 ovnkube.go:138] failed to run ovnkube: failed to start node network controller: failed to init default node network controller: failed to set node <nodename> annotations: admission webhook "node.network-node-identity.openshift.io" denied the request: user: "system:ovn-node:<nodename>" is not allowed to set k8s.ovn.org/node-chassis-id on node "<nodename>": k8s.ovn.org/node-chassis-id cannot be changed once set