[
https://issues.apache.org/jira/browse/CLOUDSTACK-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinav Roy updated CLOUDSTACK-1826:
------------------------------------
Fix Version/s: 4.2.0
> Storage migration not working, seemingly due to uuid vs id
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-1826
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1826
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.1.0
> Reporter: Marcus Sorensen
> Assignee: edison su
> Priority: Blocker
> Fix For: 4.1.0, 4.2.0
>
>
> Getting the following when trying to storage migrate between two primary
> storages:
> 2013-03-27 15:55:47,406 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===START=== 199.58.199.60 -- GET
> command=migrateVirtualMachine&storageid=7dc7d0f2-b436-3493-a925-7a5ecd6d8e8f&virtualmachineid=3bfccf79-d739-4bb8-a841-a2c770977053&response=json&sessionkey=bHE1seGjHXoJ36kFbUmZ%2BTT7T%2BQ%3D&_=1364421339385
> 2013-03-27 15:55:47,416 DEBUG [cloud.api.ApiDispatcher]
> (catalina-exec-15:null) Unable to execute API command
> migratevirtualmachineresponse due to invalid value
> 7dc7d0f2-b436-3493-a925-7a5ecd6d8e8f for parameter storageid
> Tracing this into _storageService.getStoragePool(getStoragePoolId()), we see:
> return _storagePoolDao.findById(id);
> I'm wondering if this needs to be changed to:
> return _storagePoolDao.findPoolByUUID(String.valueOf(id));
> or
> return _storagePoolDao.findByUuid(String.valueOf(id));
> The only other place I see using StorageManager's getStoragePool() is in
> deletepool, and only then when the delete fails, so this may not have popped
> up in other testing.
--
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
