Floating IP status should track router admin_state_up

[Yair Fried]

Setting router admin_state_up=False disables router and thus connectivity to all floating IPs routed through it, yet the status of the floating ip remains "ACTIVE".

How to reproduce:
1. create a VM attached external network via router
2. attach floating IP to VM
3. update router admin_state_up = False
4. ping floating IP (assuming secgroup allows it)
5. check floating IP's status

status should be DOWN, but it's still ACTIVE

[Sridhar Gaddam (sridhargaddam)]

Hello Yair,

Related to the same topic (i.e., admin_state_up attribute), there was some previous discussion [1], but without any proper conclusion.
IMO it would be good to receive some feedback about the expected behavior, before we can proceed with any patch.

Marking the current bug status to Opinion, to get feedback about the expected behavior.

[1] - https://bugs.launchpad.net/neutron/+bug/1237807
Related - http://openstack.10931.n7.nabble.com/Neutron-set-network-admin-state-up-to-false-td32080.html

--Sridhar.

[Sridhar Gaddam (sridhargaddam)]

Yair, I just added some of the Neutron Cores for their opinion on this issue. Would be nice to get their views on this topic.

[Armando Migliaccio (armando-migliaccio)]

I expressed my opinion here:

https://review.openstack.org/#/c/106620/5/tempest/scenario/test_network_basic_ops.py