yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #09827
[Bug 1280315] [NEW] nova.compute.manager should take care of dom0 when checking for available instances
Public bug reported:
When using Xen/Libvirt there are WARNING messages that there are 1
instance is available on the hypervisor that was not found in the
database. This 1 instance is the dom0 and that's ok. The check should
ignore the existence of the dom0 and should not count it at all.
# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 8066 48 r----- 12896.2
2014-02-14 15:25:13.437 33401 WARNING nova.compute.manager [-] Found 0 in the database and 1 on the hypervisor.
2014-02-14 15:35:14.229 33401 WARNING nova.compute.manager [-] Found 0 in the database and 1 on the hypervisor.
** Affects: nova
Importance: Undecided
Status: New
--
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/1280315
Title:
nova.compute.manager should take care of dom0 when checking for
available instances
Status in OpenStack Compute (Nova):
New
Bug description:
When using Xen/Libvirt there are WARNING messages that there are 1
instance is available on the hypervisor that was not found in the
database. This 1 instance is the dom0 and that's ok. The check should
ignore the existence of the dom0 and should not count it at all.
# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 8066 48 r----- 12896.2
2014-02-14 15:25:13.437 33401 WARNING nova.compute.manager [-] Found 0 in the database and 1 on the hypervisor.
2014-02-14 15:35:14.229 33401 WARNING nova.compute.manager [-] Found 0 in the database and 1 on the hypervisor.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1280315/+subscriptions
Follow ups
References