[
https://issues.apache.org/jira/browse/CLOUDSTACK-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979131#comment-13979131
]
ASF subversion and git services commented on CLOUDSTACK-6488:
-------------------------------------------------------------
Commit 54c0df56dc03d20ef1d9804d8695c3f6584470f8 in cloudstack's branch
refs/heads/4.4-forward from [~mike-tutkowski]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=54c0df5 ]
CLOUDSTACK-6488 Fixed an issue where the "path" field was not being set
properly in the DB when the volume had a snapshot taken of it
> VMware "path" field not set properly in DB in snapshot state
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-6488
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6488
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.4.0
> Environment: Ubuntu 12.04 for CS MS
> Reporter: Mike Tutkowski
> Assignee: Mike Tutkowski
> Fix For: 4.4.0
>
>
> From an e-mail I sent to the CS e-mail list:
> I was testing VMware snapshots with managed storage and believe I see a
> problem with these snapshots with non-managed storage (I was comparing
> results from managed storage to non-managed storage).
> If I take a VMware snapshot, I notice the path field in the volumes table
> references, say, the ROOT-9 VMDK instead of the ROOT-9-000001 VMDK.
> This seems like a bug.
> If I look in vSphere Client, I see that the VM is using ROOT-9-000001.vmdk.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
