Public bug reported:
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.
** Affects: nova
Importance: Undecided
Status: New
--
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/1596119
Title:
Can't delete instance with numa_topology after upgrading from kilo
Status in OpenStack Compute (nova):
New
Bug description:
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:
https://bugs.launchpad.net/nova/+bug/1596119/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
