[
https://issues.apache.org/jira/browse/CLOUDSTACK-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912677#comment-13912677
]
Sanjay Tripathi commented on CLOUDSTACK-6172:
---------------------------------------------
As a part of fix, now copyCommand method will update the newRecord with the
uuid of oldRecord in the “volumes” table and mark the uuid field of the old
record as NULL.
> 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.1.5#6160)
