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-8754) VM migration triggered by dynamic scaling is failing
Date Mon, 24 Aug 2015 05:08:45 GMT


ASF GitHub Bot commented on CLOUDSTACK-8754:

Github user koushik-das commented on the pull request:
    @DaanHoogland I have verified using the simulator based on the repro steps mentioned in
the bug. I found some issues in the simulator while testing this issue end-to-end, will push
the simulator fixes as a separate PR.
    Also I had done a (de)serialization test for VmWorkMigrateForScale. But I don't want to
have it as unit test unless I see a valid justification (or some better way to test it).

> VM migration triggered by dynamic scaling is failing
> ----------------------------------------------------
>                 Key: CLOUDSTACK-8754
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.5.0, 4.6.0
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>             Fix For: 4.6.0
> Steps to reproduce
> 1. Create a cluster with two hosts, disable one. Since dynamic scaling is supported by
XS and Vmware use one of them.
> 2. Create 2 service offerings (say 'small' and 'big')
> 3. Exhaust CPU capacity of the enabled host by deploying VMs with SO 'small'.
> 4. Try scaling up one of the VMs to SO 'big', and make sure it is failing with insufficient
> 5. Enable the other host in cluster. Make sure this has enough CPU capacity to accommodate
the VM with SO 'big'.
> 6. Now repeat step 4.
> Expected
> ------------
> Since there is no cpu resource left on host, vm should scale up after live migration
to another host
> Actual
> --------
> VM scale up failed due to "Received exception while scaling 
> Unable to serialize:

This message was sent by Atlassian JIRA

View raw message