[
https://issues.apache.org/jira/browse/CLOUDSTACK-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173010#comment-16173010
]
ASF subversion and git services commented on CLOUDSTACK-9182:
-------------------------------------------------------------
Commit f2584bb9e755ae296c0e05515363d6b3a5d3c71f in cloudstack's branch
refs/heads/master from sureshanaparti
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=f2584bb ]
CLOUDSTACK-9182: Some running VMs turned off on manual migration when auto
migration failed while host preparing for maintenance. (#1252)
Fix: Block VMOperations if Host in PrepareForMaintenance mode. VM operations
(Stop, Reboot, Destroy, Migrate to host) are not allowed when Host in
PrepareForMaintenance mode.
> Some running VMs turned off on manual migration when auto migration failed
> while host preparing for maintenance
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9182
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9182
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, VMware
> Affects Versions: 4.5.2
> Environment: vCenter 5.0
> Reporter: Suresh Kumar Anaparti
> Assignee: Suresh Kumar Anaparti
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
