On Mon, Sep 3, 2018 at 7:00 PM, Sahina Bose <sabose(a)redhat.com> wrote:
> xargs -I{} sudo -u vdsm dd if={} | tar -tvf -
> 772a3dfe-aee8-45d9-9df5-beddcbf92010.ovf\", u'removes': None,
u'creates':
> None, u'chdir': None, u'stdin': None}}, u'stdout_lines': [],
u'stderr':
> u\"vdsm-client: Command Image.prepare with args {'storagepoolID':
> 'e90984b6-af79-11e8-a2dd-00163e24d363', 'storagedomainID':
> 'b4c84ead-fb7f-4478-acd2-0309d569b9aa', 'volumeID':
> 'b18f30b1-5625-4581-b815-94291b226c79', 'imageID':
> '[u7894c850-665f-47dd-8376-e4da5ae7807f]'} failed:\\n(code=201,
> message=Volume does not exist:
> (u'b18f30b1-5625-4581-b815-94291b226c79',))\\ntar: This does not look like
> a tar archive
>
> Is this a known issue?
>
vdsm log contains
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in
_run
return fn(*args, **kargs)
File "<string>", line 2, in prepareImage
File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 49, in
method
ret = func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 3176, in
prepareImage
raise se.VolumeDoesNotExist(leafUUID)
VolumeDoesNotExist: Volume does not exist:
(u'10730bab-8b24-4001-afde-a83659063c00',)
See
https://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/68...
Any clues as to what's going wrong? (Failing for the last 13 days)
Turned out to be issue with ansible version - the play that filters out the
disks returning wrong results with older ansible?
CI passes with
. Can someone please
merge?
thanks!