← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1757495] [NEW] Using dvr and centralized routers in same network fails

 

Public bug reported:

Brief overview and reproducing steps:
1. Create tenant network, let's say 10.3.2.0/24.
2. Create centralized HA router. Attach it at 10.3.2.1
3. Boot VM and ping 10.3.2.1 - works.
4. Create distributed router. Attach it at any free IP, e.g. 10.3.2.5
5. Try to ping 10.3.2.1 from VM - fails. Ping 10.3.2.5 - works.

I can reproduce this consistently. The setup might be a bit of a corner case:
 - deployment with openstack kolla. Openvswitch.
 - openstack pike. neutron 11.0.2
 - tenant provider networks are vlan
 - there are 2 neutron nodes to host HA routers
 - all compute nodes configured for DVR

No errors in logs.
On the compute node hosting the VM, I can see dropped packages on integration bridge br-int.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Using dvr and centralized routers in same network fails

Status in neutron:
  New

Bug description:
  Brief overview and reproducing steps:
  1. Create tenant network, let's say 10.3.2.0/24.
  2. Create centralized HA router. Attach it at 10.3.2.1
  3. Boot VM and ping 10.3.2.1 - works.
  4. Create distributed router. Attach it at any free IP, e.g. 10.3.2.5
  5. Try to ping 10.3.2.1 from VM - fails. Ping 10.3.2.5 - works.

  I can reproduce this consistently. The setup might be a bit of a corner case:
   - deployment with openstack kolla. Openvswitch.
   - openstack pike. neutron 11.0.2
   - tenant provider networks are vlan
   - there are 2 neutron nodes to host HA routers
   - all compute nodes configured for DVR

  No errors in logs.
  On the compute node hosting the VM, I can see dropped packages on integration bridge br-int.

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


Follow ups