This was novel when I reported this, but now the bug was fixed during granular-candidates work. Linked the related patches manually just now.
Unit test submitted in https://review.openstack.org/#/c/566842/ Fixed in https://review.openstack.org/#/c/517757/ ** Changed in: nova Status: Confirmed => 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/1769853 Title: Local disk without enough capacity appears in allocation candidates Status in OpenStack Compute (nova): Fix Released Bug description: How to reproduce ------------------------- In placement, 1. Setup a compute node resource provider with inventories of - 24 VCPU - 2048 MEMORY_MB - 1600 DISK_GB 2. Setup a shared storage resource provider with "MISC_SHARES_VIA_AGGREGATE" tag with - 2000 DISK_GB inventory 3. Set them both in a same aggregate 4. Get allocation candidates requesting - 1 VCPU - 64 MEMORY_MB - 1800 DISK_GB inventory. Expected ------------- Get one allocation request where DISK inventory is provided by the shared storage Actual ---------- Get two allocation request, in one of which DISK inventory is provided by the compute node To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1769853/+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
