NovaObject does not properly honor VERSION
Bug #1239709 reported by
Dan Smith
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Dan Smith | ||
Havana |
Fix Released
|
High
|
Dan Smith |
Bug Description
The base object infrastructure has been comparing Object.version instead of the Object.VERSION that *all* the objects have been setting and incrementing when changes have been made. Since the base object defined a .version, and that was used to determine the actual version of an object, all objects defining a different VERSION were ignored.
All systems in the wild currently running broken code are sending version '1.0' for all of their objects. The fix is to change the base object infrastructure to properly examine, compare and send Object.VERSION.
Impact should be minimal at this point, but getting systems patched as soon as possible will be important going forward.
tags: | added: havana-backport-potential |
Changed in nova: | |
status: | Fix Committed → Fix Released |
tags: | removed: havana-backport-potential in-stable-havana |
Changed in nova: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/51615
Review: https:/