migration 153 creates deleted=NULL columns
Bug #1147839 reported by
Chris Behrens
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Chris Behrens |
Bug Description
Migration 153 adds system_metadata for every instance... containing a copy of the instance_type. However, it doesn't create entries with 'deleted' set.... so they default to NULL in mysql. deleted should be explicitly set to 0, instead.
When instance_get* joins system_metadata, all of these new entries are not there, because NULL does not match deleted=0 when joining.
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → grizzly-rc1 |
Changed in nova: | |
assignee: | nobody → Chris Behrens (cbehrens) |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/23627
Review: https:/