yahoo-eng-team team mailing list archive

[Sridhar Gaddam <sridhar.gaddam@xxxxxxxxxxxx>]

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.

** Changed in: neutron
     Assignee: Sridhar Gaddam (sridhargaddam) => (unassigned)

** Changed in: neutron
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1396310

Title:
  Floating IP status should track router admin_state_up

Status in OpenStack Neutron (virtual network service):
  Opinion

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1396310/+subscriptions