Author: Hans Lindgren <hanl...@kth.se>
Date: Wed Jun 29 20:29:47 2016 +0200
Do not try to backport when db has older object version
Instance extras are stored as serialized objects in the database and
because of this it is possible to get a version back that is older
than what the client requested. This is in itself not a problem, but
the way we do things right now in conductor we end up trying to
backport to a newer version, which raises InvalidTargetVersion.
This change adds a check to make sure we skip backporting if the
requested version is newer than the actual db version as long as the
major version is the same.
** Changed in: nova
Status: In Progress => Fix Released
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Can't delete instance with numa_topology after upgrading from kilo
Status in OpenStack Compute (nova):
Using the RDO Kilo version of Nova (2015.1.0-3) with dedicated cpu
pinning populates the numa_topology database field with data at
"nova_object.version": "1.1". After upgrading to Liberty a new
instance will be created with a 1.2 object version however already
existing instances created under Kilo remain at 1.1. Attempting to do
many actions on these instances (start, delete) will fail with the
following error: RemoteError: Remote error: InvalidTargetVersion
Invalid target version 1.2.
Updating from Kilo to Mitaka produces the same problem.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp