yahoo-eng-team team mailing list archive

[OpenStack Infra <1630698@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/382853
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8e052c7fe9262c38da9d8b5f9a0ee889d9c1c6be
Submitter: Zuul
Branch:    master

commit 8e052c7fe9262c38da9d8b5f9a0ee889d9c1c6be
Author: paul-carlton2 <paul.carlton2@xxxxxxx>
Date:   Thu Oct 6 12:02:15 2016 +0100

    Update nova network info when doing rebuild for evacuate operation
    
    When nova evacuate or host-evacuate are used to recreate instances with
    sriov ports the instances are allocated new device ids on the target and
    neutron is updated accordingly. However the network info data passed
    to the driver spawn method is not updated and thus the instance tries
    to use the device id they were allocated on the source node. If a pre
    existing instance is using that device id or no such device exists on
    the target node then the instance will fail to start.
    
    Co-Authored-By: Steven Webster <steven.webster@xxxxxxxxxxxxx>
    Change-Id: I860ab9cf3f9a38bd4ea5bceecda8105b6fee93dc
    Closes-Bug: #1630698
    Related-Bug: #1677621


** 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/1630698

Title:
  nova evacuate of instances with sriov ports fails due to use of source
  device

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  In Progress
Status in OpenStack Compute (nova) queens series:
  In Progress

Bug description:
  When nova evacuate or host-evacuate are used to recreate instances
  with sriov ports the instances are allocated new device ids on the
  target and neutron is updated accordingly.  However the network info
  data passed to the driver spawn method is not updated and thus the
  instance tries to use the device id they were allocated on the source
  node.  If a pre existing instance is using that device id or no such
  device exists on the target node then the instance will fail to start.

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