cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9182) Some running VMs turned off on manual migration when auto migration failed while host preparing for maintenance
Date Fri, 02 Dec 2016 12:24:58 GMT


ASF GitHub Bot commented on CLOUDSTACK-9182:

Github user cloudmonger commented on the issue:
    ### ACS CI BVT Run
     Build Number 153
     Hypervisor xenserver
     NetworkType Advanced
    _Link to logs Folder (search by build_no):_
    **Failed tests:**
     * test_01_snapshot_root_disk Failed
     * test_deploy_vm_from_iso Failing since 25 runs
     * test_DeployVmAntiAffinityGroup Failed
     * test_10_attachAndDetach_iso Failing since 26 runs
    **Skipped tests:**
    **Passed test suits:**

> Some running VMs turned off on manual migration when auto migration failed while host
preparing for maintenance
> ---------------------------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-9182
>                 URL:
>             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
> 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

View raw message