2b447b7236
The PciPassthroughFilter logic checks each InstancePCIRequest individually against the available PCI pools of a given host and given boot request. So it is possible that the scheduler accepts a host that has a single PCI device available even if two devices are requested for a single instance via two separate PCI aliases. Then the PCI claim on the compute detects this but does not stop the boot just logs an ERROR. This results in the instance booted without any PCI device. This patch does two things: 1) changes the PCI claim to fail with an exception and trigger a re-schedule instead of just logging an ERROR. 2) change the PciDeviceStats.support_requests that is called during scheduling to not just filter pools for individual requests but also consume the request from the pool within the scope of a single boot request. The fix in #2) would not be enough alone as two parallel scheduling request could race for a single device on the same host. #1) is the ultimate place where we consume devices under a compute global lock so we need the fix there too. Closes-Bug: #1986838 Change-Id: Iea477be57ae4e95dfc03acc9368f31d4be895343
9 lines
358 B
YAML
9 lines
358 B
YAML
---
|
|
fixes:
|
|
- |
|
|
`Bug #1986838 <https://bugs.launchpad.net/nova/+bug/1986838>`_: Nova now
|
|
correctly schedules an instance that requests multiple PCI devices via
|
|
multiple PCI aliases in the flavor extra_spec when multiple similar devices
|
|
are requested but the compute host has only one such device matching with
|
|
each request individually.
|