yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #73711
[Bug 1757207] Re: compute resource providers not equal to compute nodes in deployment
Shouldn't the upgrade check simply discount deleted compute_nodes ?
+-----------------------------------------------------------------------+
| Check: Resource Providers |
| Result: Warning |
| Details: There are 34 compute resource providers and 40 compute nodes |
| in the deployment. Ideally the number of compute resource |
| providers should equal the number of enabled compute nodes |
| otherwise the cloud may be underutilized. See |
| https://docs.openstack.org/nova/latest/user/placement.html |
| for more details. |
+-----------------------------------------------------------------------+
mysql> select count(*) from compute_nodes;
+----------+
| count(*) |
+----------+
| 40 |
+----------+
1 row in set (0.00 sec)
mysql> select count(*) from compute_nodes where deleted=0;
+----------+
| count(*) |
+----------+
| 34 |
+----------+
1 row in set (0.00 sec)
** Changed in: nova
Status: Expired => Incomplete
--
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/1757207
Title:
compute resource providers not equal to compute nodes in deployment
Status in OpenStack Compute (nova):
Incomplete
Bug description:
Description
===========
When I execute the command `nova-status upgrade check`,
output:
nova-status upgrade check
+----------------------------------------------------------------------+
| Upgrade Check Results |
+----------------------------------------------------------------------+
| Check: Cells v2 |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Placement API |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Resource Providers |
| Result: Warning |
| Details: There are 4 compute resource providers and 15 compute nodes |
| in the deployment. Ideally the number of compute resource |
| providers should equal the number of enabled compute nodes |
| otherwise the cloud may be underutilized. See |
| http://docs.openstack.org/developer/nova/placement.html |
| for more details. |
+----------------------------------------------------------------------+
Steps to reproduce
==================
How to replicate this?
Remove the hosts from the openstack controller:
nova hypervisor-list
nova service-delete {id}
Then run:
su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova
The deleted compute node will be added again as a new node.
run:
nova-status upgrade check
Expected result
===============
No warning when you run:
nova-status upgrade check
Actual result
=============
You can find the warning.
This causes issue with placement of new VM's.
The compute host which was deleted and added again will not be considered during VM scheduling and placement.
Environment
===========
OpenStack Pike release
Neutron Networking which is default.
Logs and Configs
================
Config as the Openstack documentation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1757207/+subscriptions
References