As seen in I2717274bb1bd370870acbf58c03dc59cee30cc5e, if an operator deletes a nova-compute service via the API but fails to stop the actual nova-compute process, the API will delete the services table and compute_nodes table records, but the nova-compute process will hit the 'update_available_resource' periodic task and re-create the compute node record, which at that point is orphaned since it does not have an associated nova-compute service. Restarting the nova-compute service _should_ recreate the service table record for that host and then the user could attempt to delete the service and compute node record again via this API, but it's better to not have to find this out the hard way. So this change adds a simple reminder that the nova-compute process on the host should be stopped before deleting the compute service. While in here, the link to the install guide about the various compute services is also fixed. Change-Id: I68f2074814c3ae890888a5c75fd2870bb99f0e08 Related-Bug: #1646255
8.5 KiB
8.5 KiB