Bulk port creation with supplied security group also adds default security group
Bug #1842666 reported by
Nate Johnston
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Nate Johnston |
Bug Description
When bulk ports are created with a security group supplied, the resulting port(s) should only have that security group assigned. But the resulting ports are getting both the requested security group as well as the tenant default security group assigned.
tags: | added: neutron-proactive-backport-potential |
To post a comment you must log in.
Indeed, reproduced it on devstack master with:
$ cat bulk_secgroups.json 753b-46d3- 8636-5ad226297a b0", security_ groups" : ["91e47ea5- 3d9c-437b- a31e-0a2fd8d318 1f"]
{
"ports": [
{
"network_id": "226ac6be-
"
}
]
}
$ export MY_TOKEN= $(openstack token issue -c id -f value) 127.0.0. 1:9696/ v2.0/ports -d @bulk_secgroups .json | jq .ports[0].id 4d9c-4a8b- b5d1-55769c4c75 c2" 4d9c-4a8b- b5d1-55769c4c75 c2|grep security_group 3d9c-437b- a31e-0a2fd8d318 1f, fc3f8c84- 118e-46c5- 8dc7-18d02ef926 af 118e-46c5- 8dc7-18d02ef926 af
$ curl -H "X-Auth-Token: $MY_TOKEN" -X POST http://
"91ec92c1-
openstack port show 91ec92c1-
| security_group_ids | 91e47ea5-
$ openstack security group show default -f value -c id
fc3f8c84-