[Bug 1782517] Re: Failed to recover stopped instance

[Brian Murray]

Hello Rikimaru, or anyone else affected,

Accepted masakari into groovy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/masakari/10.0.0-0ubuntu2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-groovy

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

** Tags added: verification-needed-focal

-- 
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:
  Fix Committed
Status in masakari source package in Groovy:
  Fix Committed
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]
  For focal:
  Test with an actual juju deployed masakari openstack deployment and ensure the reported bug is fixed on host failure.

  For all other releases the fix can be verified with an LXD container for the corresponding release:
  $ sudo apt install python3-masakari
  $ cd /usr/lib/python3/dist-packages
  $ python3 -m unittest masakari.tests.unit.engine.drivers.taskflow.test_host_failure_flow.HostFailureTestCase.test_host_failure_flow_for_stopped_instances

  The unit test will be successful on a patched deployment and will fail
  with a mismatch error in test_host_failure_flow_for_stopped_instances.

  [Where problems coud occur]
  Any regressions in this fix will likely result in similar failures to what was reported in this bug, resulting in a failure to recover an instance on host failure. The patch is a small, targeted change with a good unit test and the code is unchanged across the backports which helps mitigate regression potential.

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