Manually assign --device and --device-owner to a port does NOT binds the port inmediatly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
Medium
|
Pierre Libeau |
Bug Description
This could be considered as a documentation bug.
When a VM is created (there is a device ID), a user can create a port and assign the port device_id to the VM ID and the device_
$ openstack port list --server serverID
The port is not bound, of course. But when the VM is rebooted (hard reboot), the port is assigned and bound to this VM.
There is another related issue from the administrator point of view. A user can assign (by mistake or coincidence) the device ID of another project VM ID. This non-admin user can't see the other project VM. But the administrator, when executing the previous command, will see a VM assigned to a project with a port from another. This scenario:
* Is difficult to reproduce: the non-admin user must guess the VM ID of another project without having access.
* Affect only to the admin view, who can access to both projects.
tags: | added: doc |
Changed in neutron: | |
importance: | Undecided → Medium |
Changed in neutron: | |
assignee: | nobody → Pierre Libeau (pierre-libeau) |
NOTE: terraform [1] also allows to define the device_id of a port. In any case, that should be commented in this tool (or disallowed).
[1]https:/ /registry. terraform. io/providers/ terraform- provider- openstack/ openstack/ latest/ docs/resources/ networking_ port_v2# device_ id