[CLOUDSTACK-9182] Some running VMs turned off on manual migration when auto migration failed while host preparing for maintenance

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.5.2
• Component/s: Management Server, VMware
• Security Level: Public (Anyone can view this level - this is the default.)
• Environment: vCenter 5.0
• Assignee: Suresh Kumar Anaparti
• Reporter: Suresh Kumar Anaparti
• Created: 16/Dec/15 11:24
• Updated: 20/Sep/17 10:53

Description

When a host is put into maintenance, CloudStack schedules migration for all the running VMs present on the host. This scheduling is managed by High Availability worker thread. And every time a migration fails, CloudStack re-schedules the migration to be executed after 10 minutes.

In this case, CloudStack fails to migrate some VMs automatically while host is preparing for maintenance and admin tried to migrate them manually. All these VMs are turned off after manual migration.

Steps:

• Put a host into maintenance
• Scheduled migration failed for a VM and CloudStack re-scheduled it.
• Before the next scheduled migration, manually migrate the VM to a different host.

When the next scheduled migration was started by the HA work, it failed because there was a mismatch between the source host saved in the HA work job and the actual source host. If VM migration fails due to mismatch then the VM is stopped on the host it resides on.

Issue Links

• links to: GitHub Pull Request #1252