Reviewed: https://review.openstack.org/367307 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b6edbce9b3b092581eeda6be15059a1ba2bfcfdf Submitter: Jenkins Branch: master
commit b6edbce9b3b092581eeda6be15059a1ba2bfcfdf Author: He Jie Xu <[email protected]> Date: Thu Sep 8 19:46:24 2016 +0800 Ensure ResourceProvider/Inventory created before add Allocations record In the startup of compute node, the first available resource update will fail to add Allocations record. This is due to ResourceProvider will be created at the end of available resource update. This patch ensure the ResourceProvider and Inventory created in the beginning of available resource update. Closes-Bug: #1621437 Change-Id: I91fa7b8354a7613848225429ac9d38c6305b03c6 ** 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/1621437 Title: Add Allocations record failed in the startup of compute node Status in OpenStack Compute (nova): Fix Released Bug description: When startup the compute node, the allocation record failed to add, the message as below: 2016-09-08 19:51:43.615 WARNING nova.scheduler.client.report [req- 78558a2d-3d4c-4357-bbc2-d53281e1300e None None] Unable to submit allocation for instance 31bdb2e4-fb77-41b0-afb9-0cfe4292234d (400 400 Bad Requet The server could not comply with the request since it is either malformed or otherwise incorrect. Allocation for resource provider 'e1c72350-56dd- 468a-a035-44b224ff2d05' that does not exist. ) This due to we create ResourceProvider and Inventory in the end of available resource update. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1621437/+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

