yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #75111
[Bug 1751396] Re: DVR: Inter Tenant Traffic between two networks and connected through a shared network not reachable with DVR routers
This bug was fixed in the package neutron - 2:13.0.1-0ubuntu1
---------------
neutron (2:13.0.1-0ubuntu1) cosmic; urgency=medium
* New stable point release for OpenStack Rocky.
* d/p/revert-dvr-add-error-handling.patch: Cherry-picked from upstream to
revert DVR regressions (LP: #1751396)
* d/p/revert-dvr-inter-tenant.patch: Cherry-picked from upstream to revert
DVR regression (LP: #1783654).
-- Corey Bryant <corey.bryant@xxxxxxxxxxxxx> Tue, 02 Oct 2018 17:18:19
-0400
** Changed in: neutron (Ubuntu Cosmic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1751396
Title:
DVR: Inter Tenant Traffic between two networks and connected through a
shared network not reachable with DVR routers
Status in Ubuntu Cloud Archive:
Triaged
Status in Ubuntu Cloud Archive pike series:
Invalid
Status in Ubuntu Cloud Archive queens series:
Triaged
Status in Ubuntu Cloud Archive rocky series:
Triaged
Status in neutron:
Fix Released
Status in neutron package in Ubuntu:
Fix Released
Status in neutron source package in Artful:
Invalid
Status in neutron source package in Bionic:
Triaged
Status in neutron source package in Cosmic:
Fix Released
Bug description:
Inter Tenant Traffic between Two Tenants on two different private
networks connected through a common shared network (created by Admin)
is not route able through DVR routers
Steps to reproduce it:
(NOTE: No external, just shared network)
This is only reproducable in Multinode scenario. ( 1 Controller - 2 compute ).
Make sure that the two VMs are isolated in two different computes.
openstack network create --share shared_net
openstack subnet create shared_net_sn --network shared_net --subnet-
range 172.168.10.0/24
openstack network create net_A
openstack subnet create net_A_sn --network net_A --subnet-range 10.1.0.0/24
openstack network create net_B
openstack subnet create net_B_sn --network net_B --subnet-range 10.2.0.0/24
openstack router create router_A
openstack port create --network=shared_net --fixed-ip subnet=shared_net_sn,ip-address=172.168.10.20 port_router_A_shared_net
openstack router add port router_A port_router_A_shared_net
openstack router add subnet router_A net_A_sn
openstack router create router_B
openstack port create --network=shared_net --fixed-ip subnet=shared_net_sn,ip-address=172.168.10.30 port_router_B_shared_net
openstack router add port router_B port_router_B_shared_net
openstack router add subnet router_B net_B_sn
openstack server create server_A --flavor m1.tiny --image cirros --nic net-id=net_A
openstack server create server_B --flavor m1.tiny --image cirros --nic net-id=net_B
Add static routes to the router.
openstack router set router_A --route destination=10.1.0.0/24,gateway=172.168.10.20
openstack router set router_B --route destination=10.2.0.0/24,gateway=172.168.10.30
```
Ping from one instance to the other times out
Ubuntu SRU details:
-------------------
[Impact]
See above
[Test Case]
Deploy OpenStack with dvr enabled and then follow the steps above.
[Regression Potential]
The patches that are backported have already landed upstream in the corresponding stable branches, helping to minimize any regression potential.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1751396/+subscriptions
References