efc27ff84c
In some environments the libvirt nodedev list can become out of sync with the current MAC address assigned to a netdev, As a result the nodedev lookup can fail. This results in an uncaught libvirt exception which breaks the update_available_resource function resultingin an incorrect resource view in the database. e.g. libvirt.libvirtError: Node device not found: no node device with matching name 'net_enp7s0f3v1_ea_60_77_1f_21_50' This change removes the dependency on the nodedev name when looking up nic feature flags. Change-Id: Ibf8dca4bd57b3bddb39955b53cc03564506f5754 Closes-Bug: #1883671
13 lines
625 B
YAML
13 lines
625 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Since the 16.0.0 (Pike) release, nova has collected NIC feature
|
|
flags via libvirt. To look up the NIC feature flags for a whitelisted
|
|
PCI device the nova libvirt driver computed the libvirt nodedev name
|
|
by rendering a format string using the netdev name associated with
|
|
the interface and its current MAC address. In some environments the
|
|
libvirt nodedev list can become out of sync with the current MAC address
|
|
assigned to a netdev and as a result the nodedev look up can fail.
|
|
Nova now uses PCI addresses, rather than MAC addresses, to look up these
|
|
PCI network devices.
|