← Back to team overview

yahoo-eng-team team mailing list archive

  1. yahoo-eng-team team
  2. Mailing list archive
  3. Message #37149

[Bug 1487823] [NEW] DVR+LBaasV2- Floating IP down

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

Description of problem:
AIO+Compute setup. LbaasV2+DVR
Floating ip is not going ip after associating it to LB vip. 

When we work with dvr the EXTERNAL (gateway IF) is configured on the
snat ns (when in non dvr it is on qrouter ns)

"
[root@puma07 ~(keystone_admin)]# ip netns
qlbaas-0e804f06-c5f7-42ce-a2a2-dceab1021f32
snat-c7f6851d-981b-4b07-9584-0803d0240b7f      <-------------------
qrouter-c7f6851d-981b-4b07-9584-0803d0240b7f
qdhcp-e2a6b8e4-40de-47e5-9dcd-e66121c5562b
"
When we associate floating ip to LB vip it searches the external IF in the router NS.

associating floating ip to VM (without LB) work fine.


Version-Release number of selected component (if applicable):
python-neutron-fwaas-2015.1.0-3.el7ost.noarch
openstack-neutron-common-2015.1.0-12.el7ost.noarch
python-neutronclient-2.4.0-1.el7ost.noarch
openstack-neutron-2015.1.0-12.el7ost.noarch
python-neutron-lbaas-2015.1.0-5.el7ost.noarch
openstack-neutron-ml2-2015.1.0-12.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-12.el7ost.noarch
openstack-neutron-lbaas-2015.1.0-5.el7ost.noarch
python-neutron-2015.1.0-12.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch


How reproducible:


Steps to Reproduce:
1.configure DVR setup AIO+compute
2. Enable lbaasV2. create load-balacner. 
3.Create FloatingIP and assign it to the LB vip port. 

Actual results:
Floating IP is down due to DVR configuration ( gateway IF is on snat Ns and not on router NS)

Expected results:
Floating IP should be up

I think we should do 1 of the following: 
1. When lbaas configured, the "external IF/port" should be on qrouter ns even if it is a DVR environmet- this means no snat or fip namespaces. If additional VMs will be created and assigned with another FIPs then we should use the snat and fip namespaces. 

or

2. We should use lbaas agent exactly as we are using l3 agent in DVR
environment


logs :
2015-08-19 12:16:00.330 6391 INFO neutron.wsgi [req-beec6448-208f-4f71-88c8-c8ace78dddef ] 10.35.160.23 - - [19/Aug/2015 12:16:00] "PUT /v2.0/floatingips/8087cafc-595a-486a-8e12-7016793cfa70.json HTTP/1.1" 200 584 0.484856
2015-08-19 12:16:00.833 6300 DEBUG neutron.db.l3_dvr_db [req-74e2674c-f5d2-40b8-9187-415daba4bb1b ] FIP Agent : 00fe9d29-5c78-4d82-b018-669b2d3fe622  _process_floating_ips_dvr /usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py:415
2015-08-19 12:16:00.837 6300 DEBUG neutron.db.l3_dvr_db [req-d975570b-f66d-4825-a9dd-f019ed4fa729 ] FIP Agent : 9eb0dae2-90e9-46b5-afab-d4f5c473e74b  _process_floating_ips_dvr /usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py:415
2015-08-19 12:16:01.144 6315 DEBUG neutron.agent.l3.router_info [-] No Interface for floating IPs router: c7f6851d-981b-4b07-9584-0803d0240b7f process_floating_ip_addresses /usr/lib/python2.7/site-packages/neutron/agent/l3/router_info.py:229
2015-08-19 12:16:01.144 6315 DEBUG neutron.agent.l3.agent [-] Sending floating ip statuses: {} update_fip_statuses /usr/lib/python2.7/site-packages/neutron/agent/l3/agent.py:340

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-dvr-backlog lbaas

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

Title:
  DVR+LBaasV2- Floating IP down

Status in neutron:
  New

Bug description:
  Description of problem:
  AIO+Compute setup. LbaasV2+DVR
  Floating ip is not going ip after associating it to LB vip. 

  When we work with dvr the EXTERNAL (gateway IF) is configured on the
  snat ns (when in non dvr it is on qrouter ns)

  "
  [root@puma07 ~(keystone_admin)]# ip netns
  qlbaas-0e804f06-c5f7-42ce-a2a2-dceab1021f32
  snat-c7f6851d-981b-4b07-9584-0803d0240b7f      <-------------------
  qrouter-c7f6851d-981b-4b07-9584-0803d0240b7f
  qdhcp-e2a6b8e4-40de-47e5-9dcd-e66121c5562b
  "
  When we associate floating ip to LB vip it searches the external IF in the router NS.

  associating floating ip to VM (without LB) work fine.

  
  Version-Release number of selected component (if applicable):
  python-neutron-fwaas-2015.1.0-3.el7ost.noarch
  openstack-neutron-common-2015.1.0-12.el7ost.noarch
  python-neutronclient-2.4.0-1.el7ost.noarch
  openstack-neutron-2015.1.0-12.el7ost.noarch
  python-neutron-lbaas-2015.1.0-5.el7ost.noarch
  openstack-neutron-ml2-2015.1.0-12.el7ost.noarch
  openstack-neutron-openvswitch-2015.1.0-12.el7ost.noarch
  openstack-neutron-lbaas-2015.1.0-5.el7ost.noarch
  python-neutron-2015.1.0-12.el7ost.noarch
  openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch


  How reproducible:

  
  Steps to Reproduce:
  1.configure DVR setup AIO+compute
  2. Enable lbaasV2. create load-balacner. 
  3.Create FloatingIP and assign it to the LB vip port. 

  Actual results:
  Floating IP is down due to DVR configuration ( gateway IF is on snat Ns and not on router NS)

  Expected results:
  Floating IP should be up

  I think we should do 1 of the following: 
  1. When lbaas configured, the "external IF/port" should be on qrouter ns even if it is a DVR environmet- this means no snat or fip namespaces. If additional VMs will be created and assigned with another FIPs then we should use the snat and fip namespaces. 

  or

  2. We should use lbaas agent exactly as we are using l3 agent in DVR
  environment


  
  logs :
  2015-08-19 12:16:00.330 6391 INFO neutron.wsgi [req-beec6448-208f-4f71-88c8-c8ace78dddef ] 10.35.160.23 - - [19/Aug/2015 12:16:00] "PUT /v2.0/floatingips/8087cafc-595a-486a-8e12-7016793cfa70.json HTTP/1.1" 200 584 0.484856
  2015-08-19 12:16:00.833 6300 DEBUG neutron.db.l3_dvr_db [req-74e2674c-f5d2-40b8-9187-415daba4bb1b ] FIP Agent : 00fe9d29-5c78-4d82-b018-669b2d3fe622  _process_floating_ips_dvr /usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py:415
  2015-08-19 12:16:00.837 6300 DEBUG neutron.db.l3_dvr_db [req-d975570b-f66d-4825-a9dd-f019ed4fa729 ] FIP Agent : 9eb0dae2-90e9-46b5-afab-d4f5c473e74b  _process_floating_ips_dvr /usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py:415
  2015-08-19 12:16:01.144 6315 DEBUG neutron.agent.l3.router_info [-] No Interface for floating IPs router: c7f6851d-981b-4b07-9584-0803d0240b7f process_floating_ip_addresses /usr/lib/python2.7/site-packages/neutron/agent/l3/router_info.py:229
  2015-08-19 12:16:01.144 6315 DEBUG neutron.agent.l3.agent [-] Sending floating ip statuses: {} update_fip_statuses /usr/lib/python2.7/site-packages/neutron/agent/l3/agent.py:340

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1487823/+subscriptions
  Thread Previous • Date Previous • • Thread Next