[Bug 1782517] Re: Failed to recover stopped instance

[Billy Olsen]

** Also affects: masakari (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: masakari (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: masakari (Ubuntu Groovy)
   Importance: Undecided
       Status: New

** Also affects: masakari (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to masakari in Ubuntu.
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 Committed
Status in masakari ussuri series:
  Fix Committed
Status in masakari victoria series:
  Fix Committed
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