yahoo-eng-team team mailing list archive

[sunzuohua <zuohuasun@xxxxxxxxx>]

Public bug reported:

DVR
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.

Reason:

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
"dvr_snat_bound".

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.

https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvr_db.py#L736

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-dvr

** Tags added: l3-dvr

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

Title:
  Centralized floating ip Error status

Status in neutron:
  New

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

  Reason:

  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
  "dvr_snat_bound".

  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.

  https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvr_db.py#L736

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