Don't emit warning when ironic properties are zero
If an ironic node is registered without either of the 'memory_mb' or
'cpus' properties, the following warning messages are seen in the
nova-compute logs:
Warning, memory usage is 0 for <instance> on baremetal node <node>.
Warning, number of cpus is 0 for <instance> on baremetal node <node>.
As of the Stein release [1], the standard compute resources (VCPU,
MEMORY_MB, DISK_GB) are not registered with placement for ironic nodes.
They were not required to be set since the Pike release, but still this
warning is emitted.
NOTE(mriedem): The original commit message on this change incorrectly
said that [1] was made in Rocky but it was actually made in Stein.
The important part is that the "memory_mb" and "cpus" properties on
the node could be 0 since Pike and if they are 0, it just means
that the related standard resource class inventory is not reported
to the placement service and thus the warnings are noise.
Change-Id: I342b9b12ec869431c3abad75eb8194c34151a281
Closes-Bug: #1794773
(cherry picked from commit 63b9c88386998bc584786ecb8ea7a2aae971a384)
(cherry picked from commit 0794345ecd1d61efb7a0d321eb32844d2dd684d0)
Reviewed: https:/ /review. openstack. org/608611 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=e46019a6e52 452554b85f5c40a 6e4b069172cd9a
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit e46019a6e524525 54b85f5c40a6e4b 069172cd9a
Author: Mark Goddard <email address hidden>
Date: Thu Sep 27 15:32:36 2018 +0100
Don't emit warning when ironic properties are zero
If an ironic node is registered without either of the 'memory_mb' or
'cpus' properties, the following warning messages are seen in the
nova-compute logs:
Warning, memory usage is 0 for <instance> on baremetal node <node>.
Warning, number of cpus is 0 for <instance> on baremetal node <node>.
As of the Stein release [1], the standard compute resources (VCPU,
MEMORY_MB, DISK_GB) are not registered with placement for ironic nodes.
They were not required to be set since the Pike release, but still this
warning is emitted.
This change removes these warning messages.
Backport: rocky, queens, pike
[1] https:/ /review. openstack. org/#/c/ 565841/
NOTE(mriedem): The original commit message on this change incorrectly
said that [1] was made in Rocky but it was actually made in Stein.
The important part is that the "memory_mb" and "cpus" properties on
the node could be 0 since Pike and if they are 0, it just means
that the related standard resource class inventory is not reported
to the placement service and thus the warnings are noise.
Change-Id: I342b9b12ec8694 31c3abad75eb819 4c34151a281 584786ecb8ea7a2 aae971a384) fb7a0d321eb3284 4d2dd684d0)
Closes-Bug: #1794773
(cherry picked from commit 63b9c88386998bc
(cherry picked from commit 0794345ecd1d61e