Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D656E10ECC for ; Tue, 29 Oct 2013 00:56:30 +0000 (UTC) Received: (qmail 98980 invoked by uid 500); 29 Oct 2013 00:56:30 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 98932 invoked by uid 500); 29 Oct 2013 00:56:30 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 98924 invoked by uid 500); 29 Oct 2013 00:56:30 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 98921 invoked by uid 99); 29 Oct 2013 00:56:30 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 00:56:30 +0000 Date: Tue, 29 Oct 2013 00:56:30 +0000 (UTC) From: "Parth Jagirdar (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (CLOUDSTACK-4983) VMWare:MS: Dynamic scaling doesnt work with vCenter 5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-4983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar closed CLOUDSTACK-4983. -------------------------------------- Resolution: Not A Problem Fix Version/s: 4.2.0 We do not poll for VMware tools status on VM's. So given that fact we introduced a check box that Admin's must check before attempting a dynamic scaling. ( A Trust feature that VMWare tools is now installed). Subsequent tests revealed that scaling can be successful with this flag set and VMWare tools not installed at all. However it is still recommended that we install the VMWare tools and then set the Flag (Which acts as a way of telling CS that VMWare tools is now successfully installed). Then perform a dynamic scaling. Closing as not a problem, But would certainly wish for a cleaner implementation that doesn't rely on Trust. There are high chances that we could pull VMWare tools status from vCenter instead of relying on manual flag. Would raise a separate enhancement request for this. > VMWare:MS: Dynamic scaling doesnt work with vCenter 5.1 > ------------------------------------------------------- > > Key: CLOUDSTACK-4983 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4983 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: API, Management Server, VMware > Affects Versions: 4.2.0 > Environment: VCenter 5.1 with ESX 5.1 > Reporter: Parth Jagirdar > Priority: Critical > Fix For: 4.2.0 > > > Dynamic scaling complains about VMWare tools not installed although its installed on VM and vCenter reports it as installed. > Is VMWare-tools detection not happening correctly on vCenter 5.1/ESXi 5.1? > -487b-9226-cba948735665 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.ScaleVMCmd > com.cloud.utils.exception.CloudRuntimeException: Unable to Scale the vm: 7c70a918-d6c1-4a23-91ff-524cafe9613d as vm does not have tools to support dynamic scaling > at com.cloud.vm.UserVmManagerImpl.upgradeRunningVirtualMachine(UserVmManagerImpl.java:1281) > at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1226) > at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1160) > at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at org.apache.cloudstack.api.command.user.vm.ScaleVMCmd.execute(ScaleVMCmd.java:102) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-10-28 17:09:22,721 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-30:job-50 = [ 984aac12-7908-487b-9226-cba948735665 ]) Complete async job-50 = [ 984aac12-7908-487b-9226-cba948735665 ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Unable to Scale the vm: 7c70a918-d6c1-4a23-91ff-524cafe9613d as vm does not have tools to support dynamic scaling > 2013-10-28 17:09:25,730 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) ===START=== 10.215.2.19 -- GET command=queryAsyncJobResult&jobId=984aac12-7908-487b-9226-cba948735665&response=json&sessionkey=uH7v1HeDZJF1y9NFekMzJzhwF78%3D&_=1383005365709 > 2013-10-28 17:09:25,741 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-2:null) Async job-50 = [ 984aac12-7908-487b-9226-cba948735665 ] completed > 2013-10-28 17:09:25,748 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) ===END=== 10.215.2.19 -- GET command=queryAsyncJobResult&jobId=984aac12-7908-487b-9226-cba948735665&response=json&sessionkey=uH7v1HeDZJF1y9NFekMzJzhwF78%3D&_=1383005365709 -- This message was sent by Atlassian JIRA (v6.1#6144)