This epic tracks all the effort needed to deliver the solution related to the bug described below.

 Problem Description: Clearly explain the issue.

Removing the ovn-encap-ip configuration from OVS db (e.g.  ovs-vsctl remove Open_vSwitch . external-ids ovn-encap-ip) does not result in removal of the encap entry in sb.

Afterwards, no other chassis would be able to use this encap-ip (until  ovn-encap-ip is set in the first hv) as the encap still exists in sb.

 Impact Assessment: Describe the severity and impact (e.g., network down,availability of a workaround, etc.).

Low. 

 Software Versions: Specify the exact versions in use (e.g.,openvswitch3.1-3.1.0-147.el8fdp).

main

  Issue Type: Indicate whether this is a new issue or a regression (if a regression, state the last known working version).

Not a regression.

 Reproducibility: Confirm if the issue can be reproduced consistently. If not, describe how often it occurs.

Consistent

 Reproduction Steps: Provide detailed steps or scripts to replicate the issue.

Configure ovn-encap-ip ip1 in chassis-1 and ovn-encap-ip ip2 in chassis-2

Remove ovn-encap-ip from chassis-1

Set ovn-encap-ip ip1 in chassis-2. 

 Expected Behavior: Describe what should happen under normal circumstances.

After an ovn-encap-ip has been removed from a chassis, other chassis should be able to use it.

 Observed Behavior: Explain what actually happens.

 Troubleshooting Actions: Outline the steps taken to diagnose or resolve the issue so far.

 Logs: If you collected logs please provide them (e.g. sos report, /var/log/openvswitch/* , testpmd console)