Can't update MAC address for direct-physical ports
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
High
|
MOS Maintenance | ||
Bug Description
Booting a guest with a neutron port of type 'direct-physical' will cause nova to allocate a PCI passthrough device for the port. The MAC address of the PCI passthrough device in the guest is not a virtual MAC address (fa:16:...) but the MAC address of the physical device since the full device is allocated to the guest (compared to SR-IOV where a virtual MAC address is arbitrarily chosen for the port).
When resizing the guest (to another flavor), nova will allocate a new PCI device for the guest. After the resize, the guest will be bound to another PCI device which has a different MAC address. However the MAC address on the neutron port is not updated, causing DHCP to not work because the MAC address is unknown.
The same issue can be observed when migrating a guest to another host.
See earlier bug filed at https:/
| tags: | added: customer-found |
| description: | updated |
| Changed in fuel: | |
| milestone: | none → 9.2-mu-11 |
| assignee: | nobody → MOS Maintenance (mos-maintenance) |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Denis Meltsaykin (dmeltsaykin) wrote | #1 |
| Changed in fuel: | |
| milestone: | 9.2-mu-11 → 9.x-updates |
| status: | Confirmed → Invalid |
Moving to Invalid. The request was for Pike, not Mitaka.