Noisy DEBUG log: Defaulting the value of the field 'numa_membw_values' to None in MetricPayload
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Balazs Gibizer | ||
Queens |
Fix Committed
|
Low
|
Elod Illes | ||
Rocky |
Fix Committed
|
Low
|
Elod Illes |
Bug Description
There are plenty of similar DEBUG log is visible in the nova log:
DEBUG nova.notificati
This logs coming from the notification sending code path [1] that tries to populate the notification payload from a nova OVO and encounters an unset / non-lazy loadable field in the source OVO.
As there are fields like MonitorMetric.
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
assignee: | nobody → Balazs Gibizer (balazs-gibizer) |
tags: | added: notifications |
As near as I can tell, numa_membw_values is never set. Maybe in some out-of-tree monitor? But it's certainly not set in https:/ /github. com/openstack/ nova/blob/ cccba02be8dda03 50a215de78b0acd e3dbf19716/ nova/compute/ monitors/ cpu/virt_ driver. py#L42 which is where I'd expect it.