[Bug 1782517] Re: Failed to recover stopped instance
Radosław Piliszek
1782517 at bugs.launchpad.net
Fri Mar 12 10:18:11 UTC 2021
** Changed in: masakari/victoria
Status: Fix Committed => Fix Released
** Changed in: masakari/ussuri
Status: Fix Committed => Fix Released
** Changed in: masakari/train
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1782517
Title:
Failed to recover stopped instance
Status in Ubuntu Cloud Archive:
New
Status in masakari:
Fix Released
Status in masakari train series:
Fix Released
Status in masakari ussuri series:
Fix Released
Status in masakari victoria series:
Fix Released
Status in masakari wallaby series:
Fix Released
Status in masakari package in Ubuntu:
New
Status in masakari source package in Focal:
New
Status in masakari source package in Groovy:
New
Status in masakari source package in Hirsute:
New
Bug description:
[Error]
Recovering host-failure was failed when there was stopped state instance on the failed host.
As a result, notification status became "failed".
(Instance's vm_state after evacuation became "stopped".)
I used the latest version of masakari.
[Cause of error]
Masakari will try to call stop API after evacuating.
But, evacuate API stops the instance at the end if the original vm_state is stopped.
So 409 error was occurred when masakari called stop API after evacuating.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1782517/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list