You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When migrating a VM to other SDRS Cluster, the VM always gets migrated to another esx within the cluster without taking into account the DRS rules. This causes cross site traffic on the san and running VMs on wrong hosts.
Streched Cluster configuration.
Host A in DRS Group A in Datacenter A with SDRS Cluster A.
DRS Rule defined: "VMs in group_A should run on Hostgroup_A"
VM is running on Host A
Run a playbook to migrate only the VMDKs of the VM to datastore_cluster_site_A
Host A and Host B can access all Datastores in Datastore Cluster "Site A".
No issues on SAN.
dastastore_cluster_A and datastore_cluster_B are present.
Same issue when defining the destination cluster!
Only when defining the destination_host, the task does not move the VM to another host.
- name: Storage Migration to defined clusterhosts: my_vmgather_facts: noserial: 1tasks:
- name: Perform vMotion of virtual machinevmware_vmotion:
hostname: "{{ vcenter }}"username: "{{ user }}"password: "{{ pass }}"vm_name: "{{ inventory_hostname }}"#destination_cluster: "{{ vmware_cluster }}"destination_datastore_cluster: "{{ datastore_cluster_site_A }}"timeout: 18000delegate_to: localhost
EXPECTED RESULTS
Only Storage DRS for this VM is executed without moving the VM to another ESX because the VM runs already on the correct Host regarding DRS Ruleset.
Same issue when defining the destination cluster!
Only when defining the destination_host, the task does not move the VM to another host.
ACTUAL RESULTS
The module executes first a VMotion to relocate VM from Host A to Host B including Storage VMotion to the correct datastore_cluster _A
After the Task is completed, VMware DRS migrates VM_A from Host_B back to Host_A because of the DRS Rules.
VMware Task Message: Hot migrating VM_A from host_A, datastore_B in vdc to host_B, datastore_A
The text was updated successfully, but these errors were encountered:
SUMMARY
When migrating a VM to other SDRS Cluster, the VM always gets migrated to another esx within the cluster without taking into account the DRS rules. This causes cross site traffic on the san and running VMs on wrong hosts.
ISSUE TYPE
COMPONENT NAME
vmware_vmotion
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
Debian 12
6.1.0-23-amd64
STEPS TO REPRODUCE
Streched Cluster configuration.
Host A in DRS Group A in Datacenter A with SDRS Cluster A.
DRS Rule defined: "VMs in group_A should run on Hostgroup_A"
VM is running on Host A
Run a playbook to migrate only the VMDKs of the VM to datastore_cluster_site_A
Host A and Host B can access all Datastores in Datastore Cluster "Site A".
No issues on SAN.
dastastore_cluster_A and datastore_cluster_B are present.
Same issue when defining the destination cluster!
Only when defining the destination_host, the task does not move the VM to another host.
EXPECTED RESULTS
Only Storage DRS for this VM is executed without moving the VM to another ESX because the VM runs already on the correct Host regarding DRS Ruleset.
Same issue when defining the destination cluster!
Only when defining the destination_host, the task does not move the VM to another host.
ACTUAL RESULTS
The module executes first a VMotion to relocate VM from Host A to Host B including Storage VMotion to the correct datastore_cluster _A
After the Task is completed, VMware DRS migrates VM_A from Host_B back to Host_A because of the DRS Rules.
The text was updated successfully, but these errors were encountered: