Instances lose connectivity if 2 shared routers get connected to external network

Bug #1527168 reported by Igor Zinovik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vmware-nsx
Fix Released
Undecided
Unassigned

Bug Description

Version:
NSX Version: 6.1.4, Build: 2691049
Neutron NSX plugin 2015.1.2

Scenario:
a) create external network EXTERNAL_NET
b) create tenant network INTERNAL1
c) create shared router and connect it to external network
d) add interface on router in INTERNAL1 net
e) launch instance and attach it to INTERNAL1
f) check connectivity with host in external network (e.g. 8.8.8.8)
g) create second internal network in same tenant, let it be INTERNAL_NET2 with enabled DHCP
h) create shared router ROUTER2 and set gateway to EXTERNAL_NET
i) add interface in INTERNAL_NET2 to ROUTER2
j) check connectivity with external hosts for INSTANCE1 (e.g. ping 8.8.8.8)

Expected result:
  instance receives ICMP reply packet
Actual result:
  instance does not receive reply packet

commands sequence:
$ neutron net-create EXTERNAL --router:external --shared
$ neutron subnet-create --allocation-pool start=172.16.211.100,end=172.16.211.150 --gateway 172.16.211.1 --disable-dhcp EXTERNAL 172.16.211.0/24

$ neutron net-create INTERNAL_NET1
$ neutron subnet-create INTERNAL_NET1 --name INTERNAL_NET1-subnet 192.168.0.0/24

$ neutron router-create ROUTER1 --router_type shared
$ neutron router-interface-add ROUTER1 INTERNAL_NET1-subnet
$ neutron router-gateway-set ROUTER1 EXTERNAL

$ nova boot --flavor m1.tiny --image TestVM-VMDK --nic net-id=$(neutron net-list|awk '/INTERNAL_NET1/ {print $2}') INSTANCE1

verify connectivity with external host from INSTANCE1 (ping 8.8.8.8)
Got reply.

$ neutron net-create INTERNAL_NET2
$ neutron subnet-create INTERNAL_NET2 --name INTERNAL_NET2-subnet 192.168.1.0/24

$ neutron router-create ROUTER2 --router_type shared
$ neutron router-interface-add ROUTER2 INTERNAL_NET2-subnet
$ neutron router-gateway-set ROUTER2 EXTERNAL

verify connectivity with external host from INSTANCE1 (ping 8.8.8.8)
No reply

Revision history for this message
Igor Zinovik (izinovik) wrote :
Revision history for this message
Igor Zinovik (izinovik) wrote :
Revision history for this message
Gary Kotton (garyk) wrote :

This is resolved with NSX 6.2

Changed in vmware-nsx:
status: New → Fix Committed
Adit Sarfaty (asarfaty)
Changed in vmware-nsx:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.