Order of port-creation in a VN with multiple subnets is not predictable
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R1.1 |
Fix Committed
|
Critical
|
Sachin Bansal | |||
Trunk |
Fix Committed
|
Critical
|
Sachin Bansal |
Bug Description
Build 1.10 2282 and 1.06 -38 as well.
When VN has multiple subnets, Looks like , the next IP chosen for a new port is chosen from the subnet which was last used using the subnet_id option.
This is unlike stock openstack, where it continues to pick the IP from the first subnet unless specified otherwise (or becomes full)
Create a VN VN1
Create Subnet1 in VN1
neutron port-create VN1 ==> Creates IP in Subnet1
Create Subnet2
neutron port-create VN1 --fixed-ip subnet_
neutron port-create VN1 ==> Creates IP in Subnet2
neutron port-create VN1 --fixed-ip ip_address=<Subnet1 IP> ==> Creates IP in Subnet1
neutron port-create VN1 ==> Creates IP in Subnet2
Create Subnet3
neutron port-create VN1 --fixed-ip subnet_
neutron port-create VN1 ==> Creates IP in Subnet3
Changed in juniperopenstack: | |
importance: | Medium → Critical |
Changed in juniperopenstack: | |
status: | New → In Progress |
https:/ /github. com/Juniper/ contrail- controller/ commit/ 4a4e497b766f9de f1803101c0e34dc ddf4a1bc35