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

Rajesh Battala commented on CLOUDSTACK-3264:
--------------------------------------------

while migrating the volume from one ZWPS to another ZWPS, am facing NPE.

loud.api.ApiServlet] (32533355@qtp-5278898-32:null) ===END===  10.144.6.32 -- 
GET  
command=migrateVolume&storageid=0286375c-d944-36c0-bbac-0e3dd29a583f&volumeid=7f7d8e7a-3f88-450d-aa86-eb5af9891564&response=json&sessionkey=fjtX5OKeJHLBox%2BNZ37O52Ktqzk%3D&_=1372764941425
2013-07-02 17:05:15,113 DEBUG [storage.volume.VolumeServiceImpl] 
(Job-Executor-6:job-18) Failed to copy volume
java.lang.NullPointerException
        at com.cloud.storage.VolumeVO.<init>(VolumeVO.java:172)
        at 
org.apache.cloudstack.storage.volume.VolumeServiceImpl.duplicateVolumeOnAnotherStorage(VolumeServiceImpl.java:482)
        at 
org.apache.cloudstack.storage.volume.VolumeServiceImpl.copyVolume(VolumeServiceImpl.java:526)
        at 
com.cloud.storage.VolumeManagerImpl.migrateVolume(VolumeManagerImpl.java:2110)
        at 
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at 
com.cloud.storage.VolumeManagerImpl.migrateVolume(VolumeManagerImpl.java:2102)
        at 
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at 
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd.execute(MigrateVolumeCmd.java:103)
        at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
        at 
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
        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:1110)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:722)
2013-07-02 17:05:15,114 DEBUG [cloud.storage.VolumeManagerImpl] 
(Job-Executor-6:job-18) migrate volume failed:java.lang.NullPointerException


The reported issue with the log and exception I got are different.

Please check on the latest build.
                
> [ZWPS]NPE while finding storage pools for migration
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-3264
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3264
>             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: vmware deployment , esxi 5.1
>            Reporter: Srikanteswararao Talluri
>            Assignee: Rajesh Battala
>            Priority: Blocker
>             Fix For: 4.2.0
>
>
> Steps to reproduce:
> =============
> Issue findStoragePoolsForMigration API for a volume
> ===START===  10.252.192.7 -- GET  
> command=findStoragePoolsForMigration&id=02e0e77b-59dd-4bc4-a3b8-ba3914212883&response=json&sessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D&_=1372404084373
> 2013-06-28 18:16:45,204 ERROR [cloud.api.ApiServer] (catalina-exec-16:null) 
> unhandled exception executing api command: findStoragePoolsForMigration
> java.lang.NullPointerException
>       at 
> com.cloud.server.ManagementServerImpl.listStoragePoolsForMigrationOfVolume(ManagementServerImpl.java:1336)
>       at 
> org.apache.cloudstack.api.command.admin.storage.FindStoragePoolsForMigrationCmd.execute(FindStoragePoolsForMigrationCmd.java:72)
>       at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
>       at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
>       at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
>       at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
>       at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
>       at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>       at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>       at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>       at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>       at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>       at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>       at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>       at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>       at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>       at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>       at 
> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
>       at 
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
>       at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
>       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)
> 2013-06-28 18:16:45,207 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) 
> ===END===  10.252.192.7 -- GET  
> command=findStoragePoolsForMigration&id=02e0e77b-59dd-4bc4-a3b8-ba3914212883&response=json&sessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D&_=1372404084373

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