oVirt infra daily report - unstable production jobs - 78

2016-09-15 Thread jenkins 
Good morning!

Attached is the HTML page with the jenkins status report. You can see it also 
here:
 - 
http://jenkins.ovirt.org/job/system_jenkins-report/78//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins


upstream_report.html
Description: Binary data
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ACTION REQUIKRED] vdsm check merged for 4.0 failing on Lago repository sync

2016-09-15 Thread Sandro Bonazzola 
On Thu, Sep 15, 2016 at 3:15 PM, Eyal Edri  wrote:

> Not sure what more reliable mean,
> can you open an issue in Lago [1]  with info on what needs to be improved?
>
>

https://github.com/lago-project/lago/issues/319


>
> [1] https://github.com/lago-project/lago
>
> On Thu, Sep 15, 2016 at 9:55 AM, Sandro Bonazzola 
> wrote:
>
>> http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_
>> 64/146/console
>>
>> Please either fix lago to be more reliable when syncing repos or
>> configure vdsm tests to use the right repos.
>>
>> Thanks,
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>> 
>>
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>



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

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

Re: [ACTION REQUIKRED] vdsm check merged for 4.0 failing on Lago repository sync

2016-09-15 Thread Eyal Edri 
Not sure what more reliable mean,
can you open an issue in Lago [1]  with info on what needs to be improved?


[1] https://github.com/lago-project/lago

On Thu, Sep 15, 2016 at 9:55 AM, Sandro Bonazzola 
wrote:

> http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/146/console
>
> Please either fix lago to be more reliable when syncing repos or configure
> vdsm tests to use the right repos.
>
> Thanks,
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] [VDSM] build-artifacts failing on master

2016-09-15 Thread Barak Korren 
>
> I'm not sure I understand your point. RPM spec files have %check section
> for pre-build tests. Should we, or should we not, strive to use them?

AFAIK the %check section is only relevant for DS builds, as in US we
have many other places to run tests from (e.g check_patch.sh).

AFAIK by its nature %check only allows for source-level tests (since
you don't have an RPM yet). Source-level tests can and should run
before a patch is merged. The DS build, however, happens long after
the patch is merged, and by the time it does, all source-level issues
should have been checked for.
Therefore, I think making tests run in %check should not be a high priority.

-- 
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Change in ovirt-engine[master]: core: Null-safe ImagesHandler.buildStorageToDiskMap()

2016-09-15 Thread Gil Shinar 
There was an issue in the Jenkins in that time when you've pushed the patch
and the find bugs job had a timeout so it was set to -1
I have retriggered all related jobs and now the patch has +1

On Tue, Sep 13, 2016 at 12:59 PM, Shmuel Melamud 
wrote:

> Hi!
>
> What have been failed is everything is succeeded? ;)
>
> Shmuel
>
> -- Forwarded message --
> From: Jenkins CI 
> Date: Mon, Sep 12, 2016 at 12:08 AM
> Subject: Change in ovirt-engine[master]: core: Null-safe ImagesHandler.
> buildStorageToDiskMap()
> To: Shmuel Leib Melamud 
>
>
> Jenkins CI has posted comments on this change.
>
> Change subject: core: Null-safe ImagesHandler.buildStorageToDiskMap()
> ..
>
>
> Patch Set 1: Continuous-Integration-1
>
> Build Failed
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-fro
> m-master_el7_created/2387/ : SUCCESS
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
> -el7-x86_64/6726/ : SUCCESS
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-fro
> m-4.0_el7_created/2387/ : SUCCESS
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
> -fc24-x86_64/983/ : SUCCESS
>
> --
> To view, visit https://gerrit.ovirt.org/63655
> To unsubscribe, visit https://gerrit.ovirt.org/settings
>
> Gerrit-MessageType: comment
> Gerrit-Change-Id: I61f67c4f088b5782b4879e9dc9721cc156eebc0d
> Gerrit-PatchSet: 1
> Gerrit-Project: ovirt-engine
> Gerrit-Branch: master
> Gerrit-Owner: Shmuel Leib Melamud 
> Gerrit-Reviewer: Arik Hadas 
> Gerrit-Reviewer: Jenkins CI
> Gerrit-Reviewer: Shahar Havivi 
> Gerrit-Reviewer: Shmuel Leib Melamud 
> Gerrit-Reviewer: gerrit-hooks 
> Gerrit-HasComments: No
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] [VDSM] build-artifacts failing on master

2016-09-15 Thread Dan Kenigsberg 
On Thu, Sep 15, 2016 at 01:15:29PM +0300, Barak Korren wrote:
> >
> > I love running tests on the build systems - its gives another layer of
> > assurance that we are going to build a good package for the relevant
> > system/architecture.
> >
> > However, the offending patch makes it impossible on el7-based build
> > system. Can we instead skip the test (on such systems) if the right nose
> > version is not installed?
> >
> > We should file a bug to fix nose on el7.
> >
> 
> IMO test requirements != build req != runtime req.
> 
> It is perfectly valid to use virtualenv and pip to enable using the
> latest and graetest testing tools, but those should __only__ be used
> in a testing environment. Those should not be used in a build
> environment which is designed to be reproducible and hence is
> typically devoid of network access.

That's clear.

> Deploy requirements should be tested, but by their nature those tests
> need to run post-build and hence are better left to integration tests
> like ovirt-system-tests.

I'm not sure I understand your point. RPM spec files have %check section
for pre-build tests. Should we, or should we not, strive to use them?
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ACTION REQUIRED] VDSM master builf failing on NOSE version check

2016-09-15 Thread Sandro Bonazzola 
On Thu, Sep 15, 2016 at 12:25 PM, Dan Kenigsberg  wrote:

> On Thu, Sep 15, 2016 at 11:46:11AM +0200, Sandro Bonazzola wrote:
> > On Thu, Sep 15, 2016 at 11:14 AM, Dan Kenigsberg 
> wrote:
> >
> > > On Thu, Sep 15, 2016 at 08:51:59AM +0200, Sandro Bonazzola wrote:
> > > > *http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-
> > > el7-x86_64/836/console
> > > >  > > el7-x86_64/836/console>*
> > > >
> > > >
> > > > *00:05:37.816* make[1]: Entering directory
> > > > `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-
> > > x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'*00:05:37.817*
> > > > Makefile:980: warning: overriding recipe for target
> > > > `check-recursive'*00:05:37.818* Makefile:516: warning: ignoring old
> > > > recipe for target `check-recursive'*00:05:38.119* Error: NOSE is too
> > > > old, please install NOSE 1.3.7 or later*00:05:38.119* make[1]: ***
> > > > [tests] Error 1
> > >
> > > Yes, we broke it with https://gerrit.ovirt.org/63638 as discussed on
> > >
> > > [VDSM] build-artifacts failing on master
> > >
> > > >
> > > >
> > > > Is a newer version of nose really needed?
> > >
> > > yes.
> > >
> > > > If no: please require a version of nose which is available.
> > > > If yes: we can consider shipping nose in CentOS Virt SIG repos since
> it's
> > > > available for OpenStack repos:
> > > > http://cbs.centos.org/koji/buildinfo?buildID=10186
> > >
> > > This would not solve our problem for RHEL, but it would certainly help
> > > developement upsream. How difficult would it be to add it?
> > >
> >
> > Tagged into ovirt common repo. Please add the following repo to vdsm
> > automation for el7:
> >
> > centos-ovirt-common-candidate ->
> > http://cbs.centos.org/repos/virt7-ovirt-common-candidate/$basearch/os/
> > 
>
> So https://gerrit.ovirt.org/63986 might be enough to fix the current
> job error? (though not future proof for formal brew/koji builds)
>
> Sandro, could you trigger vdsm_master_build-artifacts? My own
> account password on jenkins.ovirt.org is reset again.
>

Worked fine:
http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/839/




>
> Regards,
> Dan.
>



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

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

Re: [ACTION REQUIRED] VDSM master builf failing on NOSE version check

2016-09-15 Thread Dan Kenigsberg 
On Thu, Sep 15, 2016 at 11:46:11AM +0200, Sandro Bonazzola wrote:
> On Thu, Sep 15, 2016 at 11:14 AM, Dan Kenigsberg  wrote:
> 
> > On Thu, Sep 15, 2016 at 08:51:59AM +0200, Sandro Bonazzola wrote:
> > > *http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-
> > el7-x86_64/836/console
> > >  > el7-x86_64/836/console>*
> > >
> > >
> > > *00:05:37.816* make[1]: Entering directory
> > > `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-
> > x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'*00:05:37.817*
> > > Makefile:980: warning: overriding recipe for target
> > > `check-recursive'*00:05:37.818* Makefile:516: warning: ignoring old
> > > recipe for target `check-recursive'*00:05:38.119* Error: NOSE is too
> > > old, please install NOSE 1.3.7 or later*00:05:38.119* make[1]: ***
> > > [tests] Error 1
> >
> > Yes, we broke it with https://gerrit.ovirt.org/63638 as discussed on
> >
> > [VDSM] build-artifacts failing on master
> >
> > >
> > >
> > > Is a newer version of nose really needed?
> >
> > yes.
> >
> > > If no: please require a version of nose which is available.
> > > If yes: we can consider shipping nose in CentOS Virt SIG repos since it's
> > > available for OpenStack repos:
> > > http://cbs.centos.org/koji/buildinfo?buildID=10186
> >
> > This would not solve our problem for RHEL, but it would certainly help
> > developement upsream. How difficult would it be to add it?
> >
> 
> Tagged into ovirt common repo. Please add the following repo to vdsm
> automation for el7:
> 
> centos-ovirt-common-candidate ->
> http://cbs.centos.org/repos/virt7-ovirt-common-candidate/$basearch/os/
> 

So https://gerrit.ovirt.org/63986 might be enough to fix the current
job error? (though not future proof for formal brew/koji builds)

Sandro, could you trigger vdsm_master_build-artifacts? My own
account password on jenkins.ovirt.org is reset again.

Regards,
Dan.
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] [VDSM] build-artifacts failing on master

2016-09-15 Thread Barak Korren 
>
> I love running tests on the build systems - its gives another layer of
> assurance that we are going to build a good package for the relevant
> system/architecture.
>
> However, the offending patch makes it impossible on el7-based build
> system. Can we instead skip the test (on such systems) if the right nose
> version is not installed?
>
> We should file a bug to fix nose on el7.
>

IMO test requirements != build req != runtime req.

It is perfectly valid to use virtualenv and pip to enable using the
latest and graetest testing tools, but those should __only__ be used
in a testing environment. Those should not be used in a build
environment which is designed to be reproducible and hence is
typically devoid of network access.
Deploy requirements should be tested, but by their nature those tests
need to run post-build and hence are better left to integration tests
like ovirt-system-tests.

-- 
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [VDSM] build-artifacts failing on master

2016-09-15 Thread Barak Korren 
On 14 September 2016 at 22:31, Eyal Edri  wrote:
> Its actually a good question to know if standard CI supports versions of
> RPMs.
> Barak - do you know if we can specify in build-artifacts.packages file a
> version requirement?
>
> for e.g python-nose >= 1.3.7
>

You can only use the syntax supported by yum.
Since yum always installs latest by default, a '>=' syntax would not
be useful with it.


-- 
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ACTION REQUIRED] VDSM master builf failing on NOSE version check

2016-09-15 Thread Sandro Bonazzola 
On Thu, Sep 15, 2016 at 11:14 AM, Dan Kenigsberg  wrote:

> On Thu, Sep 15, 2016 at 08:51:59AM +0200, Sandro Bonazzola wrote:
> > *http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-
> el7-x86_64/836/console
> >  el7-x86_64/836/console>*
> >
> >
> > *00:05:37.816* make[1]: Entering directory
> > `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-
> x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'*00:05:37.817*
> > Makefile:980: warning: overriding recipe for target
> > `check-recursive'*00:05:37.818* Makefile:516: warning: ignoring old
> > recipe for target `check-recursive'*00:05:38.119* Error: NOSE is too
> > old, please install NOSE 1.3.7 or later*00:05:38.119* make[1]: ***
> > [tests] Error 1
>
> Yes, we broke it with https://gerrit.ovirt.org/63638 as discussed on
>
> [VDSM] build-artifacts failing on master
>
> >
> >
> > Is a newer version of nose really needed?
>
> yes.
>
> > If no: please require a version of nose which is available.
> > If yes: we can consider shipping nose in CentOS Virt SIG repos since it's
> > available for OpenStack repos:
> > http://cbs.centos.org/koji/buildinfo?buildID=10186
>
> This would not solve our problem for RHEL, but it would certainly help
> developement upsream. How difficult would it be to add it?
>

Tagged into ovirt common repo. Please add the following repo to vdsm
automation for el7:

centos-ovirt-common-candidate ->
http://cbs.centos.org/repos/virt7-ovirt-common-candidate/$basearch/os/





>
> >
> > Please let me know.
> >
> > --
> > Sandro Bonazzola
> > Better technology. Faster innovation. Powered by community collaboration.
> > See how it works at redhat.com
> > 
>



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

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

Re: [ovirt-devel] [VDSM] build-artifacts failing on master

2016-09-15 Thread Dan Kenigsberg 
On Wed, Sep 14, 2016 at 11:28:05PM +0300, Nir Soffer wrote:
> On Wed, Sep 14, 2016 at 10:43 PM, Nir Soffer  wrote:
> > On Wed, Sep 14, 2016 at 10:40 PM, Irit Goihman  wrote:
> >> I think that what's missing in build-artifacts.sh is the following commands
> >> that exist in check-patch.sh:
> >>
> >> easy_install pip
> >> pip install -U nose==1.3.7
> >
> > We cannot do this in brew/koji, you can use only packages from the 
> > distribution
> > when running make rpm.
> 
> The best way to avoid such issues is to remove the "make tests"
> from the %check section in the spec.
> 
> This allows using latest and greatest development tools which are not 
> available
> in brew or koji.
> 
> Here is a quick patch, please review:
> https://gerrit.ovirt.org/63966

I love running tests on the build systems - its gives another layer of
assurance that we are going to build a good package for the relevant
system/architecture.

However, the offending patch makes it impossible on el7-based build
system. Can we instead skip the test (on such systems) if the right nose
version is not installed?

We should file a bug to fix nose on el7.

> 
> >> This should install the right version for nose (that doesn't exist in rhel
> >> yum repos)
> >>
> >> On Wed, Sep 14, 2016 at 10:31 PM, Eyal Edri  wrote:
> >>>
> >>> Its actually a good question to know if standard CI supports versions of
> >>> RPMs.
> >>> Barak - do you know if we can specify in build-artifacts.packages file a
> >>> version requirement?
> >>>
> >>> for e.g python-nose >= 1.3.7
> >>>
> >>> On Wed, Sep 14, 2016 at 10:21 PM, Nir Soffer  wrote:
> 
>  The build-artifacts job is failing on master now with this error:
> 
>  19:09:23 Error: NOSE is too old, please install NOSE 1.3.7 or later
>  19:09:23 make[1]: *** [tests] Error 1
>  19:09:23 make[1]: Leaving directory
> 
>  `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'
>  19:09:23 error: Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
>  19:09:23
>  19:09:23
>  19:09:23 RPM build errors:
>  19:09:23 Bad exit status from /var/tmp/rpm-tmp.LQXOfm (%check)
> 
>  Looks like this patch is the cause:
> 
>  commit 4e729ddd2b243d0953e2de5d31c42fc59859bf23
>  Author: Edward Haas 
>  Date:   Sun Sep 11 14:10:01 2016 +0300
> 
>  build tests: Require NOSE 1.3.7 and up for running tests
> 
>  On RHEL7/Centos7 the provided NOSE version is 1.3.0.
>  CI runs the tests with 1.3.7.
> 
>  To be consistent and avoid different behaviours, assure that the
>  tests
>  are running with a minimum nose version of 1.3.7.
> 
>  Specifically, between 1.3.0 and 1.3.7 a bug has been resolved
>  regarding
>  test labeling and its support with test class inheritance.
> 
>  Change-Id: If79d8624cee1c14a21840e4a08000fc33abb58e5
>  Signed-off-by: Edward Haas 
>  Reviewed-on: https://gerrit.ovirt.org/63638
>  Continuous-Integration: Jenkins CI
>  Reviewed-by: Petr Horáček 
>  Reviewed-by: Irit Goihman 
>  Reviewed-by: Yaniv Bronhaim 
>  Reviewed-by: Piotr Kliczewski 
> 
>  I did not check the details, but it seems we need to revert this patch.
> 
>  Please check and fix.
> 
>  Cheers,
>  Nir
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ACTION REQUIRED] VDSM master builf failing on NOSE version check

2016-09-15 Thread Dan Kenigsberg 
On Thu, Sep 15, 2016 at 08:51:59AM +0200, Sandro Bonazzola wrote:
> *http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/836/console
> *
> 
> 
> *00:05:37.816* make[1]: Entering directory
> `/home/jenkins/workspace/vdsm_master_build-artifacts-el7-x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'*00:05:37.817*
> Makefile:980: warning: overriding recipe for target
> `check-recursive'*00:05:37.818* Makefile:516: warning: ignoring old
> recipe for target `check-recursive'*00:05:38.119* Error: NOSE is too
> old, please install NOSE 1.3.7 or later*00:05:38.119* make[1]: ***
> [tests] Error 1

Yes, we broke it with https://gerrit.ovirt.org/63638 as discussed on

[VDSM] build-artifacts failing on master

> 
> 
> Is a newer version of nose really needed?

yes.

> If no: please require a version of nose which is available.
> If yes: we can consider shipping nose in CentOS Virt SIG repos since it's
> available for OpenStack repos:
> http://cbs.centos.org/koji/buildinfo?buildID=10186

This would not solve our problem for RHEL, but it would certainly help
developement upsream. How difficult would it be to add it?

> 
> Please let me know.
> 
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : ovirt_4.0_he-system-tests #270

2016-09-15 Thread jenkins 
See 

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

[ACTION REQUIKRED] vdsm check merged for 4.0 failing on Lago repository sync

2016-09-15 Thread Sandro Bonazzola 
http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/146/console

Please either fix lago to be more reliable when syncing repos or configure
vdsm tests to use the right repos.

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

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

[ACTION REQUIRED] VDSM master builf failing on NOSE version check

2016-09-15 Thread Sandro Bonazzola 
*http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/836/console
*


*00:05:37.816* make[1]: Entering directory
`/home/jenkins/workspace/vdsm_master_build-artifacts-el7-x86_64/vdsm/rpmbuild/BUILD/vdsm-4.18.999'*00:05:37.817*
Makefile:980: warning: overriding recipe for target
`check-recursive'*00:05:37.818* Makefile:516: warning: ignoring old
recipe for target `check-recursive'*00:05:38.119* Error: NOSE is too
old, please install NOSE 1.3.7 or later*00:05:38.119* make[1]: ***
[tests] Error 1


Is a newer version of nose really needed?
If no: please require a version of nose which is available.
If yes: we can consider shipping nose in CentOS Virt SIG repos since it's
available for OpenStack repos:
http://cbs.centos.org/koji/buildinfo?buildID=10186

Please let me know.

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

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