[
https://issues.apache.org/jira/browse/CLOUDSTACK-8754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706472#comment-14706472
]
Koushik Das commented on CLOUDSTACK-8754:
-----------------------------------------
The serialization for 'VmWorkMigrateForScale' object is failing as it has
'DeployDestination' as one of the members which in turn fails as there is a
field of type Map<Volume, StoragePool> in it. At runtime this map has objects
of type PrimaryDataStoreImpl which is not serialisable and so the error.
> 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)
