detached instance error on some unit tests
Bug #1096653 reported by
Sean Dague
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Chris Behrens |
Bug Description
Caught in an unrelated change set in the unit tests - http://
It looks like there is another lazy loaded dependent object which is now failing due to the no-db-compute changes.
Changed in nova: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in nova: | |
milestone: | none → grizzly-2 |
Changed in nova: | |
assignee: | Dan Smith (danms) → Chris Behrens (cbehrens) |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
Notes so far:
Actually, it's failing on the "deleted" column, which is neither lazy-loaded nor specific to Instance.
Also, I can reproduce it (seemingly) all the time on my fast machine, and (seemingly) never on a slow one, and in both cases, for full runs and single tests.
It's failing to convert the instance on the outbound side of the RPC call from nova-api, which means that the code making the call is passing some half-baked instance or something, and isn't related to no-db-compute changes, but rather no-db-messaging ones which have been in the tree for quite a while.
I tend to think this is either some race that just got uncovered, or the result of something else changing...