SR-IOV port cannot be added to a VM if it already has one
Bug #1570400 reported by
Mikhail Chernik
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Confirmed
|
Wishlist
|
Sergey Nikitin | ||
| 9.x |
Won't Fix
|
Wishlist
|
Sergey Nikitin | ||
Bug Description
Environment: MOS 9.0, ISO 192
Detailed bug description
Connecting an instance which was created with SR-IOV port to another SR-IOV port fails and the latter port gets deleted
Steps to reproduce:
1. Create 2 SR-IOV ports
2. Boot a VM using one of these port
3. Try to attach the other port to the VM
Expected result:
port is added, vm has 2 SR-IOV ports
Actual result:
ClientException occurs, the port is deleted
neutron-all.log: http://
nova-compute log: http://
workflow example: http://
| Changed in mos: | |
| milestone: | none → 10.0 |
| milestone: | 10.0 → none |
| Changed in mos: | |
| milestone: | none → 10.0 |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Changed in mos: | |
| assignee: | Elena Ezhova (eezhova) → MOS Nova (mos-nova) |
Revision history for this message
| Roman Podoliaka (rpodolyaka) wrote | #2 |
| tags: | added: enhancement |
| Changed in mos: | |
| importance: | Medium → Wishlist |
| summary: |
- SR-IOV port cannot be added to a VM if it is already has one + SR-IOV port cannot be added to a VM if it already has one |
| tags: | added: 10.0-reviewed |
| Changed in mos: | |
| assignee: | MOS Nova (mos-nova) → Sergey Nikitin (snikitin) |
| no longer affects: | mos/10.0.x |
To post a comment you must log in.
It is currently impossible to attach direct or macvtap type ports to an instance as it requires additional pci device allocation which nova doesn't support. There is a similar bug in nova [1] and a spec [2] which is still on review, so the feature would land in Newton in the best-case scenario.
[1] https:/
[2] https:/