yahoo-eng-team team mailing list archive

[OpenStack Infra <1657424@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/434897
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=5eb0db9b369dbcf594e0dd66fcebf12c69699417
Submitter: Jenkins
Branch:    master

commit 5eb0db9b369dbcf594e0dd66fcebf12c69699417
Author: Claudiu Belu <cbelu@xxxxxxxxxxxxxxxxxxxxxx>
Date:   Thu Feb 16 15:11:11 2017 +0200

    hyperv: make sure to plug OVS VIFs after resize/migrate
    
    Since the network_info wasn't getting passed to vmops.power_on
    after a resize/cold migrate confirmation, the OVS VIFs weren't
    getting plugged.
    
    (cherry-picked from commit 568a682e5efa6e4fd49b69e02cbd80f1d8a96c63)
    
    Change-Id: I9097debeb68cb25dec27e7b3e979cf51d951c250
    Closes-Bug: #1657424


** Changed in: compute-hyperv
       Status: New => 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/1657424

Title:
  Hyper-V: Instance ports not bound after resize

Status in compute-hyperv:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  When using OVS, the Hyper-V driver creates the OVS ports only after
  the instance is powered on (due to a Hyper-V limitation).

  The issue is that in case of cold migrations/resize, this step is currently skipped, as the driver doesn't pass the network info object when powering on the instance:
  https://github.com/openstack/nova/blob/07b6580a1648a860eefb5a949cb443c2a335a89a/nova/virt/hyperv/migrationops.py#L300-L301

  Simply passing that object will fix the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1657424/+subscriptions