After an instance is created, the flavor could be deleted. But
operations still need to be able to occur against the VM when that
occurs. A new test in Tempest showed that we had been using the
incorrect (and potentially deleted) flavor when a resize/migration was
reverting.
This change updates the code to use the flavor that is stored on the
instance itself.
Reviewed: https:/ /review. openstack. org/311521 /git.openstack. org/cgit/ openstack/ nova-powervm/ commit/ ?id=f98749a2d31 54452d8edb8c0e9 5b54f5cde579d1
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit f98749a2d315445 2d8edb8c0e95b54 f5cde579d1
Author: Drew Thorstensen <email address hidden>
Date: Fri Apr 29 10:12:33 2016 -0500
Fix revert migration if flavor deleted
After an instance is created, the flavor could be deleted. But
operations still need to be able to occur against the VM when that
occurs. A new test in Tempest showed that we had been using the
incorrect (and potentially deleted) flavor when a resize/migration was
reverting.
This change updates the code to use the flavor that is stored on the
instance itself.
Change-Id: I16254d8eb74a72 4e3e0a538f47259 e9627c4233a e2dd4a492f65d42 6f8b091e1f) powervm/ tests/virt/ powervm/ test_driver. py
Closes-Bug: 1570748
(cherry picked from commit e72a505860b2f7c
Conflicts:
nova_