You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rayees Namathponnan (JIRA)" <ji...@apache.org> on 2013/04/04 23:42:17 UTC
[jira] [Created] (CLOUDSTACK-1943) Null pointer excretion after
creating new VM
Rayees Namathponnan created CLOUDSTACK-1943:
-----------------------------------------------
Summary: Null pointer excretion after creating new VM
Key: CLOUDSTACK-1943
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1943
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: Master
This issue observed in VM ware
Reporter: Rayees Namathponnan
Fix For: 4.2.0
Steps to reproduce
Step 1 : Create and install a master build (Revision: 4f9bdba2815510d55cbf0727f80fe57b14023022)
Step 2 : Create advanced zone
Step 3 : Deploy a VM
Actual Result
VM create successfully , after complete the VM creation, below null pointer exception thrown in MS log during capacity check
2013-04-04 14:04:29,604 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Done executing cpu/ram capacity update
2013-04-04 14:04:29,604 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Executing storage capacity update
2013-04-04 14:04:29,631 DEBUG [cloud.storage.StorageManagerImpl] (CapacityChecker:null) Successfully set Capacity - 23621556633600 for capacity type - 3 , DataCenterId - 1, HostOrPoolId - 1, PodId 1
2013-04-04 14:04:29,652 ERROR [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Caught exception in recalculating capacity
java.lang.NullPointerException
at com.cloud.storage.StorageManagerImpl.createCapacityEntry(StorageManagerImpl.java:1003)
at com.cloud.alert.AlertManagerImpl.recalculateCapacity(AlertManagerImpl.java:360)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.alert.AlertManagerImpl.checkForAlerts(AlertManagerImpl.java:506)
at com.cloud.alert.AlertManagerImpl$CapacityChecker.run(AlertManagerImpl.java:495)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
2013-04-04 14:04:29,671 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Done running Capacity Checker ...
2013-04-04 14:04:30,234 INFO [vmware.resource.VmwareResource] (DirectAgent-16:10.223.250.130) destroy volume-wrapper VM ROOT-1-1
2013-04-04 14:04:30,857 INFO [vmware.mo.DatastoreMO] (DirectAgent-16:10.223.250.130) Search file on [4faf04c26dd83025b43f65d32cc49d02] ROOT-1-1
2013-04-04 14:04:30,908 INFO [vmware.mo.DatastoreMO] (DirectAgent-16:10.223.250.130) Unable to test file existence due to exception java.lang.RuntimeException, skip deleting of it
2013-04-04 14:04:30,910 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-16:null) Seq 2-314507272: Response Received:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira