[
https://issues.apache.org/jira/browse/CLOUDSTACK-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662893#comment-13662893
]
ASF subversion and git services commented on CLOUDSTACK-2567:
-------------------------------------------------------------
Commit a58ee74e1c3760852214be28d8ef7051f27e1f29 in branch refs/heads/master
from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a58ee74 ]
CLOUDSTACK-2567 - Check whether DMC - dynamic memory control is enabled for the
hyervisor before trying to scale the vm. If its not then dont scale and instead
throw and exception.
> NPE when scaling of VM on unsupported hypervisor
> ------------------------------------------------
>
> Key: CLOUDSTACK-2567
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2567
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, XenServer
> Affects Versions: 4.2.0
> Reporter: Prasanna Santhanam
> Priority: Critical
> Fix For: 4.2.0
>
>
> When running the scaleVM test on xen 6.0.2 server which doesn't have dynamic
> memory control enabled following NullPointerException is observed:
> http://jenkins.buildacloud.org/job/test-smoke-matrix/suite=test_scale_vm/277/testReport/integration.smoke.test_scale_vm/TestScaleVm/test_01_scale_vm/
> Error Message
> Check service offering of the VM
> -------------------- >> begin captured logging << --------------------
> testclient.testcase.TestScaleVm: DEBUG: Scaling VM-ID:
> 8d58d33d-0732-494e-ae69-e807d62d92c8 to service offering:
> a06578e2-28e9-47a8-9a42-74f60650aa5a
> --------------------- >> end captured logging << ---------------------
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_scale_vm/test/integration/smoke/test_scale_vm.py",
> line 213, in test_01_scale_vm
> "Check service offering of the VM"
> File "/usr/local/lib/python2.7/unittest/case.py", line 494, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/local/lib/python2.7/unittest/case.py", line 902, in
> assertMultiLineEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
> raise self.failureException(msg)
> Check service offering of the VM
> -------------------- >> begin captured logging << --------------------
> testclient.testcase.TestScaleVm: DEBUG: Scaling VM-ID:
> 8d58d33d-0732-494e-ae69-e807d62d92c8 to service offering:
> a06578e2-28e9-47a8-9a42-74f60650aa5a
> --------------------- >> end captured logging << ---------------------
> 2013-05-18 15:28:37,451 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-38:job-38) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.ScaleVMCmd
> java.lang.NullPointerException
> at
> com.cloud.vm.VirtualMachineManagerImpl.upgradeVmDb(VirtualMachineManagerImpl.java:2776)
> at
> com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1154)
> at
> com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1084)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.ScaleVMCmd.execute(ScaleVMCmd.java:92)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 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
