Re: [ovirt-devel] Can't add DC with API v4 - client issue

2016-10-14 Thread Ravi Nori 
Also can you please try following command to directly obtain token from
SSO. Can replace engine with FQDN and IP to see if both work

curl -v -k -H "Accept: application/json" 'https://
:443/ovirt-engine/sso/oauth/token?grant_type=password=admin@internal
=123=ovirt-app-api'

You should see output similar to the one below

{"access_token":"K0sBa0D3rLtmNTdMJ-Q4FzOgCtGGY2cSFSCwbLkG94te9nDdmEzHSizsFaOeNMdwOziIv3l2-Uqm8bxWkMpwMA","scope":"ovirt-app-api
ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search
ovirt-ext=token-info:validate","exp":-381399824,"token_type":"bearer"}

Thanks

Ravi

On Fri, Oct 14, 2016 at 4:00 PM, Yaniv Kaul  wrote:

> On Oct 14, 2016 7:13 PM, "Ravi Nori"  wrote:
> >
> > SSO configuration looks good.
> >
> > Can you please share any additional httpd configuration in
> /etc/httpd/conf.d. Anything to do with LocationMatch for ovirt-engine urls.
>
> This is a standard ovirt-system-tests on Lago installation, nothing out of
> the ordinary,  but I'll check.
> Y.
>
> >
> > On Fri, Oct 14, 2016 at 12:52 PM, Yaniv Kaul  wrote:
> >>
> >>
> >>
> >> On Fri, Oct 14, 2016 at 3:50 PM, Ravi Nori  wrote:
> >>>
> >>> Hi Yaniv,
> >>>
> >>> Can you check the output of https::///ovirt-engine/sso/status
> in your browser and see if the SSO service is active.
> >>>
> >>> If SSO is deployed, you should see an output similar to the one below.
> Also are you able to login to webadmin using the browser?
> >>
> >>
> >> I am able to login using the webui.
> >>
> >>>
> >>>
> >>> {"status_description":"SSO Webapp Deployed","version":"0","
> status":"active"}
> >>
> >>
> >> Indeed:
> >> {"status_description":"SSO Webapp Deployed","version":"0","
> status":"active"}
> >>
> >> (not sure what 'version 0' means?)
> >>
> >>>
> >>>
> >>> Please share the content of /etc/ovirt-engine/engine.conf.
> d/11-setup-sso.conf
> >>
> >>
> >> [root@lago-basic-suite-master-engine ~]# cat
> /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf
> >> ENGINE_SSO_CLIENT_ID="ovirt-engine-core"
> >> ENGINE_SSO_CLIENT_SECRET="bsOabtD7gE2McwLe80P109UV800XLx4O"
> >> ENGINE_SSO_AUTH_URL="https://${ENGINE_FQDN}:443/ovirt-engine/sso;
> >> ENGINE_SSO_SERVICE_URL="https://localhost:443/ovirt-engine/sso;
> >> ENGINE_SSO_SERVICE_SSL_VERIFY_HOST=false
> >> ENGINE_SSO_SERVICE_SSL_VERIFY_CHAIN=true
> >> SSO_ALTERNATE_ENGINE_FQDNS=""
> >> SSO_ENGINE_URL="https://${ENGINE_FQDN}:443/ovirt-engine/;
> >>
> >>
> >> Thanks,
> >> Y.
> >>
> >>
> >>>
> >>>
> >>> Thanks
> >>>
> >>> Ravi
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Fri, Oct 14, 2016 at 7:57 AM, Juan Hernández 
> wrote:
> 
>  On 10/14/2016 01:45 PM, Yaniv Kaul wrote:
>  >
>  >
>  > On Thu, Oct 13, 2016 at 11:13 AM, Juan Hernández <
> jhern...@redhat.com
>  > > wrote:
>  >
>  > On 10/13/2016 12:04 AM, Yaniv Kaul wrote:
>  > > On Fri, Oct 7, 2016 at 10:44 PM, Yaniv Kaul  
>  > > >> wrote:
>  > >
>  > > I'm trying on FC24, using
>  > >
>  >  python-ovirt-engine-sdk4-4.1.0-0.0.20161003git056315d.fc24.x86_64
> to
>  > > add a DC, and failing - against master. The client is
> unhappy:
>  > > File
>  > >
>  >  "/home/ykaul/ovirt-system-tests/basic-suite-master/test-
> scenarios/002_bootstrap.py",
>  > > line 98, in add_dc4
>  > > version=sdk4.types.Version(
> major=DC_VER_MAJ,minor=DC_VER_MIN),
>  > >   File "/usr/lib64/python2.7/site-
> packages/ovirtsdk4/services.py",
>  > > line 4347, in add
>  > > response = self._connection.send(request)
>  > >   File "/usr/lib64/python2.7/site-
> packages/ovirtsdk4/__init__.py",
>  > > line 276, in send
>  > > return self.__send(request)
>  > >   File "/usr/lib64/python2.7/site-
> packages/ovirtsdk4/__init__.py",
>  > > line 298, in __send
>  > > self._sso_token = self._get_access_token()
>  > >   File "/usr/lib64/python2.7/site-
> packages/ovirtsdk4/__init__.py",
>  > > line 460, in _get_access_token
>  > > sso_response = self._get_sso_response(self._sso_url,
>  > post_data)
>  > >   File "/usr/lib64/python2.7/site-
> packages/ovirtsdk4/__init__.py",
>  > > line 498, in _get_sso_response
>  > > return json.loads(body_buf.getvalue()
> .decode('utf-8'))
>  > >   File "/usr/lib64/python2.7/json/__init__.py", line
> 339, in loads
>  > > return _default_decoder.decode(s)
>  > >   File "/usr/lib64/python2.7/json/decoder.py", line 364,
> in decode
>  > > obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>  > >   File

Re: [ovirt-devel] Engine Health

2016-10-14 Thread Yaniv Kaul 
On Fri, Oct 14, 2016 at 11:27 PM, Stuart Gott  wrote:

> All,
>
> We're working on a script that stands up an oVirt Engine and adds a node
> to it. The issue is we don't know how long to wait before trying to add a
> node. What we're doing right now is to check the status of the engine using:
>
> https://ENGINE_IP/ovirt-engine/services/health
>
> to determine when the oVirt engine itself has booted. That link reports
> "DB Up!Welcome to Health Status!" as soon as the web UI is accessible, but
> this is not the same thing as having an actual usable cluster attached.
>
> Would it be possible to have separate status messages to distinguish
> between an engine that has/is missing a usable cluster? Is that already
> possible some other way? Blindly waiting for arbitrary time periods is
> error prone.
>

The API also has a test command as well. I don't think we need to extend it
for a specific use case. What about a missing data center? Host? SPM?
You can see in ovirt-system-test for an example that at least checks that
the service is up (and could use the serice health end point as well)
connects to the API and performs a test() against it to verify it works. I
think that overall should suffice.
Y.


>
> Thanks!
>
> Stu
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Engine Health

2016-10-14 Thread Stuart Gott 
All,

We're working on a script that stands up an oVirt Engine and adds a node to
it. The issue is we don't know how long to wait before trying to add a
node. What we're doing right now is to check the status of the engine using:

https://ENGINE_IP/ovirt-engine/services/health

to determine when the oVirt engine itself has booted. That link reports "DB
Up!Welcome to Health Status!" as soon as the web UI is accessible, but this
is not the same thing as having an actual usable cluster attached.

Would it be possible to have separate status messages to distinguish
between an engine that has/is missing a usable cluster? Is that already
possible some other way? Blindly waiting for arbitrary time periods is
error prone.

Thanks!

Stu
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Can't add DC with API v4 - client issue

2016-10-14 Thread Yaniv Kaul 
On Oct 14, 2016 7:13 PM, "Ravi Nori"  wrote:
>
> SSO configuration looks good.
>
> Can you please share any additional httpd configuration in
/etc/httpd/conf.d. Anything to do with LocationMatch for ovirt-engine urls.

This is a standard ovirt-system-tests on Lago installation, nothing out of
the ordinary,  but I'll check.
Y.

>
> On Fri, Oct 14, 2016 at 12:52 PM, Yaniv Kaul  wrote:
>>
>>
>>
>> On Fri, Oct 14, 2016 at 3:50 PM, Ravi Nori  wrote:
>>>
>>> Hi Yaniv,
>>>
>>> Can you check the output of https::///ovirt-engine/sso/status
in your browser and see if the SSO service is active.
>>>
>>> If SSO is deployed, you should see an output similar to the one below.
Also are you able to login to webadmin using the browser?
>>
>>
>> I am able to login using the webui.
>>
>>>
>>>
>>> {"status_description":"SSO Webapp
Deployed","version":"0","status":"active"}
>>
>>
>> Indeed:
>> {"status_description":"SSO Webapp
Deployed","version":"0","status":"active"}
>>
>> (not sure what 'version 0' means?)
>>
>>>
>>>
>>> Please share the content of
/etc/ovirt-engine/engine.conf.d/11-setup-sso.conf
>>
>>
>> [root@lago-basic-suite-master-engine ~]# cat
/etc/ovirt-engine/engine.conf.d/11-setup-sso.conf
>> ENGINE_SSO_CLIENT_ID="ovirt-engine-core"
>> ENGINE_SSO_CLIENT_SECRET="bsOabtD7gE2McwLe80P109UV800XLx4O"
>> ENGINE_SSO_AUTH_URL="https://${ENGINE_FQDN}:443/ovirt-engine/sso;
>> ENGINE_SSO_SERVICE_URL="https://localhost:443/ovirt-engine/sso;
>> ENGINE_SSO_SERVICE_SSL_VERIFY_HOST=false
>> ENGINE_SSO_SERVICE_SSL_VERIFY_CHAIN=true
>> SSO_ALTERNATE_ENGINE_FQDNS=""
>> SSO_ENGINE_URL="https://${ENGINE_FQDN}:443/ovirt-engine/;
>>
>>
>> Thanks,
>> Y.
>>
>>
>>>
>>>
>>> Thanks
>>>
>>> Ravi
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Oct 14, 2016 at 7:57 AM, Juan Hernández 
wrote:

 On 10/14/2016 01:45 PM, Yaniv Kaul wrote:
 >
 >
 > On Thu, Oct 13, 2016 at 11:13 AM, Juan Hernández  > wrote:
 >
 > On 10/13/2016 12:04 AM, Yaniv Kaul wrote:
 > > On Fri, Oct 7, 2016 at 10:44 PM, Yaniv Kaul 
 > > >> wrote:
 > >
 > > I'm trying on FC24, using
 > >
 >
python-ovirt-engine-sdk4-4.1.0-0.0.20161003git056315d.fc24.x86_64 to
 > > add a DC, and failing - against master. The client is
unhappy:
 > > File
 > >
 >
"/home/ykaul/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py",
 > > line 98, in add_dc4
 > >
 version=sdk4.types.Version(major=DC_VER_MAJ,minor=DC_VER_MIN),
 > >   File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
 > > line 4347, in add
 > > response = self._connection.send(request)
 > >   File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
 > > line 276, in send
 > > return self.__send(request)
 > >   File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
 > > line 298, in __send
 > > self._sso_token = self._get_access_token()
 > >   File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
 > > line 460, in _get_access_token
 > > sso_response = self._get_sso_response(self._sso_url,
 > post_data)
 > >   File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
 > > line 498, in _get_sso_response
 > > return json.loads(body_buf.getvalue().decode('utf-8'))
 > >   File "/usr/lib64/python2.7/json/__init__.py", line 339,
in loads
 > > return _default_decoder.decode(s)
 > >   File "/usr/lib64/python2.7/json/decoder.py", line 364,
in decode
 > > obj, end = self.raw_decode(s, idx=_w(s, 0).end())
 > >   File "/usr/lib64/python2.7/json/decoder.py", line 382, in
 > raw_decode
 > > raise ValueError("No JSON object could be decoded")
 > > ValueError: No JSON object could be decoded
 > >
 > >
 > > Surprisingly, I now can't find that RPM of this SDK in
 > > resources.ovirt.org 
 >  now.
 > >
 > > I've tried
 > > with
 >
http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94eeb5.fc24.x86_64.rpm
 > <
http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94eeb5.fc24.x86_64.rpm
>
 > >
 >  <
http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94eeb5.fc24.x86_64.rpm
 > <

Re: [ovirt-devel] Can't add DC with API v4 - client issue

2016-10-14 Thread Ravi Nori 
SSO configuration looks good.

Can you please share any additional httpd configuration in
/etc/httpd/conf.d. Anything to do with LocationMatch for ovirt-engine urls.

On Fri, Oct 14, 2016 at 12:52 PM, Yaniv Kaul  wrote:

>
>
> On Fri, Oct 14, 2016 at 3:50 PM, Ravi Nori  wrote:
>
>> Hi Yaniv,
>>
>> Can you check the output of https::///ovirt-engine/sso/status in
>> your browser and see if the SSO service is active.
>>
>> If SSO is deployed, you should see an output similar to the one below.
>> Also are you able to login to webadmin using the browser?
>>
>
> I am able to login using the webui.
>
>
>>
>> {"status_description":"SSO Webapp Deployed","version":"0","statu
>> s":"active"}
>>
>
> Indeed:
> {"status_description":"SSO Webapp Deployed","version":"0","
> status":"active"}
>
> (not sure what 'version 0' means?)
>
>
>>
>> Please share the content of /etc/ovirt-engine/engine.conf.
>> d/11-setup-sso.conf
>>
>
> [root@lago-basic-suite-master-engine ~]# cat
> /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf
> ENGINE_SSO_CLIENT_ID="ovirt-engine-core"
> ENGINE_SSO_CLIENT_SECRET="bsOabtD7gE2McwLe80P109UV800XLx4O"
> ENGINE_SSO_AUTH_URL="https://${ENGINE_FQDN}:443/ovirt-engine/sso;
> ENGINE_SSO_SERVICE_URL="https://localhost:443/ovirt-engine/sso;
> ENGINE_SSO_SERVICE_SSL_VERIFY_HOST=false
> ENGINE_SSO_SERVICE_SSL_VERIFY_CHAIN=true
> SSO_ALTERNATE_ENGINE_FQDNS=""
> SSO_ENGINE_URL="https://${ENGINE_FQDN}:443/ovirt-engine/;
>
>
> Thanks,
> Y.
>
>
>
>>
>> Thanks
>>
>> Ravi
>>
>>
>>
>>
>>
>> On Fri, Oct 14, 2016 at 7:57 AM, Juan Hernández 
>> wrote:
>>
>>> On 10/14/2016 01:45 PM, Yaniv Kaul wrote:
>>> >
>>> >
>>> > On Thu, Oct 13, 2016 at 11:13 AM, Juan Hernández >> > > wrote:
>>> >
>>> > On 10/13/2016 12:04 AM, Yaniv Kaul wrote:
>>> > > On Fri, Oct 7, 2016 at 10:44 PM, Yaniv Kaul >> 
>>> > > >> wrote:
>>> > >
>>> > > I'm trying on FC24, using
>>> > >
>>> >  python-ovirt-engine-sdk4-4.1.0-0.0.20161003git056315d.fc24.x86_64
>>> to
>>> > > add a DC, and failing - against master. The client is
>>> unhappy:
>>> > > File
>>> > >
>>> >  "/home/ykaul/ovirt-system-tests/basic-suite-master/test-scen
>>> arios/002_bootstrap.py",
>>> > > line 98, in add_dc4
>>> > > version=sdk4.types.Version(ma
>>> jor=DC_VER_MAJ,minor=DC_VER_MIN),
>>> > >   File "/usr/lib64/python2.7/site-pac
>>> kages/ovirtsdk4/services.py",
>>> > > line 4347, in add
>>> > > response = self._connection.send(request)
>>> > >   File "/usr/lib64/python2.7/site-pac
>>> kages/ovirtsdk4/__init__.py",
>>> > > line 276, in send
>>> > > return self.__send(request)
>>> > >   File "/usr/lib64/python2.7/site-pac
>>> kages/ovirtsdk4/__init__.py",
>>> > > line 298, in __send
>>> > > self._sso_token = self._get_access_token()
>>> > >   File "/usr/lib64/python2.7/site-pac
>>> kages/ovirtsdk4/__init__.py",
>>> > > line 460, in _get_access_token
>>> > > sso_response = self._get_sso_response(self._sso_url,
>>> > post_data)
>>> > >   File "/usr/lib64/python2.7/site-pac
>>> kages/ovirtsdk4/__init__.py",
>>> > > line 498, in _get_sso_response
>>> > > return json.loads(body_buf.getvalue().decode('utf-8'))
>>> > >   File "/usr/lib64/python2.7/json/__init__.py", line 339,
>>> in loads
>>> > > return _default_decoder.decode(s)
>>> > >   File "/usr/lib64/python2.7/json/decoder.py", line 364, in
>>> decode
>>> > > obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>>> > >   File "/usr/lib64/python2.7/json/decoder.py", line 382, in
>>> > raw_decode
>>> > > raise ValueError("No JSON object could be decoded")
>>> > > ValueError: No JSON object could be decoded
>>> > >
>>> > >
>>> > > Surprisingly, I now can't find that RPM of this SDK in
>>> > > resources.ovirt.org 
>>> >  now.
>>> > >
>>> > > I've tried
>>> > > with
>>> > http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc
>>> 24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94e
>>> eb5.fc24.x86_64.rpm
>>> > >> c24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94
>>> eeb5.fc24.x86_64.rpm>
>>> > >
>>> >  >> 24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94e
>>> eb5.fc24.x86_64.rpm
>>> > >> c24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94
>>> eeb5.fc24.x86_64.rpm>>
>>> > >
>>> > > - same result.

Re: [ovirt-devel] Can't add DC with API v4 - client issue

2016-10-14 Thread Yaniv Kaul 
On Fri, Oct 14, 2016 at 3:50 PM, Ravi Nori  wrote:

> Hi Yaniv,
>
> Can you check the output of https::///ovirt-engine/sso/status in
> your browser and see if the SSO service is active.
>
> If SSO is deployed, you should see an output similar to the one below.
> Also are you able to login to webadmin using the browser?
>

I am able to login using the webui.


>
> {"status_description":"SSO Webapp Deployed","version":"0","
> status":"active"}
>

Indeed:
{"status_description":"SSO Webapp Deployed","version":"0","status":"active"}

(not sure what 'version 0' means?)


>
> Please share the content of /etc/ovirt-engine/engine.conf.
> d/11-setup-sso.conf
>

[root@lago-basic-suite-master-engine ~]# cat
/etc/ovirt-engine/engine.conf.d/11-setup-sso.conf
ENGINE_SSO_CLIENT_ID="ovirt-engine-core"
ENGINE_SSO_CLIENT_SECRET="bsOabtD7gE2McwLe80P109UV800XLx4O"
ENGINE_SSO_AUTH_URL="https://${ENGINE_FQDN}:443/ovirt-engine/sso;
ENGINE_SSO_SERVICE_URL="https://localhost:443/ovirt-engine/sso;
ENGINE_SSO_SERVICE_SSL_VERIFY_HOST=false
ENGINE_SSO_SERVICE_SSL_VERIFY_CHAIN=true
SSO_ALTERNATE_ENGINE_FQDNS=""
SSO_ENGINE_URL="https://${ENGINE_FQDN}:443/ovirt-engine/;


Thanks,
Y.



>
> Thanks
>
> Ravi
>
>
>
>
>
> On Fri, Oct 14, 2016 at 7:57 AM, Juan Hernández 
> wrote:
>
>> On 10/14/2016 01:45 PM, Yaniv Kaul wrote:
>> >
>> >
>> > On Thu, Oct 13, 2016 at 11:13 AM, Juan Hernández > > > wrote:
>> >
>> > On 10/13/2016 12:04 AM, Yaniv Kaul wrote:
>> > > On Fri, Oct 7, 2016 at 10:44 PM, Yaniv Kaul > 
>> > > >> wrote:
>> > >
>> > > I'm trying on FC24, using
>> > >
>> >  python-ovirt-engine-sdk4-4.1.0-0.0.20161003git056315d.fc24.x86_64
>> to
>> > > add a DC, and failing - against master. The client is unhappy:
>> > > File
>> > >
>> >  "/home/ykaul/ovirt-system-tests/basic-suite-master/test-scen
>> arios/002_bootstrap.py",
>> > > line 98, in add_dc4
>> > > version=sdk4.types.Version(ma
>> jor=DC_VER_MAJ,minor=DC_VER_MIN),
>> > >   File "/usr/lib64/python2.7/site-pac
>> kages/ovirtsdk4/services.py",
>> > > line 4347, in add
>> > > response = self._connection.send(request)
>> > >   File "/usr/lib64/python2.7/site-pac
>> kages/ovirtsdk4/__init__.py",
>> > > line 276, in send
>> > > return self.__send(request)
>> > >   File "/usr/lib64/python2.7/site-pac
>> kages/ovirtsdk4/__init__.py",
>> > > line 298, in __send
>> > > self._sso_token = self._get_access_token()
>> > >   File "/usr/lib64/python2.7/site-pac
>> kages/ovirtsdk4/__init__.py",
>> > > line 460, in _get_access_token
>> > > sso_response = self._get_sso_response(self._sso_url,
>> > post_data)
>> > >   File "/usr/lib64/python2.7/site-pac
>> kages/ovirtsdk4/__init__.py",
>> > > line 498, in _get_sso_response
>> > > return json.loads(body_buf.getvalue().decode('utf-8'))
>> > >   File "/usr/lib64/python2.7/json/__init__.py", line 339, in
>> loads
>> > > return _default_decoder.decode(s)
>> > >   File "/usr/lib64/python2.7/json/decoder.py", line 364, in
>> decode
>> > > obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>> > >   File "/usr/lib64/python2.7/json/decoder.py", line 382, in
>> > raw_decode
>> > > raise ValueError("No JSON object could be decoded")
>> > > ValueError: No JSON object could be decoded
>> > >
>> > >
>> > > Surprisingly, I now can't find that RPM of this SDK in
>> > > resources.ovirt.org 
>> >  now.
>> > >
>> > > I've tried
>> > > with
>> > http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc
>> 24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94e
>> eb5.fc24.x86_64.rpm
>> > > c24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94
>> eeb5.fc24.x86_64.rpm>
>> > >
>> >  > 24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94e
>> eb5.fc24.x86_64.rpm
>> > > c24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94
>> eeb5.fc24.x86_64.rpm>>
>> > >
>> > > - same result.
>> > >
>> > > Did not see anything obvious on server or engine logs.
>> > > The code:
>> > > def add_dc4(api):
>> > > nt.assert_true(api != None)
>> > > dcs_service = api.system_service().data_centers_service()
>> > > nt.assert_true(
>> > > dc = dcs_service.add(
>> > > sdk4.types.DataCenter(
>> > >

[ovirt-devel] Use six for smoothing over the differences between the Python

2016-10-14 Thread Suramya Shah 
Hi,
just wanted to share this utility .It might be helpful in many project
modifications.
https://pythonhosted.org/six/
https://pypi.python.org/pypi/six
Thanks
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Can't add DC with API v4 - client issue

2016-10-14 Thread Ravi Nori 
Hi Yaniv,

Can you check the output of https::///ovirt-engine/sso/status in
your browser and see if the SSO service is active.

If SSO is deployed, you should see an output similar to the one below. Also
are you able to login to webadmin using the browser?

{"status_description":"SSO Webapp Deployed","version":"0","status":"active"}

Please share the content of
/etc/ovirt-engine/engine.conf.d/11-setup-sso.conf

Thanks

Ravi





On Fri, Oct 14, 2016 at 7:57 AM, Juan Hernández  wrote:

> On 10/14/2016 01:45 PM, Yaniv Kaul wrote:
> >
> >
> > On Thu, Oct 13, 2016 at 11:13 AM, Juan Hernández  > > wrote:
> >
> > On 10/13/2016 12:04 AM, Yaniv Kaul wrote:
> > > On Fri, Oct 7, 2016 at 10:44 PM, Yaniv Kaul  
> > > >> wrote:
> > >
> > > I'm trying on FC24, using
> > >
> >  python-ovirt-engine-sdk4-4.1.0-0.0.20161003git056315d.fc24.x86_64
> to
> > > add a DC, and failing - against master. The client is unhappy:
> > > File
> > >
> >  "/home/ykaul/ovirt-system-tests/basic-suite-master/test-
> scenarios/002_bootstrap.py",
> > > line 98, in add_dc4
> > > version=sdk4.types.Version(major=DC_VER_MAJ,minor=DC_VER_
> MIN),
> > >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.
> py",
> > > line 4347, in add
> > > response = self._connection.send(request)
> > >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.
> py",
> > > line 276, in send
> > > return self.__send(request)
> > >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.
> py",
> > > line 298, in __send
> > > self._sso_token = self._get_access_token()
> > >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.
> py",
> > > line 460, in _get_access_token
> > > sso_response = self._get_sso_response(self._sso_url,
> > post_data)
> > >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.
> py",
> > > line 498, in _get_sso_response
> > > return json.loads(body_buf.getvalue().decode('utf-8'))
> > >   File "/usr/lib64/python2.7/json/__init__.py", line 339, in
> loads
> > > return _default_decoder.decode(s)
> > >   File "/usr/lib64/python2.7/json/decoder.py", line 364, in
> decode
> > > obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> > >   File "/usr/lib64/python2.7/json/decoder.py", line 382, in
> > raw_decode
> > > raise ValueError("No JSON object could be decoded")
> > > ValueError: No JSON object could be decoded
> > >
> > >
> > > Surprisingly, I now can't find that RPM of this SDK in
> > > resources.ovirt.org 
> >  now.
> > >
> > > I've tried
> > > with
> > http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/
> fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.
> 20161004gitf94eeb5.fc24.x86_64.rpm
> >  fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.
> 20161004gitf94eeb5.fc24.x86_64.rpm>
> > >
> >   fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.
> 20161004gitf94eeb5.fc24.x86_64.rpm
> >  fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.
> 20161004gitf94eeb5.fc24.x86_64.rpm>>
> > >
> > > - same result.
> > >
> > > Did not see anything obvious on server or engine logs.
> > > The code:
> > > def add_dc4(api):
> > > nt.assert_true(api != None)
> > > dcs_service = api.system_service().data_centers_service()
> > > nt.assert_true(
> > > dc = dcs_service.add(
> > > sdk4.types.DataCenter(
> > > name=DC_NAME4,
> > > description='APIv4 DC',
> > > local=False,
> > >
> > > version=sdk4.types.Version(major=DC_VER_MAJ,minor=DC_VER_MIN),
> > > ),
> > > )
> > > )
> > >
> > >
> > > And the api object is from:
> > > return sdk4.Connection(
> > > url=url,
> > > username=constants.ENGINE_USER,
> > >
> >  password=str(self.metadata['ovirt-engine-password']),
> > > insecure=True,
> > > debug=True,
> > > )
> > >
> > >
> > > The clue is actually on the HTTPd logs:
> > > 192.168.203.1 - - [12/Oct/2016:17:56:27 -0400] "POST
> > > /ovirt-engine/sso/oauth/token HTTP/1.1" 404

Re: [ovirt-devel] Can't add DC with API v4 - client issue

2016-10-14 Thread Juan Hernández 
On 10/14/2016 01:45 PM, Yaniv Kaul wrote:
> 
> 
> On Thu, Oct 13, 2016 at 11:13 AM, Juan Hernández  > wrote:
> 
> On 10/13/2016 12:04 AM, Yaniv Kaul wrote:
> > On Fri, Oct 7, 2016 at 10:44 PM, Yaniv Kaul  
> > >> wrote:
> >
> > I'm trying on FC24, using
> >   
>  python-ovirt-engine-sdk4-4.1.0-0.0.20161003git056315d.fc24.x86_64 to
> > add a DC, and failing - against master. The client is unhappy:
> > File
> >   
>  
> "/home/ykaul/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py",
> > line 98, in add_dc4
> > version=sdk4.types.Version(major=DC_VER_MAJ,minor=DC_VER_MIN),
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
> > line 4347, in add
> > response = self._connection.send(request)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
> > line 276, in send
> > return self.__send(request)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
> > line 298, in __send
> > self._sso_token = self._get_access_token()
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
> > line 460, in _get_access_token
> > sso_response = self._get_sso_response(self._sso_url,
> post_data)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
> > line 498, in _get_sso_response
> > return json.loads(body_buf.getvalue().decode('utf-8'))
> >   File "/usr/lib64/python2.7/json/__init__.py", line 339, in loads
> > return _default_decoder.decode(s)
> >   File "/usr/lib64/python2.7/json/decoder.py", line 364, in decode
> > obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> >   File "/usr/lib64/python2.7/json/decoder.py", line 382, in
> raw_decode
> > raise ValueError("No JSON object could be decoded")
> > ValueError: No JSON object could be decoded
> >
> >
> > Surprisingly, I now can't find that RPM of this SDK in
> > resources.ovirt.org 
>  now.
> >
> > I've tried
> > with
> 
> http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.20161004gitf94eeb5.fc24.x86_64.rpm
> 
> 
> >   
>  
>  
> >
> >
> > - same result.
> >
> > Did not see anything obvious on server or engine logs.
> > The code:
> > def add_dc4(api):
> > nt.assert_true(api != None)
> > dcs_service = api.system_service().data_centers_service()
> > nt.assert_true(
> > dc = dcs_service.add(
> > sdk4.types.DataCenter(
> > name=DC_NAME4,
> > description='APIv4 DC',
> > local=False,
> >
> > version=sdk4.types.Version(major=DC_VER_MAJ,minor=DC_VER_MIN),
> > ),
> > )
> > )
> >
> >
> > And the api object is from:
> > return sdk4.Connection(
> > url=url,
> > username=constants.ENGINE_USER,
> >   
>  password=str(self.metadata['ovirt-engine-password']),
> > insecure=True,
> > debug=True,
> > )
> >
> >
> > The clue is actually on the HTTPd logs:
> > 192.168.203.1 - - [12/Oct/2016:17:56:27 -0400] "POST
> > /ovirt-engine/sso/oauth/token HTTP/1.1" 404 74
> >
> > And indeed, from the deubg log:
> > begin captured logging << \n
> > root: DEBUG: Trying 192.168.203.3...\n
> > root: DEBUG: Connected to 192.168.203.3 (192.168.203.3) port 443
> (#0)\n
> > root: DEBUG: Initializing NSS with certpath: sql:/etc/pki/nssdb\n
> > root: DEBUG: skipping SSL peer certificate verification\n
> > root: DEBUG: ALPN/NPN, server did not agree to a protocol\n
> > root: DEBUG: SSL connection using
> TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256\n
> > root: DEBUG: Server certificate:\n
> > root: DEBUG: subject: CN=engine,O=Test,C=US\n
> > root: DEBUG: start date: Oct 11 21:55:29 2016 GMT\n
>

Re: [ovirt-devel] Can't add DC with API v4 - client issue

2016-10-14 Thread Yaniv Kaul 
On Thu, Oct 13, 2016 at 11:13 AM, Juan Hernández 
wrote:

> On 10/13/2016 12:04 AM, Yaniv Kaul wrote:
> > On Fri, Oct 7, 2016 at 10:44 PM, Yaniv Kaul  > > wrote:
> >
> > I'm trying on FC24, using
> > python-ovirt-engine-sdk4-4.1.0-0.0.20161003git056315d.fc24.x86_64 to
> > add a DC, and failing - against master. The client is unhappy:
> > File
> > "/home/ykaul/ovirt-system-tests/basic-suite-master/test-
> scenarios/002_bootstrap.py",
> > line 98, in add_dc4
> > version=sdk4.types.Version(major=DC_VER_MAJ,minor=DC_VER_MIN),
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
> > line 4347, in add
> > response = self._connection.send(request)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
> > line 276, in send
> > return self.__send(request)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
> > line 298, in __send
> > self._sso_token = self._get_access_token()
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
> > line 460, in _get_access_token
> > sso_response = self._get_sso_response(self._sso_url, post_data)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py",
> > line 498, in _get_sso_response
> > return json.loads(body_buf.getvalue().decode('utf-8'))
> >   File "/usr/lib64/python2.7/json/__init__.py", line 339, in loads
> > return _default_decoder.decode(s)
> >   File "/usr/lib64/python2.7/json/decoder.py", line 364, in decode
> > obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> >   File "/usr/lib64/python2.7/json/decoder.py", line 382, in
> raw_decode
> > raise ValueError("No JSON object could be decoded")
> > ValueError: No JSON object could be decoded
> >
> >
> > Surprisingly, I now can't find that RPM of this SDK in
> > resources.ovirt.org  now.
> >
> > I've tried
> > with http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/
> fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.
> 20161004gitf94eeb5.fc24.x86_64.rpm
> >  fc24/x86_64/python-ovirt-engine-sdk4-4.0.0-0.1.
> 20161004gitf94eeb5.fc24.x86_64.rpm>
> >
> > - same result.
> >
> > Did not see anything obvious on server or engine logs.
> > The code:
> > def add_dc4(api):
> > nt.assert_true(api != None)
> > dcs_service = api.system_service().data_centers_service()
> > nt.assert_true(
> > dc = dcs_service.add(
> > sdk4.types.DataCenter(
> > name=DC_NAME4,
> > description='APIv4 DC',
> > local=False,
> >
> > version=sdk4.types.Version(major=DC_VER_MAJ,minor=DC_VER_MIN),
> > ),
> > )
> > )
> >
> >
> > And the api object is from:
> > return sdk4.Connection(
> > url=url,
> > username=constants.ENGINE_USER,
> > password=str(self.metadata['
> ovirt-engine-password']),
> > insecure=True,
> > debug=True,
> > )
> >
> >
> > The clue is actually on the HTTPd logs:
> > 192.168.203.1 - - [12/Oct/2016:17:56:27 -0400] "POST
> > /ovirt-engine/sso/oauth/token HTTP/1.1" 404 74
> >
> > And indeed, from the deubg log:
> > begin captured logging << \n
> > root: DEBUG: Trying 192.168.203.3...\n
> > root: DEBUG: Connected to 192.168.203.3 (192.168.203.3) port 443 (#0)\n
> > root: DEBUG: Initializing NSS with certpath: sql:/etc/pki/nssdb\n
> > root: DEBUG: skipping SSL peer certificate verification\n
> > root: DEBUG: ALPN/NPN, server did not agree to a protocol\n
> > root: DEBUG: SSL connection using TLS_ECDHE_RSA_WITH_AES_128_
> GCM_SHA256\n
> > root: DEBUG: Server certificate:\n
> > root: DEBUG: subject: CN=engine,O=Test,C=US\n
> > root: DEBUG: start date: Oct 11 21:55:29 2016 GMT\n
> > root: DEBUG: expire date: Sep 16 21:55:29 2021 GMT\n
> > root: DEBUG: common name: engine\nroot: DEBUG: issuer:
> > CN=engine.38998,O=Test,C=US\n
> > *root: DEBUG: POST /ovirt-engine/sso/oauth/token HTTP/1.1\n*
> > *root: DEBUG: Host: 192.168.203.3\n*
> > *root: DEBUG: User-Agent: PythonSDK/4.1.0a0\n*
> > *root: DEBUG: Accept: application/json\n*
> > *root: DEBUG: Content-Length: 78\n*
> > *root: DEBUG: Content-Type: application/x-www-form-urlencoded\nroot:
> > DEBUG:
> > username=admin%40internal=ovirt-app-api=
> 123_type=password\n*
> > *root: DEBUG: upload completely sent off: 78 out of 78 bytes\n*
> > *root: DEBUG: HTTP/1.1 404 Not Found\n*
> > *root: DEBUG: Date: Wed, 12 Oct 2016 21:56:27 GMT\n*
> > *root: DEBUG: Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips\n*
> > *root: DEBUG: Content-Length: 74\n*
> > *root: DEBUG: Content-Type:

[ovirt-devel] system tests failing on template export

2016-10-14 Thread Evgheni Dereveanchin 
Hello,

We've got several cases today where system tests failed
when attempting to export templates:

http://jenkins.ovirt.org/job/ovirt_master_system-tests/655/testReport/junit/(root)/004_basic_sanity/template_export/

Related engine.log looks something like this:
https://paste.fedoraproject.org/449936/47643643/raw/

I could not find any obvious issues in SPM logs, could someone
please take a look to confirm what may be causing this issue?

Full logs from the test are available here:
http://jenkins.ovirt.org/job/ovirt_master_system-tests/655/artifact/

Regards, 
Evgheni Dereveanchin 
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Upgrade from 3.6 el7 job broken?

2016-10-14 Thread Evgheni Dereveanchin 
Hi Sandro,

This was fixed recently as we added hystrix to the respective puppet manifest:
https://gerrit.ovirt.org/#/c/65291/

I checked the failing job and it seems to be related to a single slave vm0026.
It seems to be broken (doesn't even show up in foreman so never applied 
the puppet class to install missing packages). I took it offline and will check 
what's wrong with it. Thanks for bringing this to my attention!

The jira ticket related to modifying the job and making the build part run
in mock and not rely on host packages is here:
https://ovirt-jira.atlassian.net/browse/OVIRT-616

Regards, 
Evgheni Dereveanchin 

- Original Message -
From: "Sandro Bonazzola" <sbona...@redhat.com>
To: "Roman Mohr" <rm...@redhat.com>, "Evgheni Dereveanchin" 
<edere...@redhat.com>, infra-supp...@ovirt.org
Cc: "infra" <in...@ovirt.org>, "devel" <devel@ovirt.org>
Sent: Friday, 14 October, 2016 9:09:10 AM
Subject: Re: Upgrade from 3.6 el7 job broken?

On Fri, Oct 14, 2016 at 8:59 AM, Roman Mohr <rm...@redhat.com> wrote:

>
>
> On Fri, Oct 14, 2016 at 8:57 AM, Sandro Bonazzola <sbona...@redhat.com>
> wrote:
>
>>
>>
>> On Fri, Oct 14, 2016 at 8:48 AM, Sandro Bonazzola <sbona...@redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Oct 14, 2016 at 8:44 AM, Roman Mohr <rm...@redhat.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I saw a lot of failing builds lately on this job:
>>>>
>>>>   http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-fro
>>>> m-3.6_el7_created/
>>>>
>>>> One log which still exists is:
>>>>
>>>> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-fro
>>>> m-3.6_el7_created/3666/
>>>> It seems like the BUILD ENGINE RPM step is failing, but I can't see any
>>>> reason why:
>>>>
>>>> BUILDING ENGINE RPM
>>>> + create_rpms 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
>>>>  
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo
>>>>  .gitee47dd2
>>>> + local 
>>>> src_rpm=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
>>>> + local 
>>>> dst_dir=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo
>>>> + local release=.gitee47dd2
>>>> + local 
>>>> workspace=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created
>>>> + local 'BUILD_JAVA_OPTS_MAVEN=-XX:MaxPermSize=1G 
>>>> -Dgwt.compiler.localWorkers=1 '
>>>> + local 'BUILD_JAVA_OPTS_GWT=-XX:PermSize=512M -XX:MaxPermSize=1G  
>>>>-Xms1G -Xmx6G '
>>>> + env 'BUILD_JAVA_OPTS_MAVEN=-XX:MaxPermSize=1G 
>>>> -Dgwt.compiler.localWorkers=1 ' 'BUILD_JAVA_OPTS_GWT=-XX:PermSize=512M 
>>>> -XX:MaxPermSize=1G -Xms1G -Xmx6G ' rpmbuild -D 
>>>> 'ovirt_build_minimal 1' -D 'release_suffix .gitee47dd2' -D 
>>>> 'ovirt_build_extra_flags -gs 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/artifactory-ovirt-org-settings.xml'
>>>>  -D '_srcrpmdir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  -D '_specdir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  -D '_sourcedir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  -D '_rpmdir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  -D '_builddir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  --rebuild 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0
 .master.20161014001903.el7.centos.src.rpm
>>>> + return 1
>>>> Build step 'Execute shell' marked build as failure
>>>> Performing Post build task...
>>>> Match found for :.* : True
>>>> Logical operation result is TRUE
>>>> Running script  : #!/bin/bash -x
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>>
>>>
>>> Rpmbuild fails on:
>>> er

Re: [ovirt-devel] engine-setup: ***L:ERROR Internal error: No module named dwh

2016-10-14 Thread Simone Tiraboschi 
On Thu, Oct 13, 2016 at 5:34 PM, Vojtech Szocs  wrote:

> Hi, thanks for fixing this.
>
> (Should we really add DWH as requirement for dev-env? Shouldn't it be
> opt-in instead?)
>

Good point,
on the packaged build DWH setup is now a strict dependency but you can
still choose to install it on a different server.


>
> Thanks,
> Vojtech
>
>
> - Original Message -
> > From: "Simone Tiraboschi" 
> > To: "Vojtech Szocs" 
> > Cc: "devel" 
> > Sent: Thursday, October 13, 2016 12:23:39 AM
> > Subject: Re: [ovirt-devel] engine-setup: ***L:ERROR Internal error: No
> module named dwh
> >
> > Hi,
> > Jakub was right: the issue has been introduced with commit 221c7ed.
> >
> > It affects just the dev env since there we are currently not installing
> (we
> > need to dig this!) DWH which instead is a dependency on the packaged
> builds
> > since 4.0.
> >
> > Patch https://gerrit.ovirt.org/#/c/65409/ fixes it.
> >
> > ciao
> >
> > On Wed, Oct 12, 2016 at 6:08 PM, Vojtech Szocs 
> wrote:
> >
> > > Same problem here.
> > >
> > > Vojtech
> > >
> > >
> > > - Original Message -
> > > > From: "Dominik Holler" 
> > > > To: devel@ovirt.org
> > > > Sent: Wednesday, October 12, 2016 2:39:27 PM
> > > > Subject: Re: [ovirt-devel] engine-setup: ***L:ERROR Internal error:
> No
> > > module named dwh
> > > >
> > > > Hi,
> > > > I got the same error. Is there any experience about this, by now?
> > > > Dominik
> > > >
> > > > On Mon, 10 Oct 2016 15:48:08 -0400 (EDT)
> > > > Jakub Niedermertl  wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > does anyone else experience following error of `engine-setup`?
> > > > >
> > > > > $ ~/target/bin/engine-setup
> > > > > ***L:ERROR Internal error: No module named dwh
> > > > >
> > > > > I have a suspicion it might be related to commit '221c7ed
> packaging:
> > > > > setup: Remove constants duplication'.
> > > > >
> > > > > Jakub
> > > > > ___
> > > > > Devel mailing list
> > > > > Devel@ovirt.org
> > > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > >
> > > > ___
> > > > Devel mailing list
> > > > Devel@ovirt.org
> > > > http://lists.ovirt.org/mailman/listinfo/devel
> > > >
> > > ___
> > > Devel mailing list
> > > Devel@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> > >
> >
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Upgrade from 3.6 el7 job broken?

2016-10-14 Thread Sandro Bonazzola 
On Fri, Oct 14, 2016 at 8:59 AM, Roman Mohr <rm...@redhat.com> wrote:

>
>
> On Fri, Oct 14, 2016 at 8:57 AM, Sandro Bonazzola <sbona...@redhat.com>
> wrote:
>
>>
>>
>> On Fri, Oct 14, 2016 at 8:48 AM, Sandro Bonazzola <sbona...@redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Oct 14, 2016 at 8:44 AM, Roman Mohr <rm...@redhat.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I saw a lot of failing builds lately on this job:
>>>>
>>>>   http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-fro
>>>> m-3.6_el7_created/
>>>>
>>>> One log which still exists is:
>>>>
>>>> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-fro
>>>> m-3.6_el7_created/3666/
>>>> It seems like the BUILD ENGINE RPM step is failing, but I can't see any
>>>> reason why:
>>>>
>>>> BUILDING ENGINE RPM
>>>> + create_rpms 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
>>>>  
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo
>>>>  .gitee47dd2
>>>> + local 
>>>> src_rpm=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
>>>> + local 
>>>> dst_dir=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo
>>>> + local release=.gitee47dd2
>>>> + local 
>>>> workspace=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created
>>>> + local 'BUILD_JAVA_OPTS_MAVEN=-XX:MaxPermSize=1G 
>>>> -Dgwt.compiler.localWorkers=1 '
>>>> + local 'BUILD_JAVA_OPTS_GWT=-XX:PermSize=512M -XX:MaxPermSize=1G  
>>>>-Xms1G -Xmx6G '
>>>> + env 'BUILD_JAVA_OPTS_MAVEN=-XX:MaxPermSize=1G 
>>>> -Dgwt.compiler.localWorkers=1 ' 'BUILD_JAVA_OPTS_GWT=-XX:PermSize=512M 
>>>> -XX:MaxPermSize=1G -Xms1G -Xmx6G ' rpmbuild -D 
>>>> 'ovirt_build_minimal 1' -D 'release_suffix .gitee47dd2' -D 
>>>> 'ovirt_build_extra_flags -gs 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/artifactory-ovirt-org-settings.xml'
>>>>  -D '_srcrpmdir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  -D '_specdir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  -D '_sourcedir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  -D '_rpmdir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  -D '_builddir 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>>>>  --rebuild 
>>>> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
>>>> + return 1
>>>> Build step 'Execute shell' marked build as failure
>>>> Performing Post build task...
>>>> Match found for :.* : True
>>>> Logical operation result is TRUE
>>>> Running script  : #!/bin/bash -x
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>>
>>>
>>> Rpmbuild fails on:
>>> error: Failed build dependencies:
>>> hystrix-core is needed by ovirt-engine-4.1.0-0.0.master.
>>> 20161014004451.git32a6f0c.el7.centos.noarch
>>> hystrix-metrics-event-stream is needed by ovirt-engine-4.1.0-0.0.master.
>>> 20161014004451.git32a6f0c.el7.centos.noarch
>>> Installing /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6
>>> _el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014
>>> 004451.el7.centos.src.rpm
>>>
>>> I'll check why those rpms are missing.
>>>
>>
>> Looks like a temporary failure accessing EPEL repository.
>>
>>
> Hm, maybe it happens on some slaves only, but there always? Because it
> happens pretty often.
> Here is a good example:
>
> https://gerrit.ovirt.org/#/q/status:open+project:ovirt-
> engine+branch:master+topic:AuditLogableBase-inject
>
> All the broken builds are because of this. And that is just after the last
> rebase from Alon. Before

Re: [ovirt-devel] Upgrade from 3.6 el7 job broken?

2016-10-14 Thread Sandro Bonazzola 
On Fri, Oct 14, 2016 at 8:44 AM, Roman Mohr  wrote:

> Hi,
>
> I saw a lot of failing builds lately on this job:
>
>   http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-
> from-3.6_el7_created/
>
> One log which still exists is:
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-
> from-3.6_el7_created/3666/
> It seems like the BUILD ENGINE RPM step is failing, but I can't see any
> reason why:
>
> BUILDING ENGINE RPM
> + create_rpms 
> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
>  
> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo
>  .gitee47dd2
> + local 
> src_rpm=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
> + local 
> dst_dir=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo
> + local release=.gitee47dd2
> + local 
> workspace=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created
> + local 'BUILD_JAVA_OPTS_MAVEN=-XX:MaxPermSize=1G 
> -Dgwt.compiler.localWorkers=1 '
> + local 'BUILD_JAVA_OPTS_GWT=-XX:PermSize=512M -XX:MaxPermSize=1G 
> -Xms1G -Xmx6G '
> + env 'BUILD_JAVA_OPTS_MAVEN=-XX:MaxPermSize=1G 
> -Dgwt.compiler.localWorkers=1 ' 'BUILD_JAVA_OPTS_GWT=-XX:PermSize=512M
>  -XX:MaxPermSize=1G -Xms1G -Xmx6G ' rpmbuild -D 'ovirt_build_minimal 
> 1' -D 'release_suffix .gitee47dd2' -D 'ovirt_build_extra_flags -gs 
> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/artifactory-ovirt-org-settings.xml'
>  -D '_srcrpmdir 
> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>  -D '_specdir 
> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>  -D '_sourcedir 
> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>  -D '_rpmdir 
> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>  -D '_builddir 
> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
>  --rebuild 
> /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
> + return 1
> Build step 'Execute shell' marked build as failure
> Performing Post build task...
> Match found for :.* : True
> Logical operation result is TRUE
> Running script  : #!/bin/bash -x
>
>
> Best Regards,
>
>

Rpmbuild fails on:
error: Failed build dependencies:
hystrix-core is needed by
ovirt-engine-4.1.0-0.0.master.20161014004451.git32a6f0c.el7.centos.noarch
hystrix-metrics-event-stream is needed by
ovirt-engine-4.1.0-0.0.master.20161014004451.git32a6f0c.el7.centos.noarch
Installing
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014004451.el7.centos.src.rpm

I'll check why those rpms are missing.






>
> Roman
>
>
> ___
> Infra mailing list
> in...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Upgrade from 3.6 el7 job broken?

2016-10-14 Thread Roman Mohr 
Hi,

I saw a lot of failing builds lately on this job:


http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_created/

One log which still exists is:

http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_created/3666/
It seems like the BUILD ENGINE RPM step is failing, but I can't see any
reason why:

BUILDING ENGINE RPM
+ create_rpms 
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo
.gitee47dd2
+ local 
src_rpm=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
+ local 
dst_dir=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo
+ local release=.gitee47dd2
+ local 
workspace=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created
+ local 'BUILD_JAVA_OPTS_MAVEN=-XX:MaxPermSize=1G
-Dgwt.compiler.localWorkers=1 '
+ local 'BUILD_JAVA_OPTS_GWT=-XX:PermSize=512M
-XX:MaxPermSize=1G -Xms1G -Xmx6G '
+ env 'BUILD_JAVA_OPTS_MAVEN=-XX:MaxPermSize=1G
-Dgwt.compiler.localWorkers=1 ' 'BUILD_JAVA_OPTS_GWT=
-XX:PermSize=512M -XX:MaxPermSize=1G -Xms1G -Xmx6G '
rpmbuild -D 'ovirt_build_minimal 1' -D 'release_suffix .gitee47dd2' -D
'ovirt_build_extra_flags -gs
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/artifactory-ovirt-org-settings.xml'
-D '_srcrpmdir 
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
-D '_specdir 
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
-D '_sourcedir 
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
-D '_rpmdir 
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
-D '_builddir 
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo'
--rebuild 
/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161014001903.el7.centos.src.rpm
+ return 1
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -x


Best Regards,


Roman
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel