Public bug reported: When GET allocation_candidate request is sent to the placement api with normal and custom resource requested the placement API returns no allocation candidates.
The scenario works properly if the two resources requested are from different providers but non of the is a custom resource. See the functional test case reproducing the problem: https://review.openstack.org/#/c/485088 See the ML thread for the discussion: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119832.html ** 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/1705231 Title: Placement returns no allocation candidate for request that needs both compute resources and custom shared resources Status in OpenStack Compute (nova): New Bug description: When GET allocation_candidate request is sent to the placement api with normal and custom resource requested the placement API returns no allocation candidates. The scenario works properly if the two resources requested are from different providers but non of the is a custom resource. See the functional test case reproducing the problem: https://review.openstack.org/#/c/485088 See the ML thread for the discussion: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119832.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1705231/+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
