yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #51078
[Bug 1275675] Re: Version change in ObjectField does not work with back-levelling
This is now over 2 years old and the comments in [1] indicate that this
is the responsibility of "oslo.versionedobjects" now. The ML discussion
[1] doesn't show a clear path forward neither. I'm closing it as "won't
fix".
References:
[1] https://review.openstack.org/#/c/202554/
[2] http://lists.openstack.org/pipermail/openstack-dev/2014-February/026151.html
** Changed in: nova
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1275675
Title:
Version change in ObjectField does not work with back-levelling
Status in OpenStack Compute (nova):
Won't Fix
Status in oslo.versionedobjects:
New
Bug description:
When a NovaObject primitive is deserialized the object version is
checked and an IncompatibleObjectVersion exception is raised if the
serialized primitive is labelled with a version that is not known
locally. The exception indicates what version is known locally, and
the deserialization attempts to backport the primitive to the local
version.
If a NovaObject A has an ObjectField b containing NovaObject B and it
is B that has the incompatible version, the version number in the
exception will be the the locally supported version for B. The
desrialization will then attempt to backport the primitive of object A
to the locally supported version number for object B.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1275675/+subscriptions
References