You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If anything fails and raises an exception during
confirm_resize, the migration status is stuck in
"confirming" status even though the instance status
may be "ERROR".
This change adds the errors_out_migration decorator
to the confirm_resize method to make sure the migration
status is "error" if an error is raised.
In bug 1821594 it was the driver.confirm_migration
method that raised some exception, so a unit test is
added here which simulates a similar scenario.
This only partially closes the bug because we are still
leaking allocations on the source node resource provider
since _delete_allocation_after_move is not called. That
will be dealt with in a separate patch.
Conflicts:
nova/tests/functional/test_servers.py
nova/tests/unit/compute/test_compute_mgr.py
NOTE(mriedem): The functional test conflict is due to not
having change I99427a52676826990d2a2ffc82cf30ad945b939c
in Rocky. The unit test conflict is due to not having
change I0851e2d54a1fdc82fe3291fb7e286e790f121e92 in Rocky.
The source_node attribute on the fake Migration object in
the unit test is added here because change
I312d61383345ea0ac1ab0c277b4c468e6aa94656 is not in Rocky.
Change-Id: Ic7d78ad43a2bad7f932c22c98944accbbed9e9e2
Partial-Bug: #1821594
(cherry picked from commit 408ef8f)
(cherry picked from commit 972d4e0)
0 commit comments