Security groups not set when port instead of network selected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Using 3:11.0.
When creating an instance with the horizon web interface, pre-create some ports mapped to floating ips. When creating an instance select a port instead of the network. Select some security group and launch instance. When instance is created there are no selected security groups, only the default one.
Steps to reproduce:
1) create a network port associated to a floating ip with newtron
2) go to horizon
3) create instance
4) select a network port already mapped instead of a network
5) select your security groups and associate them to the instance
6) launch instance.
Behavior:
The instance spawns up correctly but the security groups are not there, only the default one.
Expected behavior:
Security group in spawned instance should be the one selected during creation.
If all steps are followed but a network instead of a port is selected, the security groups are saved correctly.
This is the intentional behavior of nova API.
When you see the list of request parameters of create-server API [1], the description of "networks.port" field says "Requested security groups are not applied to pre-existing ports."
[1] https:/ /developer. openstack. org/api- ref/compute/ #create- server