You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/23 12:39:34 UTC
[jira] [Commented] (CLOUDSTACK-6172) Volume is not retaining same
uuid when migrating from one storage to another.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144648#comment-14144648 ]
ASF subversion and git services commented on CLOUDSTACK-6172:
-------------------------------------------------------------
Commit 2d19bcb46ad7c78b4842c1f52f552998a33f8836 in cloudstack's branch refs/heads/master from sanjeev
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2d19bcb ]
CLOUDSTACK-6172: Adding new test case to verify this fix
Conflicts:
test/integration/component/test_volumes.py
Signed-off-by: sanjeev <sa...@apache.org>
CLOUDSTACK-6172: Fixed review comments provided in RR 25771
> Volume is not retaining same uuid when migrating from one storage to another.
> -----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6172
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6172
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Storage Controller
> Affects Versions: 4.3.0
> Reporter: Sanjay Tripathi
> Assignee: Sanjay Tripathi
> Fix For: 4.4.0
>
>
> Volume migration results in creating a new entry in DB with different uuid, because of this if the user are using the APIs and referring to the same uuid of the volume for there different operations, which is correct as its the same volume; then this error is coming:
> Error "please specify a valid data volume".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)