seting the admin state down simply sets the linkstate down.
if disabling the network which sets the admin state of the network down does something other then set the admin state on all the ports on that netorkdown perhaps there is a race? but if its just setting the port down i dont see how that would cause a loop since that would just set the linkstate down.
what release of openstack are you using
i have not found the code path for disabling a network but assuming it just set the adminstate on all the ports to down /review. opendev. org/#/c/ 193485/ 22 which merged in liberty 5 years ago. /github. com/openstack/ neutron/ blob/f8b990736b a91af098e467608 c6dfa0b801ec19c /neutron/ plugins/ ml2/drivers/ agent/_ common_ agent.py# L259-L296
that has not removed the interface form the linux bridge since
https:/
https:/
seting the admin state down simply sets the linkstate down.
if disabling the network which sets the admin state of the network down does something other then set the admin state on all the ports on that netorkdown perhaps there is a race? but if its just setting the port down i dont see how that would cause a loop since that would just set the linkstate down.