With that change, during server create, volume-backed instances won't have root_gb disk allocated against the compute node resource provider in placement, nor will it filter on root_gb disk (no "claim"). It's not a complete solution since it doesn't handle move operations that allocate resources on a new host like during cold/live migrate, unshelve and evacuate (well, at least not for existing instances anyway since their request spec wouldn't have the is_bfv flag set). But it's a step in the right direction. The only problem is, as currently written, it's not backportable to stable branches.
This wasn't linked into the bug properly, but this change should resolve some of the problem here:
https:/ /review. openstack. org/#/c/ 580720/
With that change, during server create, volume-backed instances won't have root_gb disk allocated against the compute node resource provider in placement, nor will it filter on root_gb disk (no "claim"). It's not a complete solution since it doesn't handle move operations that allocate resources on a new host like during cold/live migrate, unshelve and evacuate (well, at least not for existing instances anyway since their request spec wouldn't have the is_bfv flag set). But it's a step in the right direction. The only problem is, as currently written, it's not backportable to stable branches.