<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Thu, May 25, 2017 at 4:00 PM Barak Korren <<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 25 May 2017 at 15:42, Nir Soffer <<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>> wrote:<br>
><br>
> In this case, I don't see how vdsm tests can pollute the host /var/tmp.<br>
><br>
> Vdsm run 2 tests running virt-alignment-scan, one with --help, and one<br>
> with non existing images, so the temporary directory cannot be created<br>
> by these tests.<br>
<br>
As you see in $subject, we are looking for something that is invoking<br>
libgustfs, could vdsm or imageio be doing that?<br></blockquote><div><br></div><div>ovirt-imagio does not invoke any external program.</div><div><br></div><div>Vdsm tests invoke virt-alignment-scan but not in a way that can leave</div><div>anything around:</div><div><br></div><div>LIBGUESTFS_BACKEND=direct virt-alignment-scan --help<br></div><div>LIBGUESTFS_BACKEND=direct virt-alignment-scan --add no-such-file<br></div><div><br></div><div>I don't know about other tests using libguestfs.</div><div><br></div><div>But how a program running inside mock chroot can access host's /var/tmp?</div></div></div>