security groups are not attached to an instance if port-id is specified during boot
Bug #1373774 reported by
Oleg Bondarev
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Oleg Bondarev |
Bug Description
Creation of server with command
‘nova boot --image <image> --flavor m1.medium --nic port-id=<port-id> --security-groups <sec_grp> <name>’
fails to attach the security group to the port/instance. The response payload has the security group added but only default security group is attached to the instance.
Separate action has to be performed on the instance to add sec_grp, and it is successful. Supplying the same with ‘--nic net-id=<net-id>’ works as expected
Changed in nova: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-2 → 2015.1.0 |
To post a comment you must log in.
Oleg, do you know if this if is falling down in novaclient or on the nova side? I see you have assigned it to yourself, so I'm assuming you are going to dive deeper into this one.