hyperv: boot from volume with Generation 2 VM image fails

Bug #1687570 reported by Claudiu Belu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Claudiu Belu
Ocata
Fix Committed
Medium
Matt Riedemann

Bug Description

Description
===========

Spawning with boot from volume (created from a Generation 2 VM image) fails on Hyper-V due to [1].

Steps to reproduce
==================

* create a glance image with the "hw_machine_type=hyperv-gen2" property.
* create a volume from glance image.
* spawn with boot from volume.

Expected result
===============

Instance is running.

Actual result
=============

Instance is in error state, spawn failed due to [1]

Environment
===========

* OpenStack Ocata release
* Windows Hyper-V Server 2012 R2 compute nodes

[1] Log: http://paste.openstack.org/show/608574/

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/461689

Changed in nova:
status: New → In Progress
melanie witt (melwitt)
Changed in nova:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/461689
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f842f11630a968fa67f531fb4f2e9b41d3be5f27
Submitter: Jenkins
Branch: master

commit f842f11630a968fa67f531fb4f2e9b41d3be5f27
Author: Claudiu Belu <email address hidden>
Date: Tue May 2 12:08:34 2017 +0300

    hyperv: Fixes Generation 2 VMs volume boot order

    The patch that introduced setting boot order to the nova
    Hyper-V driver [1] was using a method that no longer existed
    (Generation 2 VMs only). That method was renamed by the patch
    that refactored volumeops (to use os-brick) [2].

    [1] d68c04299aa2c04aea16e881d93076236cc64d7b
    [2] 758a32f7cef6c675b35c04dd8d276c918be188dd

    Change-Id: I499f078de16b79acbf12f993e9f549c75c3fccb0
    Closes-Bug: #1687570

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/479522

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 16.0.0.0b3

This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/ocata)

Reviewed: https://review.openstack.org/479522
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=54284a4f0cb0e79cd5f1b53cfe4fc6210db7a0aa
Submitter: Jenkins
Branch: stable/ocata

commit 54284a4f0cb0e79cd5f1b53cfe4fc6210db7a0aa
Author: Claudiu Belu <email address hidden>
Date: Tue May 2 12:08:34 2017 +0300

    hyperv: Fixes Generation 2 VMs volume boot order

    The patch that introduced setting boot order to the nova
    Hyper-V driver [1] was using a method that no longer existed
    (Generation 2 VMs only). That method was renamed by the patch
    that refactored volumeops (to use os-brick) [2].

    [1] d68c04299aa2c04aea16e881d93076236cc64d7b
    [2] 758a32f7cef6c675b35c04dd8d276c918be188dd

    Change-Id: I499f078de16b79acbf12f993e9f549c75c3fccb0
    Closes-Bug: #1687570
    (cherry picked from commit f842f11630a968fa67f531fb4f2e9b41d3be5f27)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 15.0.7

This issue was fixed in the openstack/nova 15.0.7 release.

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.