cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailaja Mada (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-1602) NPE while recalculating the storage capacity
Date Fri, 08 Mar 2013 11:46:12 GMT
Sailaja Mada created CLOUDSTACK-1602:

             Summary: NPE while recalculating the storage capacity
                 Key: CLOUDSTACK-1602
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Storage Controller
    Affects Versions: 4.2.0
            Reporter: Sailaja Mada
            Assignee: edison su

Setup : Advanced Networking Zone with KVM 6.3 host 


1.  Tried to add second primary storage with wrong folder name. It failed with NPE . It is
tracked as a separate issue.  

2. While capacity checker to calculate the storage capacity- It failed with NPE 

2013-03-08 17:01:12,908 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null)
Found 0 networks to update RvR status.
2013-03-08 17:01:13,133 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Running
Capacity Checker ...
2013-03-08 17:01:13,133 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) recalculating
system capacity
2013-03-08 17:01:13,133 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Executing
cpu/ram capacity update
2013-03-08 17:01:13,141 DEBUG [cloud.capacity.CapacityManagerImpl] (CapacityChecker:null)
Found 4 VMs on host 1
2013-03-08 17:01:13,142 DEBUG [cloud.capacity.CapacityManagerImpl] (CapacityChecker:null)
Found 0 VM, not running on host 1
2013-03-08 17:01:13,145 DEBUG [cloud.capacity.CapacityManagerImpl] (CapacityChecker:null)
No need to calibrate cpu capacity, host:1 usedCpu: 2000 reservedCpu: 0
2013-03-08 17:01:13,145 DEBUG [cloud.capacity.CapacityManagerImpl] (CapacityChecker:null)
No need to calibrate memory capacity, host:1 usedMem: 2013265920 reservedMem: 0
2013-03-08 17:01:13,145 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Done executing
cpu/ram capacity update
2013-03-08 17:01:13,145 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Executing
storage capacity update
2013-03-08 17:01:13,162 DEBUG [] (CapacityChecker:null) Successfully
set Capacity - 1759218630656 for capacity type - 3 , DataCenterId - 1, HostOrPoolId - 200,
PodId 1
2013-03-08 17:01:13,167 ERROR [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Caught
exception in recalculating capacity
        at sun.reflect.GeneratedMethodAccessor248.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
        at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(
        at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(
        at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(
        at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(
        at $Proxy116.createCapacityEntry(Unknown Source)
        at java.util.TimerThread.mainLoop(
2013-03-08 17:01:13,184 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Done running
Capacity Checker ...

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:

View raw message