Comment 14 for bug 1940425

Setting this to incomplete for os-vif while we discuss this more.

form my perspective this looks like a neutron bug.

os-vif is now deleting the bridge but it only does that after unplugging the ports on ovs.
so at the time we delete the bridge the trunk port (the parent and the subports) have been unplugged form ovs
by os-vif as it always did. so neutron should not be managing those port or depending on the bridge anymore.

the l2 agent should be tolerant to the bridge not exiting and handle that gracefully.

so to me this looked like a prexisign bug in neutron which os-vif is not exposing.
not an error in the logic of the os-vif change or a failure to consider upgrades.

we can perhaps workaround this via a more complicated arrangement but if we make any change to os-vif for this i think i would prefer to keep this as simple as possible meaning no smart just a config option.

that said my preference would be to fix this in neutron only.