Uploaded image for project: 'CloudStack'
  1. CloudStack
  2. CLOUDSTACK-6915

Deleting dynamically added OS results in NPE for existing instances using that os type

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 4.4.0, 4.5.0
    • 4.4.0, 4.5.0
    • Hypervisor Controller
    • Security Level: Public (Anyone can view this level - this is the default.)
    • None
    • XenServer host
      Cloudstack 4.4 , VmWare host , CloudStack 4.5

    Description

      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.

      Attachments

        1. management-server.log
          5.48 MB
          Pavan Kumar Bandarupally
        2. VmWareMSLog.log
          4.54 MB
          Pavan Kumar Bandarupally

        Activity

          People

            amogh.vasekar Amogh Vasekar
            pavanb Pavan Kumar Bandarupally
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: