Submitter: Zuul
Branch:    master

commit 477d4135ba079b0239a3e4f24c92ae3b7742e537
Author: Swaminathan Vasudevan <>
Date:   Wed Jan 10 14:45:29 2018 -0800

    DVR: Fix dvr_no_external agent restart with fips
    Centralized floating IP return to Error state when
    the 'dvr_no_external' agent restarts.
    The sync data received from the server was not handling
    the agent properly and so was not update the 'dvr_snat_bound'
    This would initiate an floating IP Error state.
    This patch will fix the issue mentioned above.
    Closes-Bug: #1741411
    Change-Id: Id1cf26ffba8262ba7b3e5f41faa4cb28ba9dcb7d

** Changed in: neutron
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.

  Centralized floating ip Error status

Status in neutron:
  Fix Released

Bug description:
  l3 agent mode on network nodes : dvr_snat
  l3 agent mode on compute nodes : dvr_no_external

  Reproduction steps:

  1.Create a dvr.
  2.Create a vm and associate a floating ip.
  3.Restart l3 agent on the compute node which hosting the vm or add a new 
interface to the router.
  4.The floating ip status becomes error.


  When l3 agent gets dvr info from server

  1) If the agent mode is "dvr_snat", the value of "host" for the fip
  will be "FLOATING_IP_HOST_NEEDS_BINDING and the value of
  "dvr_snat_bound" will be "True".

  2) If the agent mode is not "dvr_snat", the value of "host" for the
  fip will be the real host that hosting the vm and there is not

  Then l3 agents on the compute nodes will get dvr infos including
  centralized floating ips and try to config them in fip ns. But the
  agent mode on compute node is "dvr_no_external" and there is no fip
  ns, so the agent will fail to config the fips.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to