[ https://issues.apache.org/jira/browse/CLOUDSTACK-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709516#comment-13709516 ]
ASF subversion and git services commented on CLOUDSTACK-3545: ------------------------------------------------------------- Commit 04a868231311477dde8e60d4f87a0360ef681dd1 in branch refs/heads/master from [~devdeep] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=04a8682 ] CLOUDSTACK-3545: NPE in listStoragePoolsForMigration api. The volume table no longer holds the pod id, the column is null now. Made a change to get the pod id from the storage pool on which the volume resides. > NPE while listing the storage pools for migrating a volume > ---------------------------------------------------------- > > Key: CLOUDSTACK-3545 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3545 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Affects Versions: 4.2.0 > Reporter: Devdeep Singh > Assignee: Devdeep Singh > Priority: Blocker > Fix For: 4.2.0 > > > 1. Do a cloudstack setup with either XenServer 6.1 or 6.2 hosts. > 2. Add multiple storage pools to the cluster. > 3. Execute a findStoragePoolsForMigration api to list the storage pools > available for migrating a volume. > A NPE is generated. Stack trace looks as follows > 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) -- 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