Public bug reported: 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. ** Affects: nova Importance: Undecided Status: New ** Tags: nova-manage placement ** Tags added: neutron ** Tags added: nova-manage ** Tags removed: neutron ** Description changed: 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. | +----------------------------------------------------------------------+ 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 You can find this warning. This causes issue with placement of new VM's. - The deleted compute host will not be considered during VM scheduling and placement. + The compute host which was deleted and added again will not be considered during VM scheduling and placement. ** Description changed: 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 - You can find this warning. + 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. -- 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): New 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
