Here's the SHA for the VMware-snapshot fix I put into 4.4-forward (to be cherry picked by Daan to 4.4):
54c0df56dc03d20ef1d9804d8695c3f6584470f8 On Wed, Apr 23, 2014 at 1:40 PM, Mike Tutkowski < [email protected]> wrote: > I fixed this "path" issue. > > I'll check the code in in a bit and e-mail the SHA for anyone who might be > interested in the change to double check what I changed to correct the > issue. > > > On Wed, Apr 23, 2014 at 9:59 AM, Mike Tutkowski < > [email protected]> wrote: > >> Hi, >> >> 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. >> >> Can anyone confirm or deny this as a problem? >> >> Thanks! >> >> -- >> *Mike Tutkowski* >> *Senior CloudStack Developer, SolidFire Inc.* >> e: [email protected] >> o: 303.746.7302 >> Advancing the way the world uses the >> cloud<http://solidfire.com/solution/overview/?video=play> >> *(tm)* >> > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: [email protected] > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *(tm)* > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: [email protected] o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *(tm)*
