Object versioning is unstable in case of inheritance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Fix Released
|
High
|
Stan Lagun |
Bug Description
Suppose that we deployed an instance of class A which is derived from class B. After the deployment version of the A class is written to the object model for the instance of A. However the version of B (which is a part of A) is chosen according to A's requirements which can be wide enough. So on the next object model load it might happen that another version of B is used for that purpose. It is okay from the A's stand point because this another version still meets the requirements. However the internal state (attribute set) of that another version might be different. Thus that another version might not understand the state produced by its predecessor. Things get even worse considering that it still might be the first version again upon the next model load
Changed in murano: | |
milestone: | none → newton-2 |
importance: | Undecided → High |
Changed in murano: | |
milestone: | newton-2 → newton-3 |
Fix proposed to branch: master /review. openstack. org/341961
Review: https:/