From: "Alon Bar-Lev" <alonbl(a)redhat.com>
To: "Doron Fediuck" <dfediuck(a)redhat.com>
Cc: engine-devel(a)ovirt.org
Sent: Tuesday, December 31, 2013 5:28:24 PM
Subject: Re: [Engine-devel] Broken devel setup on Gentoo?
----- Original Message -----
> From: "Doron Fediuck" <dfediuck(a)redhat.com>
> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> Cc: engine-devel(a)ovirt.org
> Sent: Tuesday, December 31, 2013 5:20:24 PM
> Subject: Re: [Engine-devel] Broken devel setup on Gentoo?
>
>
> On 12/31/2013 04:54 PM, Alon Bar-Lev wrote:
> >
> > ----- Original Message -----
> >> From: "Doron Fediuck" <dfediuck(a)redhat.com>
> >> To: engine-devel(a)ovirt.org
> >> Cc: "Alon Bar-Lev" <abarlev(a)redhat.com>
> >> Sent: Tuesday, December 31, 2013 4:50:48 PM
> >> Subject: [Engine-devel] Broken devel setup on Gentoo?
> >>
> >> While refreshing my devel environment, setup fails.
> >> Log file shows this:
> >>
> >> 2013-12-31 16:26:05 DEBUG otopi.plugins.otopi.services.openrc
> >> plugin.executeRaw:366 execute:
('/etc/init.d/ovirt-websocket-proxy',
> >> '-q', 'status'), executable='None', cwd=
> >> 'None', env=None
> >> 2013-12-31 16:26:05 DEBUG otopi.plugins.otopi.services.openrc
> >> plugin.executeRaw:389 execute-result:
> >> ('/etc/init.d/ovirt-websocket-proxy', '-q',
'status'), exception
> >> Traceback (most recent call last):
> >> File "/usr/lib64/python2.7/site-packages/otopi/plugin.py", line
376,
> >> in executeRaw
> >> env=env,
> >> File "/usr/lib64/python2.7/subprocess.py", line 711, in
__init__
> >> errread, errwrite)
> >> File "/usr/lib64/python2.7/subprocess.py", line 1308, in
> >> _execute_child
> >> raise child_exception
> >> OSError: [Errno 2] No such file or directory
> >>
> >> Should there be a redirection to use ovirt-websocket-proxy in a local
> >> script rather than daemon?
> >
http://gerrit.ovirt.org/#/q/I40f061ec6cf658e1d8ec5c3663698ceca7569b38,n,z
> Thanks.
> I'm running on this branch (ovirt-3.3) and still hitting this issue.
> I checked
> packaging/setup/plugins/ovirt-engine-setup/config/websocket_proxy.py
> and I can see the fix (now in line 258), but the issue is still there.
>
Please send setup log file.
Correct, the issue is that setup is trying to acquire service status before stopping.
Fix is available[1]
[1]