On 04/30/2013 01:36 PM, Michael Pasternak wrote:
On 04/30/2013 02:04 PM, Juan Hernandez wrote:
> On 04/30/2013 01:02 PM, Kiril Nesenko wrote:
>> Hi,
>> Can you take a look on this job [1] ?
>>
>> Traceback (most recent call last):
>> File "<string>", line 1, in <module>
>> File "cli/__init__.py", line 3, in <module>
>> from cli.context import ExecutionContext
>> File "cli/context.py", line 38, in <module>
>> from ovirtsdk.infrastructure.errors import \
>> ImportError: No module named ovirtsdk.infrastructure.errors
>> error: Bad exit status from /var/tmp/rpm-tmp.jEpk66 (%build)
>>
>> [1] -
http://jenkins.ovirt.org/job/ovirt-engine-cli_create_rpms/
>>
>> - Kiril
>
> I think that the CLI .spec needs something like this:
>
> diff --git a/ovirt-engine-cli.spec.in b/ovirt-engine-cli.spec.in
> index badfa8d..ca78590 100644
> --- a/ovirt-engine-cli.spec.in
> +++ b/ovirt-engine-cli.spec.in
> @@ -11,6 +11,7 @@ BuildRequires: python2-devel
> BuildRequires: python-setuptools-devel
> BuildRequires: python-ply
> BuildRequires: python-kitchen
> +BuildRequires: ovirt-engine-sdk >= 3.2.0.3
the spec already has this, also there is no change been done in this area.
I am checking the latest upstream code, and it doesn't have the
"BuildRequires", it does have the "Requires". I guess that we are
running this jobs in a machine where ovirt-engine-sdk is not installed.
The backtrace clearly complains about missing
ovirtsdk.infrastructure.errors. Not sure why this happens now and not
before, but it is worth testing: just install ovirt-engine-sdk in the
Jenkins machine and try again.
>
> BuildArch: noarch
>
> And then the ovirt-engine-cli package needs to be installed in the machines that run
the jobs.
not sure about this, afaiu this job only builds rpms, Kiril,
how do you trigger rpm build? and what you do afterwords?
(i cannot reproduce this on my f17)
>
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.