There is a DEBUG log coming from the notification sending code path
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.numa_membw_values that are
notorious unset in many circumstances but used in the MetricPayload
we got excessive DEBUG logging from this code path.
This patch removes the offending logging statement as soo far we failed
to found cases based on this log where anything else we could do than
what the code anyhow does, defaulting the payload field to None.
Change-Id: I680e1d9860d839a76e229c4891933872388eb050
Closes-Bug: #1788634
(cherry picked from commit 375632cbc9019f0e4e887afb5d6e48978f2a1a26)
Reviewed: https:/ /review. openstack. org/596264 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=37242807167 03bad54d6dc434b 4b1679243113d9
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 3724280716703ba d54d6dc434b4b16 79243113d9
Author: Balazs Gibizer <email address hidden>
Date: Thu Aug 23 16:57:51 2018 +0200
Remove noisy DEBUG log
There is a DEBUG log coming from the notification sending code path numa_membw_ values that are
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.
notorious unset in many circumstances but used in the MetricPayload
we got excessive DEBUG logging from this code path.
This patch removes the offending logging statement as soo far we failed
to found cases based on this log where anything else we could do than
what the code anyhow does, defaulting the payload field to None.
Change-Id: I680e1d9860d839 a76e229c4891933 872388eb050 e4e887afb5d6e48 978f2a1a26)
Closes-Bug: #1788634
(cherry picked from commit 375632cbc9019f0