yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1658070] Re: Failed SR_IOV evacuation with host

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Jay Pipes <1658070@xxxxxxxxxxxxxxxxxx>
Date: Fri, 19 May 2017 01:28:19 -0000
Reply-to: Bug 1658070 <1658070@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

*** This bug is a duplicate of bug 1512880 ***
    https://bugs.launchpad.net/bugs/1512880

The original poster's version of Nova was 13.1.2, which is Mitaka.
Therefore all the --force stuff and microversions discussion is
irrelevant (since microversion 2.29 was added in Newton).

So, the bug here is the migrate routine is not accounting for a change
in PCI address on the destination host and is effectively attempting to
launch the workload on the destination host with the source host's PCI
addresses, which clearly will not work unless, by luck, the destination
host has the exact same PCI addresses and those addresses are available.

The solution is to backport the patch that Matt referred to above that
fixes this issue in Newton and beyond:

 https://bugs.launchpad.net/nova/+bug/1512880

Marking this as a duplicate of 1512880.

** This bug has been marked a duplicate of bug 1512880
   Failed cold migration with SR-IOV

-- 
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/1658070

Title:
  Failed SR_IOV evacuation with host

Status in Mirantis OpenStack:
  Confirmed
Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) newton series:
  Confirmed
Status in OpenStack Compute (nova) ocata series:
  Confirmed

Bug description:
  When we try evacuate SR-IOV vm on concret host the VM is in ERROR
  state

  Steps to reproduce:
  1) Download trusty image
  2) Create image
  3) Create vf port:
  neutron port-create <net> --binding:vnic-type direct --device_owner nova-compute --name sriov
  4) Boot vm on this port:
  nova boot vm --flavor m1.small --image 1ff0759c-ea85-4909-a711-70fd6b71ad23 --nic port-id=cfc947be-1975-42f3-95bd-f261a2eccec0 --key-name vm_key
  5) Sgut down node with vm
  6) Evacuate vm:
  nova evacuate vm node-5.test.domain.local
  Expected result:
   VM evacuates on the 5th node
  Actual result:
   VM in error state

  Workaround:
  We can evacuate without pointing the host just nova evacuate vm

  Environment:
  #785 snap
  2 controllers? 2 compute with SR-IOV

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