Hi All, I was curious is there is a known set of API calls that will/should work when CloudStack is in simulator mode?
Some background. I'm running CS 4.2 (commit 8d043c0e4d4c9ace8628f542eacf19e5339e28e8 to be specific), on rhel 6.3 64-bit, built from source following simulator instructions here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python#Marvin-TestingwithPython-Building Simulator appears to work fine, however, I'm starting encounter API calls that fail. Specifically attachVolume fails with a NullPointerException. Is this a bug within the simulator or a known limitation? Log statement for attachVolume: ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-19:job-30 = [ fca87e69-c688-428c-82ca-4a44f5b169ff ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.hypervisor.dao.HypervisorCapabilitiesDaoImpl.getMaxDataVolumesLimit(HypervisorCapabilitiesDaoImpl.java:90) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.VolumeManagerImpl.getMaxDataVolumesSupported(VolumeManagerImpl.java:1696) at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1762) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122) 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:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Thanks! -- David Grizzanti Software Engineer Sungard Availability Services e: david.grizza...@sungard.com w: 215.446.1431 c: 570.575.0315
