yahoo-eng-team team mailing list archive

[OpenStack Infra <1762688@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/577424
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c59397e09de5506bccba513ef31ffb8585fcdc3
Submitter: Zuul
Branch:    master

commit 1c59397e09de5506bccba513ef31ffb8585fcdc3
Author: Sylvain Bauza <sbauza@xxxxxxxxxx>
Date:   Fri Jun 22 14:53:57 2018 +0200

    libvirt: Fix the rescue race for vGPU instances
    
    When rescuing an instance having a vGPU, we were not using the vGPU.
    There would then be a race condition during the rescue where the vGPU
    could be passed to another instance.
    Instead, we should just make sure the vGPU would also be in the rescued
    instance.
    
    Change-Id: I7150e15694bb149ae67da37b5e43b6ea7507fe82
    Closes-bug: #1762688


** Changed in: nova
       Status: In Progress => 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/1762688

Title:
  rescued instance doesn't have attached vGPUs

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) queens series:
  Confirmed

Bug description:
  With the libvirt driver, rescuing an instance means that the attached
  mediated devices for virtual GPUs will be released. When unrescuing
  the instance, the driver will use the existing guest XML so it will
  attach again the mediated devices, but it could be a race condition in
  case the related vGPUs are now attached to a separate instance.

  We should attach the mediated devices to the rescued instance too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1762688/+subscriptions