Target context when setting instance to ERROR when over quota
When conductor does the quota recheck, the instances are created
in a cell but when we update the instance and set it to ERROR state,
we were not targeting the context to the cell that the instance lives
in, which leads to an InstanceNotFound error and then the instance
is stuck in BUILD/scheduling state.
This targets the context to the cell when updating the instance.
Change-Id: I45faffaba4d329433a33cfb5e64c89ce4885df46
Closes-Bug: #1717000
(cherry picked from commit 7e02f02d1501925ddeb15266c05d4d95f852e21a)
Reviewed: https:/ /review. openstack. org/504178 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=9cddde1f977 5847d4b6671595d fc5c4b1bc8e718
Committed: https:/
Submitter: Jenkins
Branch: stable/pike
commit 9cddde1f9775847 d4b6671595dfc5c 4b1bc8e718
Author: Matt Riedemann <email address hidden>
Date: Wed Sep 13 17:30:59 2017 -0400
Target context when setting instance to ERROR when over quota
When conductor does the quota recheck, the instances are created
in a cell but when we update the instance and set it to ERROR state,
we were not targeting the context to the cell that the instance lives
in, which leads to an InstanceNotFound error and then the instance
is stuck in BUILD/scheduling state.
This targets the context to the cell when updating the instance.
Change-Id: I45faffaba4d329 433a33cfb5e64c8 9ce4885df46 ddeb15266c05d4d 95f852e21a)
Closes-Bug: #1717000
(cherry picked from commit 7e02f02d1501925