Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 22 Dec 2016 06:23:58 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13029701.1482317682000.578518.1482387838498@Atlassian.JIRA>
In-Reply-To: <JIRA.13029701.1482317682000@Atlassian.JIRA>
References: <JIRA.13029701.1482317682000@Atlassian.JIRA> <JIRA.13029701.1482317682019@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9690) Scale CentOS7 VM fails with
 error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 22 Dec 2016 06:24:00 -0000


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

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

Github user rhtyd commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/1849#discussion_r93571450
  
    --- Diff: api/src/org/apache/cloudstack/api/command/admin/guest/AddGuestOsCmd.java ---
    @@ -70,6 +78,23 @@ public String getOsName() {
             return osName;
         }
     
    +    public Map getDetails() {
    +        Map<String, String> detailsMap = null;
    --- End diff --
    
    don't make getDetails return null, instead return an empty hashmap.


> Scale CentOS7 VM fails with error 
> ----------------------------------
>
>                 Key: CLOUDSTACK-9690
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9690
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.10.0.0
>            Reporter: Sudhansu Sahu
>            Assignee: Sudhansu Sahu
>
> Scale CentOS7 VM fails with error "Cannot scale up the vm because of memory constraint violation"
> When creating VM from CentOS 7 template on the XenServer with dynamically scaling enabled, instance starts with base specified memory instead of memory * 4 as static limit.
> As the result, attempt to scale VM throws error in MS log:
> {noformat}
> java.lang.RuntimeException: Job failed due to exception Unable to scale vm due to Catch exception com.cloud.utils.exception.CloudRuntimeException when scaling VM:i-24-3976-VM due to com.cloud.utils.exception.CloudRuntimeException: Cannot scale up the vm because of memory constraint violation: 0 <= memory-static-min(2147483648) <= memory-dynamic-min(8589934592) <= memory-dynamic-max(8589934592) <= memory-static-max(2147483648)
> {noformat}
> REPO STEPS
> =============================
> # Enable dynamic scaling in Global settings
> # Register an CentOS 7 tempplate(with tools) and tick dynamic scaling
> # Deploy VM with this template
> # Start the VM and try to change service offering
> EXPECTED RESULT: VM should start with static limit 4x<assigned memory> and scale up when offering is changed
> ACTUAL RESULT: VM starts with maximum static limit of <assigned memory> and doesn't scale up with error in ms log :
> Cannot scale up the vm because of memory constraint violation: 


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