cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-2030) Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when scaling VM:i-2-7-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min ⤠dynamic_min = dynamic_max = static_max
Date Tue, 16 Apr 2013 09:25:17 GMT

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

prashant kumar mishra closed CLOUDSTACK-2030.
---------------------------------------------

    Resolution: Fixed

it was licensing issue 
                
> Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException
when scaling VM:i-2-7-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min
⤠dynamic_min = dynamic_max = static_max
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2030
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2030
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            Assignee: Nitin Mehta
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: access_log.2013-04-15.txt, apilog.log, catalina.out, management-server.log,
SMlog, xensource.log, xenstored-access.log
>
>
> VM scale up is failing
> Steps to reproduce
> ----------------------------
> 1-Deploy a vm with SO=small instance,Default Template
> 2-Try to Scaleup vm to SO=Medium instance using API
>  
> http://10.*.*.*:8080/client/api?command=scaleVirtualMachine&id=332739a3-7a8e408f-86e0-4b66f1ff2c7d&serviceofferingid=4da8daee-cd3e-454a-ba48-be3f9c81f085&
> Expected
> --------------
> VM scale up  should be successful 
> Actual 
> -------------
> VM scale up failed with exception 
>  unhandled exception executing api command: scaleVirtualMachine
> com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm due to Catch exception
com.xensource.xenapi.Types$XenAPIException when scaling VM:i-2-7-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory
limits must satisfy: static_min ⤠dynamic_min = dynamic_max = static_max
> snippet of management server Log
> --------------------------------------------------
> --------------------------------------------------
> 2013-04-15 09:36:17,232 ERROR [cloud.api.ApiServer] (catalina-exec-7:null) unhandled
exception executing api command: scaleVirtualMachine
> com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm due to Catch exception
com.xensource.xenapi.Types$XenAPIException when scaling VM:i-2-7-VM due to MEMORY_CONSTRAINT_VIOLATIONMemory
limits must satisfy: static_min ⤠dynamic_min = dynamic_max = static_max
>         at com.cloud.vm.VirtualMachineManagerImpl.reConfigureVm(VirtualMachineManagerImpl.java:2927)
>         at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1072)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at org.apache.cloudstack.api.command.user.vm.ScaleVMCmd.execute(ScaleVMCmd.java:88)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:164)
>         at com.cloud.api.ApiServer.queueCommand(ApiServer.java:454)
>         at com.cloud.api.ApiServer.handleRequest(ApiServer.java:304)
>         at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:302)
>         at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
>         at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message