cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9690) Scale CentOS7 VM fails with error
Date Thu, 02 Mar 2017 19:24:45 GMT


ASF GitHub Bot commented on CLOUDSTACK-9690:

Github user cloudmonger commented on the issue:
    ### ACS CI BVT Run
     Build Number 414
     Hypervisor xenserver
     NetworkType Advanced
    _Link to logs Folder (search by build_no):_
    **Failed tests:**
    **Skipped tests:**
    **Passed test suits:**

> Scale CentOS7 VM fails with error 
> ----------------------------------
>                 Key: CLOUDSTACK-9690
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions:
>            Reporter: Sudhansu Sahu
>            Assignee: Sudhansu Sahu
> Scale CentOS7 VM fails with error "Cannot scale up the vm because of memory constraint
> 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 when scaling VM:i-24-3976-VM due
to 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}
> =============================
> # 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

View raw message