Public bug reported:
The presumption all along has been that when doing a PUT
/allocations/{consumer_uuid} that the body of that request would fully
replace any allocations associated with that consumer.
This has turned out not to be the case. The code [1] to clean up the
current allocations was only deleting allocations where the consumer
_and_ resource provider matched the incoming allocations. We want to
wipe the slate.
Huge hat tip to gibi for doing the necessary digging to get this going.
[1]
https://github.com/openstack/nova/blob/master/nova/objects/resource_provider.py#L1509-L1520
** Affects: nova
Importance: High
Status: Triaged
** Tags: pike-rc-potential placement
--
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/1707669
Title:
[placement] put allocations does not do a full overwrite of existing
allocations
Status in OpenStack Compute (nova):
Triaged
Bug description:
The presumption all along has been that when doing a PUT
/allocations/{consumer_uuid} that the body of that request would fully
replace any allocations associated with that consumer.
This has turned out not to be the case. The code [1] to clean up the
current allocations was only deleting allocations where the consumer
_and_ resource provider matched the incoming allocations. We want to
wipe the slate.
Huge hat tip to gibi for doing the necessary digging to get this
going.
[1]
https://github.com/openstack/nova/blob/master/nova/objects/resource_provider.py#L1509-L1520
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1707669/+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
