instance_type data cannot be extracted from sys_meta after instance deleted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Chris Behrens | ||
Grizzly |
Fix Released
|
Critical
|
Chris Behrens |
Bug Description
This commit:
---
commit 17bca438954638d
Author: Joe Gordon <email address hidden>
Date: Wed Mar 13 16:58:13 2013 -0700
Delete InstanceSystemM
Thanks to no-db-compute only pre-delete instance data is used in
notifications. So now we can go back to deleting InstanceSystemM
when an instance is deleted.
Fixes bug 1153827
Change-Id: Ic66b998cde2a15
---
Changed things so that we delete the instance_
1) The API. If you specify 'changes-since', the API will return deleted instances. The instance_type data needs to be extracted in order to form the API response
2) _usage_audit_log() task in compute manager. This task potentially queries for deleted instances in the past day to send audit information for them nightly.
I don't have a traceback for #1 handy, but:
Traceback for #2:
Traceback (most recent call last):
File "/meow/
File "/meow/
system_
File "/meow/
return func(*args, **kwargs)
File "/meow/
system_
File "/meow/
network_info, system_metadata, **extra_usage_info)
File "/meow/
File "/meow/
instance_
KeyError: 'instance_
Changed in nova: | |
importance: | Undecided → Critical |
milestone: | none → havana-2 |
milestone: | havana-2 → havana-1 |
tags: | added: db |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
milestone: | havana-2 → havana-1 |
Changed in nova: | |
assignee: | nobody → Chris Behrens (cbehrens) |
Changed in nova: | |
status: | Confirmed → In Progress |
tags: | added: grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
Pushing back to H2, please set back to H1 if this is milestone-critical (in which case the fix needs to land in master first and then be backported to milestone-proposed before tomorrow)