nova-manage placement heal_allocations does not support instances with VGPU or Cyborg device profile request

Bug #1939020 reported by Balazs Gibizer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Wishlist
Sylvain Bauza

Bug Description

The nova-manage placement heal_allocations tool predates nested allocation support in nova. It gained explicit support for nested allocation only in case if the nested resources are coming from the port resource request [1]. If the resource request are coming from the flavor extra_specs (e.g. resources:VGPU=1) then the tool assumes that such resource can be fulfilled from the root resource provider[2][3]. This is obviously wrong for the VGPU resource that are provided on nested resource providers. Also [3] does not resolve cyborg device profiles to request groups so that request is also ignored.

As --force flag allows recreating instance allocations even if the tool does not detect a missing allocation using the tool on VGPU and Cyborg instances could result in loosing otherwise correct resource allocations. Loosing such resource allocation can lead to physical resource over-allocation later.

[1] https://github.com/openstack/nova/blob/2ffd9738602531e93495a1feca76bbb687c3e72c/nova/cmd/manage.py#L1814
[2] https://github.com/openstack/nova/blob/2ffd9738602531e93495a1feca76bbb687c3e72c/nova/cmd/manage.py#L1700
[3] https://github.com/openstack/nova/blob/2ffd9738602531e93495a1feca76bbb687c3e72c/nova/scheduler/utils.py#L607-L614

Tags: nova-manage
tags: added: nova-manage
Changed in nova:
assignee: nobody → Sylvain Bauza (sylvain-bauza)
status: New → Confirmed
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.