yahoo-eng-team team mailing list archive

[Mark McClain <1212462@xxxxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: New => 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/1212462

Title:
  arp fail/martian source

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  openstack grizzly quantum from RDO on redhat 6.4.

  quantum net-list
  +--------------------------------------+-----------+----------------------------------------------------+
  | id                                   | name      | subnets                                            |
  +--------------------------------------+-----------+----------------------------------------------------+
  | xxx3 | demo-net1 | xxxf 10.0.0.0/24   |
  | xxx5 | ext     | xxx9 192.168.0.0/24 |
  | xxx0 | main      | xxxd 10.0.2.0/24   |
  | xxxa | main      | xxx1 10.0.1.0/24   |
  +--------------------------------------+-----------+----------------------------------------------------+

  If I fire up a vm on net xxxa, getting address 10.0.1.4. I then give
  it a floating ip from external, which gets 192.168.0.13

  If I ping 192.168.0.13 it doesn't work. If I leave the ping running,
  then restart l3-agent, after a minute or two, the ping starts working
  and keeps working.

  But after that, if I ctrl-c and restart a new ping, it doesn't work. Digging into it further, there are the following in dmesg for every failed ping:
  martian source 10.0.1.4 from 10.0.1.1, on dev qbrce632e01-80
  ll header: ff:ff:ff:ff:ff:ff:fa:16:3e:02:8a:c3:08:06

  It looks like the arp responses are getting klobbered.

  part of plugin.ini:
  [OVS]
  enable_tunneling=False
  integration_bridge=br-int
  tenant_network_type=vlan
  bridge_mappings=os1:br-os1,ext:br-ext
  network_vlan_ranges=os1:1000:2000,external1

  ext is a provider type flat network attached to br-ext1

  Any ideas what would cause arp to work for a moment during l3-agent
  restart then fail again?

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