You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sudhansu Sahu (JIRA)" <ji...@apache.org> on 2016/12/21 10:54:58 UTC

[jira] [Assigned] (CLOUDSTACK-9690) Scale CentOS7 VM fails with error

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudhansu Sahu reassigned CLOUDSTACK-9690:
-----------------------------------------

    Assignee: Sudhansu Sahu

> 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)