Cluster resource group migration issue

Bug #1618425 reported by Lucian Petrut
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-win
Fix Released
Undecided
Unassigned

Bug Description

At the moment, in order to migrate a clustered VM, we move the according cluster resource group using the MoveToNewNodeParams WMI method. This method accepts an undocumented 'Parameters' argument, which is then passed to the underlying MoveClusterGroupEx clusapi.dll function. While the latter expects a property list as described here: https://msdn.microsoft.com/en-us/library/aa371809(v=vs.85).aspx, we were passing the desired migration type directly.

This worked on Windows Server 2012R2 but is causing issues on WS 2016. Resource group end up hanging in a 'Pending' state.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-win (master)

Reviewed: https://review.openstack.org/361136
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=f3de712905b7e784d5cfa061cbf9a27215a43391
Submitter: Jenkins
Branch: master

commit f3de712905b7e784d5cfa061cbf9a27215a43391
Author: Lucian Petrut <email address hidden>
Date: Fri Aug 26 13:18:08 2016 +0300

    Fix clustered vm live migration

    At the moment, in order to migrate a clustered VM, we move the
    according cluster resource group using the MoveToNewNodeParams WMI
    method. This method accepts an undocumented 'Parameters' argument,
    which is then passed to the underlying MoveClusterGroupEx clusapi.dll
    function.

    While the latter expects a property list as described at the following
    link, we were passing the desired migration type directly.
    https://msdn.microsoft.com/en-us/library/aa371809(v=vs.85).aspx

    This worked on Windows Server 2012R2 but is causing issues on WS 2016.
    Resource group end up hanging in a 'Pending' state.

    This change addresses this issue by using clusapi.dll functions directly,
    as the according WMI methods are not working, throwing a generic error
    even though the VMs are migrated properly.

    Closes-Bug: #1618425

    Change-Id: Idfcd3505cbbf2754addeba4f1ebeb880f3b9a56b

Changed in os-win:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-win (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/375598

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-win (stable/newton)

Reviewed: https://review.openstack.org/375598
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=a78531b66e2f8f6118811e764076129ab6537fd3
Submitter: Jenkins
Branch: stable/newton

commit a78531b66e2f8f6118811e764076129ab6537fd3
Author: Lucian Petrut <email address hidden>
Date: Fri Aug 26 13:18:08 2016 +0300

    Fix clustered vm live migration

    At the moment, in order to migrate a clustered VM, we move the
    according cluster resource group using the MoveToNewNodeParams WMI
    method. This method accepts an undocumented 'Parameters' argument,
    which is then passed to the underlying MoveClusterGroupEx clusapi.dll
    function.

    While the latter expects a property list as described at the following
    link, we were passing the desired migration type directly.
    https://msdn.microsoft.com/en-us/library/aa371809(v=vs.85).aspx

    This worked on Windows Server 2012R2 but is causing issues on WS 2016.
    Resource group end up hanging in a 'Pending' state.

    This change addresses this issue by using clusapi.dll functions directly,
    as the according WMI methods are not working, throwing a generic error
    even though the VMs are migrated properly.

    Closes-Bug: #1618425

    Change-Id: Idfcd3505cbbf2754addeba4f1ebeb880f3b9a56b
    (cherry picked from commit f3de712905b7e784d5cfa061cbf9a27215a43391)

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-win 1.2.1

This issue was fixed in the openstack/os-win 1.2.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-win 1.3.0

This issue was fixed in the openstack/os-win 1.3.0 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.