[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679437#comment-13679437
 ] 

ASF subversion and git services commented on CLOUDSTACK-2923:
-------------------------------------------------------------

Commit d8a235ee316af7d9b21ea62581c8b5c8925081d8 in branch refs/heads/master 
from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d8a235e ]

CLOUDSTACK-2923: Delete Secondary storage of a Zone was giving NPE bcz we were 
still refering to the object. Instead log that the cpvm and ssvm cant be 
created bcz sec storage is not available

                
> Delete Secondary storage of a Zone is giving java NPE
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-2923
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2923
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Nitin Mehta
>
> Repro Steps:
> 1.Create a Zone
> 2. Create few VMs to it
> 3.Delete Secondary storage
> Bug:
> Ms logs shows Java NPE
> Expected Result:
> Delete sceondary storage should not give any NPE
> We are getting NPE in Ms log once we delete Secondary storage
> MS Log shows :
> 2012-11-16 13:36:23,370 WARN [cloud.vm.SystemVmLoadScanner] 
> (consoleproxy-1:null) Unexpected exception null
> java.lang.NullPointerException
>         at 
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.isZoneReady(ConsoleProxyManagerImpl.java:1177)
>         at 
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:1894)
>         at 
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:166)
>         at 
> com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:101)
>         at 
> com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:30)
>         at 
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:79)
>         at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:69)
>         at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at 
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
>         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
>         at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
>         at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

--
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

Reply via email to