https://review.openstack.org/94474 has to be the issue. It changed the order of when the instance and migration objects were updated, so now the instance is updated first and the migration status is updated second. Tempest is waiting on the instance state change and once it hits that, it does an immediate confirm-resize and fails because the migration status isn't 'finished' yet.
https:/ /review. openstack. org/94474 has to be the issue. It changed the order of when the instance and migration objects were updated, so now the instance is updated first and the migration status is updated second. Tempest is waiting on the instance state change and once it hits that, it does an immediate confirm-resize and fails because the migration status isn't 'finished' yet.