yahoo-eng-team team mailing list archive

[venkata anil <anil.venkata@xxxxxxxxxxxx>]

Public bug reported:

floatingip status is not reliable as it is set to active during creation itself [1] rather than waiting for agent [2] to update it once agent finishes adding SNAT/DNAT rules.
[1] https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py#L1234
[2] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/agent.py#L131

User can check floatingip status after creation and can initiate data traffic before agent finishes 
 processing floatingip resulting in connection failures. Also fixing this can help tempest tests to initiate connection only after agent has finished floatingip processing and avoid failures.

Also floatingip status has to be properly updated during migration of
router.

** Affects: neutron
     Importance: Undecided
     Assignee: venkata anil (anil-venkata)
         Status: New


** Tags: l3-dvr-backlog l3-ha

** Changed in: neutron
     Assignee: (unassigned) => venkata anil (anil-venkata)

** Tags added: l3-dvr-backlog l3-ha

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

Title:
  set floatingip status to DOWN during creation

Status in neutron:
  New

Bug description:
  floatingip status is not reliable as it is set to active during creation itself [1] rather than waiting for agent [2] to update it once agent finishes adding SNAT/DNAT rules.
  [1] https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py#L1234
  [2] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/agent.py#L131

  User can check floatingip status after creation and can initiate data traffic before agent finishes 
   processing floatingip resulting in connection failures. Also fixing this can help tempest tests to initiate connection only after agent has finished floatingip processing and avoid failures.

  Also floatingip status has to be properly updated during migration of
  router.

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