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 15:10:46 GMT

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

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

Github user DaanHoogland commented on the pull request:

    https://github.com/apache/cloudstack/pull/725#issuecomment-133457425
  
    Maybe a little out of scope for this PR, I have been looking a bit at the hierarchy. It
contains a lot of primitives. somewhat related to our gson problem (arrays of primitive types)
those should be removed.
    
    @kishankavala I see your point on serialisation testing. But it doesn't mean that a simple
test is useless. (no -1 for that) Let us think/search on applicable tests.
    
    Did you test this code in any way?


> 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