Core plugin: VMWare
This scenario is checked in icehouse release.
Build used:
===========
neutron-common : 1:2014.1-0ubuntu1~cloud0
neutron-dhcp-agent : 1:2014.1-0ubuntu1~cloud0
neutron-l3-agent : 1:2014.1-0ubuntu1~cloud0
neutron-metadata-agent :1:2014.1-0ubuntu1~cloud0
neutron-plugin-ml2 :1:2014.1-0ubuntu1~cloud0
neutron-plugin-nicira : 1:2014.1-0ubuntu1~cloud0
neutron-plugin-vmware : 1:2014.1-0ubuntu1~cloud0
neutron-server: 1:2014.1-0ubuntu1~cloud0
python-neutron: 1:2014.1-0ubuntu1~cloud0
python-neutronclient : 2:2.3.4.46.g07bcee8+git201404070301~trusty-0ubuntu1
Steps performed:
================
1. Through network horizon, create one network with one subnet. name of this subnet is "subnet1" and his network address is 85.85.85.0/24
2. attached this subnet to router's interface.
3. Now through horizon, create second subnet for that network. His name is "subnet2" and his network address is 95.95.95.0/24.
4. try to attached this subnet to router's interface.
Observed behavior:
=================
1. Unable to connect multiple subnets of same network to one router. Only one subnet we can attached to router's interface.
2. Error will come when we try to add second subnet of same network to router.
(please refer attached screen shot for reference )
3. We can attached these subnets to two different routers.
What is the underlying stacktrace? As far as I can tell this should be possible with the NSX plugin and I suspect there is some odd failure behind.
Having said that, it does not make a great deal of sense to have two subnets belonging to the same logical network, let alone uplinking them to the same router (again, when they belong to the same L2 network).
This Tempest change does in fact alter the API test that does what you were doing via the GUI.
https:/
The 3rd CI for VMware NSX pass with or without this change so I think this bug is invalid.