Contrail port-list does not have fixed-ips based filtering
Bug #1371035 reported by
Babu Shanmugam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
Undecided
|
Unassigned | ||
R1.1 |
In Progress
|
Undecided
|
Babu Shanmugam | ||
OpenContrail |
Fix Committed
|
Undecided
|
Babu Shanmugam |
Bug Description
While nova validates the network when creating an instance, there is a problem when a second instance is created with a v4-fixed-ip
Steps to reproduce -
1. Create a test-net
2. Create a subnet for test-net
3. Boot an instance with nic-id=test-net
4. Boot another instance with nic-id=
5. Step 4 will fail, which it should not.
Changed in opencontrail: | |
assignee: | nobody → Babu Shanmugam (anbu-p) |
status: | New → In Progress |
Changed in opencontrail: | |
status: | In Progress → Fix Released |
status: | Fix Released → Fix Committed |
tags: | added: neutronapi |
To post a comment you must log in.
Babu,
This is what i tried. But it seemed to get created fine. Am i missing anything ?
neutron net-create test-net 4b6eab13- 69f3-408e- 8cfc-0a19802d9d 92 test_vm1 ( creates 20.1.1.2) 4b6eab13- 69f3-408e- 8cfc-0a19802d9d 92,v4-fixed- ip=20.1. 1.10 test_vm2
neutron subnet-create test-net 20.1.1.0/24
nova boot --flavor 2 --image $image_id --nic net-id=
nova boot --flavor 2 --image $image_id --nic net-id=
root@nodec22:~# nova list |grep test-net 0a8d-48b9- b797-02ff21c351 49 | test_vm1 | ACTIVE | None | Running | test-net=20.1.1.2 | bdf2-41c2- b782-90353e271b e8 | test_vm2 | ACTIVE | None | Running | test-net=20.1.1.10 |
| 01cfb703-
| 466fc134-
root@nodec22:~#