If a user creates a OVS bridge using the `NodeNetworkConfigurationPolicy` in GUI, it does not create the bridge with `allow-extra-patch-ports: true`, which leads to triggering the issue explained in https://issues.redhat.com/browse/OCPBUGS-37542

for completeness here is what the bug report mentioned above says 

"Pods connected to an additional OVS bridge through localnet may get abruptly disconnected from the network.

If kubernetes-nmstate pod for any reason restarts, it may reapply all the NNCPs. This would lead to removal of all patch ports connected to configured OVS bridge that were not defined in the NNCP. This means that all Pods and VMs connected to it would be disconnected.

This can be avoided by setting "allow-extra-patch-ports: true" in the NNCP."

    Always

1. Install Kubernetes NMState Operator and create an instance of NMState
2. Once the GUI is reloaded, head to "Networking -> NodeNetworkConfigurationPolicy" tab in the GUI (Console)
3. Create a OVS bridge using the "From Form", remember to set the type to "OVS vSwitch Bridge". 
4. Add a physical port to "Port" (I think it is not really necessary, but for completeness please add one if you have one)    
    

    Triggers the issue as described in https://issues.redhat.com/browse/OCPBUGS-37542

    OVS bridge created with "allow-extra-patch-ports: true"