← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1502177] [NEW] Existing Ironic instances report negative available RAM for the node after upgrade

 

Public bug reported:

Ironic nodes that have an existing instance will report negative
available RAM after upgrading beyond this commit:
https://github.com/openstack/nova/commit/b99fb0a51c658301188bbc729d1437a9c8b75d00

The node attached to the instance will not have
instance_info[memory_mb], etc, set on the node object in Ironic. This
code causes the driver to report memory_mb_used=memory_mb=0 if this info
is unset. The resource tracker notices that an instance is on that node
and sets memory_mb_used to X (the size of the instance). After which the
node reports (-X) available memory.

This can wreak havoc on tools that look at total available memory. These
could range from capacity reporting tools to scheduler/cells filters. If
more than half of the capacity has instances, the total memory available
will be negative, and could cause things to not schedule properly or
generate alerts.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: liberty-rc-potential

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1502177

Title:
  Existing Ironic instances report negative available RAM for the node
  after upgrade

Status in OpenStack Compute (nova):
  New

Bug description:
  Ironic nodes that have an existing instance will report negative
  available RAM after upgrading beyond this commit:
  https://github.com/openstack/nova/commit/b99fb0a51c658301188bbc729d1437a9c8b75d00

  The node attached to the instance will not have
  instance_info[memory_mb], etc, set on the node object in Ironic. This
  code causes the driver to report memory_mb_used=memory_mb=0 if this
  info is unset. The resource tracker notices that an instance is on
  that node and sets memory_mb_used to X (the size of the instance).
  After which the node reports (-X) available memory.

  This can wreak havoc on tools that look at total available memory.
  These could range from capacity reporting tools to scheduler/cells
  filters. If more than half of the capacity has instances, the total
  memory available will be negative, and could cause things to not
  schedule properly or generate alerts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1502177/+subscriptions


Follow ups