Verified on Ubuntu 26.04 LTS (Resolute), amd64, with two Nova compute hosts. All ten steps of the SRU test plan were followed.
With release version 21.0.0-0ubuntu1, the injected Nova HTTP 503 reproduced the bug: the notification finished, the instance was not evacuated, and its vmove remained pending without start/end timestamps. After upgrading the four Masakari runtime packages to 21.0.0-0ubuntu1.1 from resolute-proposed, the same fault produced a failed notification and failed vmoves with end times and error messages. No vmoves remained pending. After removing the fault, normal evacuation succeeded: notification finished, vmove succeeded, instance ACTIVE and running under libvirt on the second compute, and Neutron port ACTIVE and bound there. Both computes were restored to up/enabled; Apache and masakari-engine were active, and dpkg --audit was clean. Verification passed for Resolute. Attached evidence.log contains the step-by-step results, package provenance and full runtime output. ** Attachment added: "evidence.log" https://bugs.launchpad.net/masakari/+bug/2158101/+attachment/6000280/+files/evidence.log ** Tags removed: verification-needed-resolute ** Tags added: verification-done-resolute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2158101 Title: [SRU] Masakari marks host recovery finished with pending VM moves after Nova or Keystone API failure To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/caracal/+bug/2158101/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
