Cluster resource group migration issue
Bug #1618425 reported by
Lucian Petrut
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:/
This worked on Windows Server 2012R2 but is causing issues on WS 2016. Resource group end up hanging in a 'Pending' state.
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/361136 /git.openstack. org/cgit/ openstack/ os-win/ commit/ ?id=f3de712905b 7e784d5cfa061cb f9a27215a43391
Committed: https:/
Submitter: Jenkins
Branch: master
commit f3de712905b7e78 4d5cfa061cbf9a2 7215a43391
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 /msdn.microsoft .com/en- us/library/ aa371809( v=vs.85) .aspx
link, we were passing the desired migration type directly.
https:/
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: Idfcd3505cbbf27 54addeba4f1ebeb 880f3b9a56b