No logs if scheduling fails due to pages requirements
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
On a customer's environment with the NUMATopologyFilter enabled, when trying to create an instance using a flavor which has these properties:
aggregate_
aggregate_
hw:cpu_
hw:cpu_
hw:cpu_sockets='1'
hw:cpu_
hw:emulator_
hw:mem_
hw:numa_nodes='1'
hw:pmu='False'
we are getting "No valid hosts found" fault eventually on the openstack server show output. Letting aside why this is happening, I'd like to report an improvement which could be done to the NUMATopologyFil
With debug logging enabled, this is a piece of the scheduler's log:
2021-10-14 15:23:08.047 34021 DEBUG nova.virt.hardware [...] Attempting to fit instance cell InstanceNUMACel
2021-10-14 15:23:08.048 34021 DEBUG nova.virt.hardware [...] Attempting to fit instance cell InstanceNUMACel
2021-10-14 15:23:08.048 34021 DEBUG nova.scheduler.
I've redacted some parts for privacy and some other for clarity. Those messages are repeated for each compute tested.
The issue is that there's no indication of why the VM doesn't fit on the host.
Looking at the code I narrowed it down to the numa_fit_
I think it might be useful to get this information to the logs to ease on the debugging of the filter's working (as it is done for other reasons of the instance not passing the filter).
tags: | added: logging scheduler |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |