Arguably we shouldn't advertise the host-evacuate CLI, and we've talked about deprecating it in the past since it can cause unpredictable problems. See this blog post:
http://www.danplanet.com/blog/2016/03/03/evacuate-in-nova-one-command- to-confuse-us-all/ ** Changed in: nova Status: New => Opinion -- 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/1763039 Title: evacuate instance documentation not mentioning host-evacuate Status in OpenStack Compute (nova): Opinion Bug description: - [X] This is a doc addition request. The current documentation topic "evacuate" in the admin guide is not mentioning the host-evacuate command at all. if one wants to evacuate all instances on a failed host it is easier to use above command. As far as i understand the host-evacuate command will loop over the instances on the failed node and then run each instance against the scheduler so it can be recreated on a different compute node. i suggest to enhance the current documentation with a new section "auto schedule failover host" and move the current part into a section called "manually define failover host". or something like this. ----------------------------------- Release: 17.0.0.0rc2.dev637 on 2018-04-11 13:22 SHA: 80fa0ff912e37890f255bbbcd1c25f26759070ff Source: https://git.openstack.org/cgit/openstack/nova/tree/doc/source/admin/evacuate.rst URL: https://docs.openstack.org/nova/latest/admin/evacuate.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1763039/+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
