[Bug 1782517] Re: Failed to recover stopped instance

[Corey Bryant]

** Description changed:

  [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.
+ 
+ == Ubuntu SRU Details below ==
+ [Impact]
+ See above
+ 
+ [Test Case]
+ TBD
+ 
+ [Regression Potential]
+ TBD

** Changed in: cloud-archive/wallaby
       Status: New => Fix Released

** Changed in: masakari (Ubuntu Groovy)
   Importance: Undecided => High

** Changed in: masakari (Ubuntu Groovy)
       Status: New => Triaged

** Changed in: masakari (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: masakari (Ubuntu Focal)
       Status: New => Triaged

** Changed in: cloud-archive/victoria
   Importance: Undecided => High

** Changed in: cloud-archive/victoria
       Status: New => Triaged

** Changed in: cloud-archive/ussuri
   Importance: Undecided => High

** Changed in: cloud-archive/ussuri
       Status: New => Triaged

** Changed in: cloud-archive/train
   Importance: Undecided => High

** Changed in: cloud-archive/train
       Status: New => Triaged

** Changed in: cloud-archive/stein
   Importance: Undecided => High

** Changed in: cloud-archive/stein
       Status: New => Triaged

-- 
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:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Triaged
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in Ubuntu Cloud Archive victoria series:
  Triaged
Status in Ubuntu Cloud Archive wallaby series:
  Fix Released
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:
  Fix Released
Status in masakari source package in Focal:
  Triaged
Status in masakari source package in Groovy:
  Triaged
Status in masakari source package in Hirsute:
  Fix Released

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.

  == Ubuntu SRU Details below ==
  [Impact]
  See above

  [Test Case]
  TBD

  [Regression Potential]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1782517/+subscriptions