cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8754) VM migration triggered by dynamic scaling is failing
Date Fri, 21 Aug 2015 11:14:45 GMT

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

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

GitHub user koushik-das opened a pull request:

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

    CLOUDSTACK-8754: VM migration triggered by dynamic scaling is failing

    This is caused by serialization failure for VmWorkMigrateForScale object. Replaced DeployDestination
member present in VmWorkMigrateForScale with serializable types.
    
    Haven't added any unit test as couldn't find a clean way to do it. Simply adding a test
to do (de)serialization won't help catch any new member addition to the type which breaks
serializability.

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

    $ git pull https://github.com/koushik-das/cloudstack CLOUDSTACK-8754

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

    https://github.com/apache/cloudstack/pull/725.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 #725
    
----
commit 3be2b6310333b8ee263ef7865d235d30ec9c804f
Author: Koushik Das <koushik@apache.org>
Date:   2015-08-21T11:01:44Z

    CLOUDSTACK-8754: VM migration triggered by dynamic scaling is failing
    This is caused by serialization failure for VmWorkMigrateForScale object. Replaced DeployDestination
member
    present in VmWorkMigrateForScale with serializable types.

----


> VM migration triggered by dynamic scaling is failing
> ----------------------------------------------------
>
>                 Key: CLOUDSTACK-8754
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8754
>             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
capacity.
> 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 
> com.cloud.utils.exception.CloudRuntimeException: Unable to serialize: com.cloud.vm.VmWorkMigrateForScale@65700a07



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message