Hi Markus Yes,
We (VMware 5.5 and CS 4.5) experience also such kind of issues related to path. As a result "under certain conditions", it can result in a broken VM or a VM reset to template. We just experienced this today morning with one of the VMs. We added a monitoring for this state "path out of sync" and manually change the path in the DB but I agree, not a real solution. Regards René On 10/19/2017 11:23 AM, Markus Kosubek wrote: > Hello List, > > we experience a repeating issue in our environment. > > - VMWare Vcenter Server: 6.0.0 > - cloudstack 4.7.1 > > In not yet known circumstances* after Snapshot-Consolidation** in the > Hypervisor, the change of disk-configuration is not recognized by > cloudstack. > > Example: > - Vm runs on a snapshot for a certain period of time, let's say: > i-99-500-VM-00000002.vmdk, like written in cloudstack-db (column 'path' > in table 'volumes') > > - *Consolidation happens* > > - VM stops (there might be a second vmware-based problem here because > this shouldn't happen!) > > - VM's root-disk in vmware is now: i-99-500-VM.vmdk > > - but cloudstack-db still has path 'i-99-500-VM-00000002.vmdk' > > - VM won't start again, because cloudstack does not find root-disk. > > We can fix this then with updating the db manually, but this is of > course not what we want long-term. > > Does anybody of you have experience with issues of that kind? > > Any hints would greatly be appreciated. > > Regards > Markus > > * probably because consolidation takes too long so that cloudstack > thinks this task timed out, but in reality on vmware-site, the task > succeeded at the end > > ** this happens, if snapshots of a vm exist after a certain period of > time, i believe. Not quite sure about the trigger for that >
