Order of port-creation in a VN with multiple subnets is not predictable

Bug #1352301 reported by Vedamurthy Joshi
6
This bug affects 1 person
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_id=<Subnet2_id> ==> Creates IP in Subnet2

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_id=<Subnet3_id> ==> Creates IP in Subnet3

neutron port-create VN1 ==> Creates IP in Subnet3

Raj Reddy (rajreddy)
Changed in juniperopenstack:
importance: Medium → Critical
Sachin Bansal (sbansal)
Changed in juniperopenstack:
status: New → In Progress
Revision history for this message
Sachin Bansal (sbansal) wrote :
Changed in juniperopenstack:
status: In Progress → Fix Committed
Revision history for this message
Nagabhushana R (bhushana) wrote :

bug was raised before 1.1 branch was cut, the checkin URL points to r1.1, please update with the mainline commit information and move the PR appropriately.

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.