[
https://issues.apache.org/jira/browse/CLOUDSTACK-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ram Chinta updated CLOUDSTACK-123:
----------------------------------
Assignee: edison su (was: Rohit Yadav)
> Null pointer exception when there is no secondary storage available
> -------------------------------------------------------------------
>
> Key: CLOUDSTACK-123
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-123
> Project: CloudStack
> Issue Type: Bug
> Components: Management Server
> Affects Versions: pre-4.0.0
> Reporter: Sailaja Mada
> Assignee: edison su
> Fix For: pre-4.0.0
>
> Attachments: management-server.log
>
>
> Steps:
> 1. Deploy basic zone with KVM as the hypervisor
> 2. Verify that system vm's [ console proxy and secondary storage VM's ] are
> up
> 3. Delete the secondary storage
> 4. Delete System VM's
> 5. Then Management server tried to bring up the system VM's
> Observation:
> Null pointer exception when there is no secondary storage available
> Exception:
> 2012-09-17 12:40:48,824 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) No secondary storage available in zone 1, wait until it
> is ready to launch secondary storage vm
> 2012-09-17 12:40:48,824 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is not ready to launch secondary storage VM yet
> 2012-09-17 12:40:48,951 WARN [cloud.vm.SystemVmLoadScanner]
> (consoleproxy-1:null) Unexpected exception null
> java.lang.NullPointerException
> at
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.isZoneReady(ConsoleProxyManagerImpl.java:1187)
> at
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:1911)
> at
> com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:170)
> at
> com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:105)
> at
> com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:34)
> at
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:83)
> at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:73)
> 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)
> at java.lang.Thread.run(Thread.java:679)
> 2012-09-17 12:40:49,989 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 routers.
> Attached Management server log.
--
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
