Reviewed: https://review.openstack.org/427319 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=29f3d8bae23750ec53b59a258eb71459e6972927 Submitter: Jenkins Branch: master
commit 29f3d8bae23750ec53b59a258eb71459e6972927 Author: Chris Dent <[email protected]> Date: Tue Jan 31 17:25:11 2017 +0000 Fresh resource provider in RT must have generation 0 When the resource tracker creates a new resource provider it sets the generation to 1. This is wrong, because on the server side the default value for a generation, and thus the generation for a new provider is 0. This fixes that situation and thus avoids causing the first inventory write operation from the resource tracker to the placement API being a 409 conflict. Change-Id: Iaa9e786f33049799678f21b5dfaac417c6601ac8 Closes-Bug: #1660682 ** 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). https://bugs.launchpad.net/bugs/1660682 Title: resource tracker sets wrong initial resource provider generation when creating a new resource provider Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) newton series: New Bug description: When the resource tracker creates (and then effectively caches) a new resource provider for the compute node, it sets the generation to 1. This leads to the first PUT to set inventory resulting in a 409 conflict because the generation is wrong. The default generation in the database is 0, so for any new resource provider this is what it will be. So in the resource tracker, in _create_resource_provider, the generation should also be 0. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1660682/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
