manasaveloori created CLOUDSTACK-6723:
-----------------------------------------

             Summary: [DynamicallyAddingGuestOs]Observed NPE when VM is 
deployed using the guest OS which has no mapping to any hypervisor
                 Key: CLOUDSTACK-6723
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6723
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: XenServer
    Affects Versions: 4.4.0
            Reporter: manasaveloori
            Priority: Critical
             Fix For: 4.4.0


1. Add a guest os using API
I added it using cloudmonkey:
 add guestos name=test oscategoryid=11 osdisplayname=test1centos
mysql> select category_id,name,uuid,display_name from guest_os where 
display_name="test1centos";
+-------------+------+--------------------------------------+--------------+
| category_id | name | uuid                                 | display_name |
+-------------+------+--------------------------------------+--------------+
|          11 | test | 8c413100-8b68-49c3-b81c-372c3ba8f998 | test1centos  |
+-------------+------+--------------------------------------+--------------+
1 row in set (0.00 sec)

2. did not create any mapping for this OS to hypervisor.
mysql> select hypervisor_type ,guest_os_name,hypervisor_version from 
guest_os_hypervisor where guest_os_name="test1centos";
Empty set (0.00 sec)
3. Registered the template using the above created OS type.
4. Now deploy a VM using the template.

Observation:

Observed NPE in Ms logs and deploy VM is failing.


2014-05-20 17:08:53,747 DEBUG [c.c.n.NetworkModelImpl] 
(Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Service SecurityGroup is not 
supported in the network id=206
2014-05-20 17:08:53,749 DEBUG [o.a.c.e.o.VolumeOrchestrator] 
(Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Checking if we need to 
prepare 1 volumes for VM[User|i-2-13-VM]
2014-05-20 17:08:53,750 DEBUG [o.a.c.e.o.VolumeOrchestrator] 
(Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) No need to recreate the 
volume: Vol[13|vm=13|ROOT], since it already has a pool assigned: 1, adding 
disk to VM
2014-05-20 17:08:53,773 ERROR [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Failed to start instance 
VM[User|i-2-13-VM]
java.lang.NullPointerException
        at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:96)
        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:496)
        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:453)
        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-05-20 17:08:53,780 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Cleaning up resources for the 
vm VM[User|i-2-13-VM] in Starting state
2014-05-20 17:08:53,783 DEBUG [c.c.a.t.Request] 
(Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Seq 1-7387310763771167224: 
Sending  { Cmd , MgmtId: 7672522866886, via: 1(Rack1Pod1Host28), Ver: v1, 
Flags: 100011, 
[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"checkBeforeCleanup":false,"vmName":"i-2-13-VM","wait":0}}]
 }
2014-05-20 17:08:53,783 DEBUG [c.c.a.t.Request] (Work-Job-Executor-23:jo


Attaching the logs and db dump.




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to