[ https://issues.apache.org/jira/browse/CLOUDSTACK-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702911#comment-13702911 ]
ASF subversion and git services commented on CLOUDSTACK-3264: ------------------------------------------------------------- Commit 2c1a3b5f578fae7b2cd0dba7cc96cb3656a0223b in branch refs/heads/master-6-17-stable from [~vijayendrabvs] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2c1a3b5 ] CLOUDSTACK-3264: [ZWPS]NPE while finding storage pools for migration Description: Filter primary storage pools based on zonewide/clusterwide configuration when considering pools to list for storage migration of volumes. Signed-off-by: Sateesh Chodapuneedi <sate...@apache.org> > [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: Venkata Siva Vijayendra Bhamidipati > 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