[queens][nova] nova host-evacuate errot
would you like to evacuate a failed compute node or evacuate a running
compute node ?
Il giorno gio 11 lug 2019 alle ore 11:48 Jay See <jayachander.it at gmail.com>
> Hi Ignazio,
> I am trying to evacuate the compute host on older version (mitaka).
> Could please share the process you followed. I am not able to succeed with
> openstack live-migration fails with error message (this is known issue in
> older versions) and nova live-ligration - nothing happens even after
> initiating VM migration. It is almost 4 days.
> On Thu, Jul 11, 2019 at 11:31 AM Ignazio Cassano <ignaziocassano at gmail.com>
>> I am sorry.
>> For simulating an host crash I used a wrong procedure.
>> Using "echo 'c' > /proc/sysrq-trigger" all work fine
>> Il giorno gio 11 lug 2019 alle ore 11:01 Ignazio Cassano <
>> ignaziocassano at gmail.com> ha scritto:
>>> Hello All,
>>> on ocata when I poweroff a node with active instance , doing a nova
>>> host-evacuate works fine
>>> and instances are restartd on an active node.
>>> On queens it does non evacuate instances but nova-api reports for each
>>> instance the following:
>>> 2019-07-11 10:19:54.745 13811 INFO nova.api.openstack.wsgi
>>> [req-daad0a7d-87ce-41bf-b096-a70fc306db5c 0c7a2d6006614fe2b3e81e47377dd2a9
>>> c26f8d35f85547c4add392a221af1aab - default default] HTTP exception thrown:
>>> Cannot 'evacuate' instance e8485a5e-3623-4184-bcce-cafd56fa60b3 while it is
>>> in task_state powering-off
>>> So it poweroff all instance on the failed node but does not start them
>>> on active nodes
>>> What is changed ?
> P *SAVE PAPER â?? Please do not print this e-mail unless absolutely
-------------- next part --------------
An HTML attachment was scrubbed...