Public bug reported: 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. ** Affects: nova Importance: Medium Status: Triaged ** Tags: placement scheduler -- 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): Triaged 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 : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp