Public bug reported: If you are taking a nova-compute service out of service permanently, the logical steps would be:
1) Take down the service 2) Delete it from the service list (nova service-delete <uuid>) However, this does not delete the compute node record which stays forever, leading to the scheduler to always complain about it as well: 2018-09-20 13:15:45.312 131035 WARNING nova.scheduler.host_manager [req- c4a7c383-c606-48a7-b870-cc143710114a 234412d3482f4707877ca696e105bf5b acb15d2ffaae4eda98580c7b874d7f89 - default default] No compute service record found for host <snip>.vexxhost.net https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L716-L720 We should be deleting the compute node if a nova-compute binary is deleted, or that section should automatically clean up while warning (because service records can be rebuilt anyways?) ** Affects: nova Importance: Undecided Status: Invalid -- 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/1793533 Title: Deleting a service with nova-compute binary doesn't remove compute node Status in OpenStack Compute (nova): Invalid Bug description: If you are taking a nova-compute service out of service permanently, the logical steps would be: 1) Take down the service 2) Delete it from the service list (nova service-delete <uuid>) However, this does not delete the compute node record which stays forever, leading to the scheduler to always complain about it as well: 2018-09-20 13:15:45.312 131035 WARNING nova.scheduler.host_manager [req-c4a7c383-c606-48a7-b870-cc143710114a 234412d3482f4707877ca696e105bf5b acb15d2ffaae4eda98580c7b874d7f89 - default default] No compute service record found for host <snip>.vexxhost.net https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L716-L720 We should be deleting the compute node if a nova-compute binary is deleted, or that section should automatically clean up while warning (because service records can be rebuilt anyways?) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1793533/+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
