[ovirt-users] Cleanup illegal snapshot

[Nir Soffer]

On Sun, Oct 9, 2016 at 8:33 PM, Markus Stockhausen
<stockhausen at collogia.de> wrote:
> Hi Ala,
>
> that did not help. VDSM log tells me that the delta qcow2 file is missing:
>
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/task.py", line 873, in _run
>     return fn(*args, **kargs)
>   File "/usr/share/vdsm/logUtils.py", line 49, in wrapper
>     res = f(*args, **kwargs)
>   File "/usr/share/vdsm/storage/hsm.py", line 3162, in getVolumeInfo
>     volUUID=volUUID).getInfo()
>   File "/usr/share/vdsm/storage/sd.py", line 457, in produceVolume
>     volUUID)
>   File "/usr/share/vdsm/storage/fileVolume.py", line 58, in __init__
>     volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
>   File "/usr/share/vdsm/storage/volume.py", line 181, in __init__
>     self.validate()
>   File "/usr/share/vdsm/storage/volume.py", line 194, in validate
>     self.validateVolumePath()
>   File "/usr/share/vdsm/storage/fileVolume.py", line 540, in
> validateVolumePath
>     raise se.VolumeDoesNotExist(self.volUUID)
> VolumeDoesNotExist: Volume does not exist:
> (u'c277351d-e2b1-4057-aafb-55d4b607ebae',)
> ...
> Thread-196::ERROR::2016-10-09 19:31:07,037::utils::739::root::(wrapper)
> Unhandled exception
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 736, in
> wrapper
>     return f(*a, **kw)
>   File "/usr/share/vdsm/virt/vm.py", line 5264, in run
>     self.update_base_size()
>   File "/usr/share/vdsm/virt/vm.py", line 5257, in update_base_size
>     self.drive.imageID, topVolUUID)
>   File "/usr/share/vdsm/virt/vm.py", line 5191, in _getVolumeInfo
>     (domainID, volumeID))
> StorageUnavailableError: Unable to get volume info for domain
> 47202573-6e83-42fd-a274-d11f05eca2dd volume
> c277351d-e2b1-4057-aafb-55d4b607ebae

Hi Markus,

I'm sorry for this confusing log,  Vdsm is treating a missing volume
as a horrible
error is a bug, this is expected condition when you query volume info.

We also log 2 exceptions instead of one.

Would file a vdsm storage bug for these issues?

Thanks,
Nir