[
https://issues.apache.org/jira/browse/CLOUDSTACK-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226167#comment-14226167
]
ASF subversion and git services commented on CLOUDSTACK-6172:
-------------------------------------------------------------
Commit 11eab3d285620b2a62078bd48f6b9e4089ef10e9 in cloudstack's branch
refs/heads/4.3 from sanjeev
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=11eab3d ]
CLOUDSTACK-6172: Adding new test case to verify this fix
Signed-off-by: Rohit Yadav <[email protected]>
Conflicts:
test/integration/component/test_volumes.py
Signed-off-by: sanjeev <[email protected]>
CLOUDSTACK-6172: Fixed review comments provided in RR 25771
(cherry picked from commit 2d19bcb46ad7c78b4842c1f52f552998a33f8836)
Signed-off-by: Rohit Yadav <[email protected]>
> 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)
