Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 16 Dec 2015 12:34:46 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12922348.1450265048000.38522.1450269286657@Atlassian.JIRA>
In-Reply-To: <JIRA.12922348.1450265048000@Atlassian.JIRA>
References: <JIRA.12922348.1450265048000@Atlassian.JIRA>
 <JIRA.12922348.1450265048784@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9182) Some running VMs turned off on
 manual migration when auto migration failed while host preparing for
 maintenance
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059927#comment-15059927 ] 

ASF GitHub Bot commented on CLOUDSTACK-9182:
--------------------------------------------

GitHub user sureshanaparti opened a pull request:

    https://github.com/apache/cloudstack/pull/1252

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

    CLOUDSTACK-9182: Some running VMs turned off on manual migration when auto migration failed while host preparing for maintenance.
    
    Fix: Block VMOperations if Host in PrepareForMaintenance mode. VM operations (Stop, Reboot, Destroy, Migrate to host) are not allowed when Host in PrepareForMaintenance mode.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sureshanaparti/cloudstack CLOUDSTACK-9182

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1252.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1252
    
----
commit 98186f9e6a3f659ac294a30b2243070961c167fe
Author: Suresh Kumar Anaparti <sureshkumar.anaparti@citrix.com>
Date:   2015-12-16T12:31:30Z

    CLOUDSTACK-9182: Some running VMs turned off on manual migration when auto migration failed while host preparing for maintenance.
    
    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.3.4#6332)