onitake opened a new issue #3230: NPE when descriptor has VMware compatibility level 9 URL: https://github.com/apache/cloudstack/issues/3230 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ VMware ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.11.2 ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> N/A ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> VMware ESXi 5.5 ##### SUMMARY <!-- Explain the problem/feature briefly --> In CloudStack 4.11.2, it's impossible to start a VM that has an existing VMware descriptor with a compatibility level below 10. The bug manifests with a NullPointerException in com.cloud.hypervisor.vmware.mo.VirtualMachineMO.isMemoryHotAddSupported(VirtualMachineMO.java:3284 . ##### STEPS TO REPRODUCE <!-- For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate. For new features, show how the feature would be used. --> 1. Have an existing CloudStack VM that was created under VMware ESX 5.1 or older 2. Upgrade VMware to at least 5.5 3. Stop the VM 4. Start the VM <!-- You can also paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> The VM starts. ##### ACTUAL RESULTS <!-- What actually happened? --> CloudStack fails to launch the VM, instead throwing the following stack trace. <!-- Paste verbatim command output between quotes below --> ~~~ [ignored]failed toi get message for exception: null Message: null java.lang.NullPointerException at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.isMemoryHotAddSupported(VirtualMachineMO.java:3284) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1875) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:496) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315) 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 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ~~~
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
