Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EBCF818214 for ; Fri, 21 Aug 2015 15:10:46 +0000 (UTC) Received: (qmail 41768 invoked by uid 500); 21 Aug 2015 15:10:46 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 41734 invoked by uid 500); 21 Aug 2015 15:10:46 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 41725 invoked by uid 500); 21 Aug 2015 15:10:46 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 41722 invoked by uid 99); 21 Aug 2015 15:10:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2015 15:10:46 +0000 Date: Fri, 21 Aug 2015 15:10:46 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-8754) VM migration triggered by dynamic scaling is failing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)