Reviewed: https://review.openstack.org/604495 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3e902313e9c3117e76d6adf88a2f104bc229374c Submitter: Zuul Branch: master
commit 3e902313e9c3117e76d6adf88a2f104bc229374c Author: imacdonn <iain.macdonn...@oracle.com> Date: Sat Sep 22 00:55:36 2018 +0000 nova-status - don't count deleted compute_nodes When counting rows in the compute_nodes table to compare against resource records, those which have been marked as deleted should not be counted, otherwise the result is artificially high. Change-Id: Ia3fbb9c46c15826fc363286ce48984f59cbe1e62 Closes-Bug: #1757207 ** Changed in: nova Status: In Progress => Fix Released -- 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): Fix Released Status in OpenStack Compute (nova) pike series: Confirmed Status in OpenStack Compute (nova) queens series: Confirmed Status in OpenStack Compute (nova) rocky series: Confirmed 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp