yahoo-eng-team team mailing list archive

[Carl Baldwin <carl.baldwin@xxxxxx>]

** Changed in: neutron
   Importance: Undecided => Medium

** Changed in: neutron
       Status: In Progress => Invalid

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

Title:
  Floating IP namespace not created when DVR enabled and with IPv6
  enabled in devstack

Status in neutron:
  Invalid

Bug description:
  I just created a new devstack based on the latest Neutron code and the
  l3-agent is failing to create the Floating IP namespace, leading to
  floating IPs not working.  This only happens when DVR is enabled, for
  example, I have this in my local.conf:

  Q_DVR_MODE=dvr_snat

  When I allocate a floating IP and attempt to associate it with a
  running instance I see this in the l3-agent log:

  2015-03-04 20:03:46.082 28696 DEBUG neutron.agent.l3.agent [-] FloatingIP agent gateway port received from the plugin: {u'status': u'DOWN', u'binding:host_id': u'haleyb-devstack', u'name': u'', u'allowed_address_pairs': [], u'admin_state_up': True, u'network_id': u'bda13d78-bf4c-45b8-8cb6-dd3449b1d3c5', u'tenant_id': u'', u'extra_dhcp_opts': [], u'binding:vif_details': {u'port_filter': True, u'ovs_hybrid_plug': True}, u'binding:vif_type': u'ovs', u'device_owner': u'network:floatingip_agent_gateway', u'mac_address': u'fa:16:3e:94:74:f0', u'binding:profile': {}, u'binding:vnic_type': u'normal', u'fixed_ips': [{u'subnet_id': u'99260be2-91ef-423a-8dd8-4ecf15ffb14c', u'ip_address': u'172.24.4.4'}, {u'subnet_id': u'97a9534f-eec4-4c06-bdf5-61bab04455b7', u'ip_address': u'fe80:cafe:cafe::3'}], u'id': u'47f8a65f-6008-4a97-93a3-85f68ea4ff00', u'security_groups': [], u'device_id': u'2674f378-26c0-4b29-b920-5637640acffc'} create_dvr_fip_interfaces /opt/stack/neutron/neutron/agent/l3/agent.py:627
  2015-03-04 20:03:46.082 28696 ERROR neutron.agent.l3.agent [-] Missing subnet/agent_gateway_port

  That error means that no port for the external gateway will be created
  along with the namespace where it lives.

  Subsequent errors confirm that:

  2015-03-04 20:03:47.494 28696 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'fip-bda13d78-bf4c-45b8-8cb6-dd3449b1d3c5', 'ip', '-o', 'link', 'show', 'fpr-d73fd397-4'] create_process /opt/stack/neutron/neutron/agent/linux/utils.py:51
  2015-03-04 20:03:47.668 28696 DEBUG neutron.agent.linux.utils [-]
  Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'fip-bda13d78-bf4c-45b8-8cb6-dd3449b1d3c5', 'ip', '-o', 'link', 'show', 'fpr-d73fd397-4']
  Exit code: 1
  Stdout:
  Stderr: Cannot open network namespace "fip-bda13d78-bf4c-45b8-8cb6-dd3449b1d3c5": No such file or directory

  $ ip netns
  qdhcp-91416e8f-856e-42ae-a9fd-9abe25d8b47a
  snat-d73fd397-47f8-4272-b55a-b33b2307eaad
  qrouter-d73fd397-47f8-4272-b55a-b33b2307eaad

  This is only happening with Kilo, but I don't have an exact date as to
  when it started, just that I noticed it starting yesterday (March
  3rd).

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