On revert_resize(), the migration context was dropped hence setting it
to None. The problem is that the migration context is needed when
executing finish_revert_resize() so that the neutron port can be updated
with the right binding profile.
This patch moves the instance.drop_migration_context() call out from the
resource tracker so that the migration context can be dropped at the
appropriate times: after RT.drop_move_claim() is called in the compute
manager's confirm_resize() call and after the virt driver's
finish_revert_resize() in the compute manager's finish_revert_resize()
call.
Reviewed: https:/ /review. openstack. org/349060 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=2f073fd8df4 da9d828f4d36357 dbf6605ad3dcb1
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2f073fd8df4da9d 828f4d36357dbf6 605ad3dcb1
Author: Ludovic Beliveau <email address hidden>
Date: Fri Jul 29 11:51:47 2016 -0400
Fix drop_move_claim() on revert resize
On revert_resize(), the migration context was dropped hence setting it revert_ resize( ) so that the neutron port can be updated
to None. The problem is that the migration context is needed when
executing finish_
with the right binding profile.
This patch moves the instance. drop_migration_ context( ) call out from the move_claim( ) is called in the compute revert_ resize( ) in the compute manager's finish_ revert_ resize( )
resource tracker so that the migration context can be dropped at the
appropriate times: after RT.drop_
manager's confirm_resize() call and after the virt driver's
finish_
call.
Change-Id: I1b7b2573de4380 576dd8b801ed59d 8955b0ab72a
Partial-bug: #1512880