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 6D71117EBD for ; Mon, 20 Oct 2014 12:25:34 +0000 (UTC) Received: (qmail 43554 invoked by uid 500); 20 Oct 2014 12:25:34 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 43519 invoked by uid 500); 20 Oct 2014 12:25:34 -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 43509 invoked by uid 500); 20 Oct 2014 12:25:34 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 43506 invoked by uid 99); 20 Oct 2014 12:25:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2014 12:25:34 +0000 Date: Mon, 20 Oct 2014 12:25:34 +0000 (UTC) From: "Pavan Kumar Bandarupally (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (CLOUDSTACK-6915) Deleting dynamically added OS results in NPE for existing instances using that os type 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-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavan Kumar Bandarupally reopened CLOUDSTACK-6915: -------------------------------------------------- I can reproduce the issue on VmWare on 4.5 build. Hence re-opening the issue. > Deleting dynamically added OS results in NPE for existing instances using that os type > -------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-6915 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6915 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Hypervisor Controller > Affects Versions: 4.4.0, 4.5.0 > Environment: XenServer host > Cloudstack 4.4 > Reporter: Pavan Kumar Bandarupally > Assignee: Amogh Vasekar > Priority: Critical > Fix For: 4.4.0, 4.5.0 > > Attachments: management-server.log > > > A guest OS is dynamically added and an instance is deployed successfully using that os type (ISO used to deploy instance was of that OS type). The custom os added was deleted using removeGuestOS. After this the instance is stopped and started again. > This start operation resulted in Null Pointer Exception. > 2014-06-16 06:50:33,350 ERROR [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Failed to start instance VM[User|i-2-12-VM] > java.lang.NullPointerException > at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:93) > at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995) > at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) > at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325) > at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) > at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503) > at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > 2014-06-16 06:50:33,359 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Cleaning up resources for the vm VM[User|i-2-12-VM] in Starting state > PFA MS log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)