search for: asyncproc

...way: > > while p.poll() is None: the problem is proc.stdout.read(1) didn't raise and error when the stream closed but return ''. its a CPopen behaviour and works differently in subprocess. > ... > > p.returncode calling wait is non-standard feature in vdsm AsyncProc > wrapper. This is > the object used by v2v vdsm module, so there accessing p.returncode does call > p.poll(). > > These non-standard apis will be removed from vdsm, please do not use them. > > >>> c = p.stdout.read(1) > >>> print c > >>&gt...

> On 30 Mar 2016, at 11:49, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Wed, Mar 30, 2016 at 12:19:35PM +0300, Shahar Havivi wrote: >> Hi, >> >> We encounter a problem in VDSM project that virt-v2v become zombie task while >> importing vm from vmware. >> When virt-v2v is in 'copy disk' mode and we someone deletes the vm at vmware

...dable', 'bbb'] >>> p = CPopen(cmd, env=env) >>> while p.returncode is None: p.returncode just return the instance variable, there is no wait() involved. The right way: while p.poll() is None: ... p.returncode calling wait is non-standard feature in vdsm AsyncProc wrapper. This is the object used by v2v vdsm module, so there accessing p.returncode does call p.poll(). These non-standard apis will be removed from vdsm, please do not use them. >>> c = p.stdout.read(1) >>> print c >>> -------------------------------------------...

...sed but return ''. > its a CPopen behaviour and works differently in subprocess. No, it works the same in both, this was just a bug in our code. Fixed in https://gerrit.ovirt.org/55477 > >> ... >> >> p.returncode calling wait is non-standard feature in vdsm AsyncProc >> wrapper. This is >> the object used by v2v vdsm module, so there accessing p.returncode does call >> p.poll(). >> >> These non-standard apis will be removed from vdsm, please do not use them. >> >> >>> c = p.stdout.read(1) >> >>&g...