Comment 11 for bug 1401870

Years later, but adding a comment that this option doesn't appear to work in 100% of the cases, leaving empty bridges on remote hypervisors where no interfaces are attached.

Combined with another ebtables bug that appears to allow traffic to traverse the local bridge and br received by the remote, now empty bridge, it causes DNS and DHCP failures inside instances on the local bridge.

There appears to be a race condition between the time 'fip.host = None' is checked and when that API call commit the change to the db is flushed, where fip.host is checked too soon, and fails to remove the empty bridge.

The result, is an empty, remote bridge receiving traffic destined for a local bridge on another hypervisor.