sync_power_states fails because it queries for deleted instances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Dan Prince |
Bug Description
Using the latest Nova Grizzly nova code (a2f260f). I'm seeing the following Exception in /var/log/
2013-01-07 12:23:15 ERROR nova.manager [req-73d075a9-
2013-01-07 12:23:15 27683 TRACE nova.manager Traceback (most recent call last):
2013-01-07 12:23:15 27683 TRACE nova.manager File "/usr/lib/
2013-01-07 12:23:15 27683 TRACE nova.manager task(self, context)
2013-01-07 12:23:15 27683 TRACE nova.manager File "/usr/lib/
2013-01-07 12:23:15 27683 TRACE nova.manager db_instance[
2013-01-07 12:23:15 27683 TRACE nova.manager File "/usr/lib/
2013-01-07 12:23:15 27683 TRACE nova.manager return self._manager.
2013-01-07 12:23:15 27683 TRACE nova.manager File "/usr/lib/
2013-01-07 12:23:15 27683 TRACE nova.manager raise (e._exc_info[1], None, e._exc_info[2])
2013-01-07 12:23:15 27683 TRACE nova.manager InstanceNotFound: Instance 5aadd494-
----
The issue seems to be that in commit (d22b0ca2402d96
Previously the calls ultimately use the DB API's query_model call which used the context to determine whether deleted records should be used.
We either need to:
-update the new calls to use the context for backwards compatability with the old function.
-update the new calls to explicitly pass 'deleted' in all the cases that they should (sync_power_states would need to do this for example)
Changed in nova: | |
importance: | Undecided → Critical |
status: | New → In Progress |
assignee: | nobody → Dan Prince (dan-prince) |
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
Fix proposed to branch: master /review. openstack. org/19113
Review: https:/