[
https://issues.apache.org/jira/browse/CLOUDSTACK-8754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712739#comment-14712739
]
ASF subversion and git services commented on CLOUDSTACK-8754:
-------------------------------------------------------------
Commit 22fad9d515e3e77af1d239a430b67808c2e563a5 in cloudstack's branch
refs/heads/master from [~rohit.ya...@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=22fad9d ]
Merge pull request #725 from koushik-das/CLOUDSTACK-8754
CLOUDSTACK-8754: VM migration triggered by dynamic scaling is failingThis 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.
* pr/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.
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
> 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)
