Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread David Caro 
On 12/01 19:37, Tal Nisan wrote:
> Well, if the integration team is OK with that then I guess it's up to the
> branch owner indeed and as said it will be very helpful for the backport
> process if we indeed have CI jobs and gerrit hooks on the 3.6.1 branch for
> the following weeks until 3.6.1 is released

Ok, waiting for reply from the integration team, not sure if all of them are
monitoring the infra list though, you might ask on devel too (or cc them)

> 
> On Tue, Dec 1, 2015 at 7:30 PM, David Caro  wrote:
> 
> > On 12/01 19:25, Tal Nisan wrote:
> > > Well, it's not my decision but of the integration team, for me as the
> > > stable branches maintainer it will help a lot to have the gerrit hooks
> > (I'd
> > > say even a must) and CI (not a must but definitely nice to have)
> >
> >
> > I disagree on that, I think that it's the projects owners that should know
> > what do they want to test and when, not the integration team.
> >
> > In any case, can you ask whoever makes the decision to ack?
> >
> > >
> > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> > >
> > > >
> > > > So a couple questions here:
> > > >
> > > >  * Who decides which branches are stable?
> > > >  * Who decides which branches have ci?
> > > >
> > > > In the latter, you can easily add the extra branch to the vdsm project
> > > > yaml:
> > > >
> > > >
> > > >
> > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> > > >
> > > > There on line 55, just define another version:
> > > >
> > > >  - 3.6.1:
> > > >  branch: ovirt-3.6.1
> > > >
> > > > And the jobs will be created automatically once merged
> > > >
> > > >
> > > > (I know, it needs a bit of a cleanup, and we are working on even not
> > > > having to
> > > > change any yaml, but for now it's what we have)
> > > >
> > > > On 12/01 10:52, Tal Nisan wrote:
> > > > > The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> > > > > Aside for that, CI is not running on new patches there
> > > > >
> > > > > [1]
> > > > >
> > > > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
> > ovirt-engine-3.3
> > > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > > > ovirt-engine-3.3.1)
> > > > >- Check merged to previous::IGNORE, Not in stable branch
> > > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
> > > > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
> > > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> > > >
> > > > > ___
> > > > > Infra mailing list
> > > > > Infra@ovirt.org
> > > > > http://lists.ovirt.org/mailman/listinfo/infra
> > > >
> > > >
> > > > --
> > > > David Caro
> > > >
> > > > Red Hat S.L.
> > > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > > >
> > > > Tel.: +420 532 294 605
> > > > Email: dc...@redhat.com
> > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > > Web: www.redhat.com
> > > > RHT Global #: 82-62605
> > > >
> >
> > --
> > David Caro
> >
> > Red Hat S.L.
> > Continuous Integration Engineer - EMEA ENG Virtualization R
> >
> > Tel.: +420 532 294 605
> > Email: dc...@redhat.com
> > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > Web: www.redhat.com
> > RHT Global #: 82-62605
> >

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread David Caro 

So a couple questions here:

 * Who decides which branches are stable?
 * Who decides which branches have ci?

In the latter, you can easily add the extra branch to the vdsm project yaml:

  
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master

There on line 55, just define another version:

 - 3.6.1:
 branch: ovirt-3.6.1

And the jobs will be created automatically once merged


(I know, it needs a bit of a cleanup, and we are working on even not having to
change any yaml, but for now it's what we have)

On 12/01 10:52, Tal Nisan wrote:
> The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> Aside for that, CI is not running on new patches there
> 
> [1]
> 
>- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
>ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4 ovirt-engine-3.3
>engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
>ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 
> ovirt-engine-3.3.1)
>- Check merged to previous::IGNORE, Not in stable branch
>(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
>'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
>'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
>'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])

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


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread David Caro 
On 12/01 19:25, Tal Nisan wrote:
> Well, it's not my decision but of the integration team, for me as the
> stable branches maintainer it will help a lot to have the gerrit hooks (I'd
> say even a must) and CI (not a must but definitely nice to have)


I disagree on that, I think that it's the projects owners that should know
what do they want to test and when, not the integration team.

In any case, can you ask whoever makes the decision to ack?

> 
> On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> 
> >
> > So a couple questions here:
> >
> >  * Who decides which branches are stable?
> >  * Who decides which branches have ci?
> >
> > In the latter, you can easily add the extra branch to the vdsm project
> > yaml:
> >
> >
> > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> >
> > There on line 55, just define another version:
> >
> >  - 3.6.1:
> >  branch: ovirt-3.6.1
> >
> > And the jobs will be created automatically once merged
> >
> >
> > (I know, it needs a bit of a cleanup, and we are working on even not
> > having to
> > change any yaml, but for now it's what we have)
> >
> > On 12/01 10:52, Tal Nisan wrote:
> > > The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> > > Aside for that, CI is not running on new patches there
> > >
> > > [1]
> > >
> > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4 ovirt-engine-3.3
> > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > ovirt-engine-3.3.1)
> > >- Check merged to previous::IGNORE, Not in stable branch
> > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
> > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
> > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> >
> > > ___
> > > Infra mailing list
> > > Infra@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> > --
> > David Caro
> >
> > Red Hat S.L.
> > Continuous Integration Engineer - EMEA ENG Virtualization R
> >
> > Tel.: +420 532 294 605
> > Email: dc...@redhat.com
> > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > Web: www.redhat.com
> > RHT Global #: 82-62605
> >

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread Tal Nisan 
Well, if the integration team is OK with that then I guess it's up to the
branch owner indeed and as said it will be very helpful for the backport
process if we indeed have CI jobs and gerrit hooks on the 3.6.1 branch for
the following weeks until 3.6.1 is released

On Tue, Dec 1, 2015 at 7:30 PM, David Caro  wrote:

> On 12/01 19:25, Tal Nisan wrote:
> > Well, it's not my decision but of the integration team, for me as the
> > stable branches maintainer it will help a lot to have the gerrit hooks
> (I'd
> > say even a must) and CI (not a must but definitely nice to have)
>
>
> I disagree on that, I think that it's the projects owners that should know
> what do they want to test and when, not the integration team.
>
> In any case, can you ask whoever makes the decision to ack?
>
> >
> > On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> >
> > >
> > > So a couple questions here:
> > >
> > >  * Who decides which branches are stable?
> > >  * Who decides which branches have ci?
> > >
> > > In the latter, you can easily add the extra branch to the vdsm project
> > > yaml:
> > >
> > >
> > >
> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> > >
> > > There on line 55, just define another version:
> > >
> > >  - 3.6.1:
> > >  branch: ovirt-3.6.1
> > >
> > > And the jobs will be created automatically once merged
> > >
> > >
> > > (I know, it needs a bit of a cleanup, and we are working on even not
> > > having to
> > > change any yaml, but for now it's what we have)
> > >
> > > On 12/01 10:52, Tal Nisan wrote:
> > > > The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> > > > Aside for that, CI is not running on new patches there
> > > >
> > > > [1]
> > > >
> > > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
> ovirt-engine-3.3
> > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > > ovirt-engine-3.3.1)
> > > >- Check merged to previous::IGNORE, Not in stable branch
> > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
> > > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
> > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> > >
> > > > ___
> > > > Infra mailing list
> > > > Infra@ovirt.org
> > > > http://lists.ovirt.org/mailman/listinfo/infra
> > >
> > >
> > > --
> > > David Caro
> > >
> > > Red Hat S.L.
> > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > >
> > > Tel.: +420 532 294 605
> > > Email: dc...@redhat.com
> > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > Web: www.redhat.com
> > > RHT Global #: 82-62605
> > >
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread Tal Nisan 
Well, it's not my decision but of the integration team, for me as the
stable branches maintainer it will help a lot to have the gerrit hooks (I'd
say even a must) and CI (not a must but definitely nice to have)

On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:

>
> So a couple questions here:
>
>  * Who decides which branches are stable?
>  * Who decides which branches have ci?
>
> In the latter, you can easily add the extra branch to the vdsm project
> yaml:
>
>
> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
>
> There on line 55, just define another version:
>
>  - 3.6.1:
>  branch: ovirt-3.6.1
>
> And the jobs will be created automatically once merged
>
>
> (I know, it needs a bit of a cleanup, and we are working on even not
> having to
> change any yaml, but for now it's what we have)
>
> On 12/01 10:52, Tal Nisan wrote:
> > The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> > Aside for that, CI is not running on new patches there
> >
> > [1]
> >
> >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4 ovirt-engine-3.3
> >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> ovirt-engine-3.3.1)
> >- Check merged to previous::IGNORE, Not in stable branch
> >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
> >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
> >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
>
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
>
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[2015-12-01] Weekly infra team status

2015-12-01 Thread David Caro 

Hi everyone, this week updates:


* Jenkins slaves stabilized
After last week's upgrade, some of the slaves got wrongly configured,
during this week all the slaves have been checked and fixed any issues
found.

* Artifactory migration
We are migrating to an artifactory server on PHX hosting, everything is
ready but if you have any ovirt-engine patches and you haven't rebased
lately, please do, or your patches will start failing the tests on thursday
morning (when the final migration will be made).

* Ticketing system for infra issues
We have almost ready the setup to create infra tickets from emails, that
will allow us to handle better the requests and gather statistics, to avoid
requests being forgotten or unanswered. (Thanks Vishnu!)
Will send a dedicated email once it's ready, for now you can still use the
jira page [1] or infa mailing list

* Ovirt system tests are now running on two dedicated slaves, ovirt-srv08 and
ovirt-srv09, which were manually setup.

* New docs for repoman project [2]
They are just dumped from the code, need some formatting and proper
structure, but it's a big advance


[1] https://ovirt-jira.atlassian.net
[2] http://repoman.readthedocs.org/en/latest


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread Eyal Edri 
On Tue, Dec 1, 2015 at 7:42 PM, David Caro  wrote:

> On 12/01 19:37, Tal Nisan wrote:
> > Well, if the integration team is OK with that then I guess it's up to the
> > branch owner indeed and as said it will be very helpful for the backport
> > process if we indeed have CI jobs and gerrit hooks on the 3.6.1 branch
> for
> > the following weeks until 3.6.1 is released
>
> Ok, waiting for reply from the integration team, not sure if all of them
> are
> monitoring the infra list though, you might ask on devel too (or cc them)
>

>From CI pov, +1 on enabling all gerrit hooks on any stable branch we add,
as far as jenkins jobs we have to be very carfeul with it, since it will
mean duplicating many jobs we have right now and not sure jenkins can
handle it.
either we decide on a limited must have sanity set of tests to run on
version branches (like 3.6.1) or we can suffice with the 3.6 jobs,
since they are a superset of 3.6.1 and if something fails there it means it
will fail 3.6.1, the otherway is very unlikely (i.e fail on 3.6.1 and not
3.6) so
this is why i think the extra resources and time per job that will be added
to jenkins won't worth adding all the jobs.

e.


>
> >
> > On Tue, Dec 1, 2015 at 7:30 PM, David Caro  wrote:
> >
> > > On 12/01 19:25, Tal Nisan wrote:
> > > > Well, it's not my decision but of the integration team, for me as the
> > > > stable branches maintainer it will help a lot to have the gerrit
> hooks
> > > (I'd
> > > > say even a must) and CI (not a must but definitely nice to have)
> > >
> > >
> > > I disagree on that, I think that it's the projects owners that should
> know
> > > what do they want to test and when, not the integration team.
> > >
> > > In any case, can you ask whoever makes the decision to ack?
> > >
> > > >
> > > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> > > >
> > > > >
> > > > > So a couple questions here:
> > > > >
> > > > >  * Who decides which branches are stable?
> > > > >  * Who decides which branches have ci?
> > > > >
> > > > > In the latter, you can easily add the extra branch to the vdsm
> project
> > > > > yaml:
> > > > >
> > > > >
> > > > >
> > >
> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> > > > >
> > > > > There on line 55, just define another version:
> > > > >
> > > > >  - 3.6.1:
> > > > >  branch: ovirt-3.6.1
> > > > >
> > > > > And the jobs will be created automatically once merged
> > > > >
> > > > >
> > > > > (I know, it needs a bit of a cleanup, and we are working on even
> not
> > > > > having to
> > > > > change any yaml, but for now it's what we have)
> > > > >
> > > > > On 12/01 10:52, Tal Nisan wrote:
> > > > > > The 3.6.1 branch is not treated by the hooks as a stable branch
> [1]
> > > > > > Aside for that, CI is not running on new patches there
> > > > > >
> > > > > > [1]
> > > > > >
> > > > > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > > > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
> > > ovirt-engine-3.3
> > > > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > > > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > > > > ovirt-engine-3.3.1)
> > > > > >- Check merged to previous::IGNORE, Not in stable branch
> > > > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0',
> 'ovirt-engine-3.5',
> > > > > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > > > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4',
> 'ovirt-engine-3.3.3',
> > > > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> > > > >
> > > > > > ___
> > > > > > Infra mailing list
> > > > > > Infra@ovirt.org
> > > > > > http://lists.ovirt.org/mailman/listinfo/infra
> > > > >
> > > > >
> > > > > --
> > > > > David Caro
> > > > >
> > > > > Red Hat S.L.
> > > > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > > > >
> > > > > Tel.: +420 532 294 605
> > > > > Email: dc...@redhat.com
> > > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > > > Web: www.redhat.com
> > > > > RHT Global #: 82-62605
> > > > >
> > >
> > > --
> > > David Caro
> > >
> > > Red Hat S.L.
> > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > >
> > > Tel.: +420 532 294 605
> > > Email: dc...@redhat.com
> > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > Web: www.redhat.com
> > > RHT Global #: 82-62605
> > >
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Eyal Edri
Supervisor, RHEV CI
EMEA ENG Virtualization R
Red Hat Israel

phone:

Logwatch for linode01.ovirt.org (Linux)

2015-12-01 Thread logwatch 

 ### Logwatch 7.3.6 (05/19/07)  
Processing Initiated: Tue Dec  1 03:36:09 2015
Date Range Processed: yesterday
  ( 2015-Nov-30 )
  Period is day.
  Detail Level of Output: 0
  Type of Output: unformatted
   Logfiles for Host: linode01.ovirt.org
  ## 
 
 - Dovecot Begin  

 Dovecot disconnects:
Logged out: 1440 Time(s)
no auth attempts: 4 Time(s)
 
 **Unmatched Entries**
dovecot: ssl-params: Error: epoll_ctl(del, 7) failed: No such file or 
directory: 1 Time(s)
 
 -- Dovecot End - 

 
 - httpd Begin  

 
 Requests with error response codes
404 Not Found
   /: 3 Time(s)
   /%09Drupal%0986000%090: 1 Time(s)
   //admin/categories.php/login.php?cPath= ... product_preview: 82 
Time(s)
   //images/stories/wawalo.gif: 1 Time(s)
   /admin: 2 Time(s)
   /admin.php: 7 Time(s)
   /admin/: 8 Time(s)
   /admin/administrators.php/login.php: 2 Time(s)
   /admin/banner_manager.php/login.php: 2 Time(s)
   /admin/board: 2 Time(s)
   /admin/categories.php/login.php: 2 Time(s)
   /admin/file_manager.php/login.php: 2 Time(s)
   /admin/login.php: 8 Time(s)
   /administrator/index.php: 8 Time(s)
   /apple-touch-icon-precomposed.png: 2 Time(s)
   /apple-touch-icon.png: 2 Time(s)
   /bitrix/admin/index.php?lang=en: 8 Time(s)
   /blog/wp-admin/: 14 Time(s)
   /board: 4 Time(s)
   /browserconfig.xml: 1 Time(s)
   /category/news/feed: 1 Time(s)
   /category/news/feed/: 17 Time(s)
   /ddta/juhua.asp:: 1 Time(s)
   /favicon.ico: 679 Time(s)
   /index.php?option=com_jce=plugin ... 86d0dd595c8e20b: 2 Time(s)
   /index.php?option=com_users=registration: 12 Time(s)
   /info.php: 1 Time(s)
   /listinfo/announce: 1 Time(s)
   /listinfo/arch: 1 Time(s)
   /listinfo/automation: 1 Time(s)
   /listinfo/board: 3 Time(s)
   /listinfo/board:: 1 Time(s)
   /listinfo/bugs: 1 Time(s)
   /listinfo/devel: 1 Time(s)
   /listinfo/engine-commits: 2 Time(s)
   /listinfo/engine-devel: 1 Time(s)
   /listinfo/engine-patches: 1 Time(s)
   /listinfo/events: 1 Time(s)
   /listinfo/fosdem16-virt-iaas-devroom-internal: 1 Time(s)
   /listinfo/infra: 1 Time(s)
   /listinfo/infra-private: 1 Time(s)
   /listinfo/kimchi-devel: 1 Time(s)
   /listinfo/kimchi-users: 1 Time(s)
   /listinfo/lago-devel: 1 Time(s)
   /listinfo/linkedin: 1 Time(s)
   /listinfo/mailman: 2 Time(s)
   /listinfo/marketing: 1 Time(s)
   /listinfo/movirt: 1 Time(s)
   /listinfo/node-commits: 1 Time(s)
   /listinfo/node-devel: 1 Time(s)
   /listinfo/project-planning: 1 Time(s)
   /listinfo/security: 1 Time(s)
   /listinfo/security-private: 1 Time(s)
   /listinfo/users: 4 Time(s)
   /listinfo/users-pt: 1 Time(s)
   /listinfo/wiki: 1 Time(s)
   /listinfo/wordpress-admins: 1 Time(s)
   /listinfo/workshop-mar2012: 1 Time(s)
   /listinfo/workshop-nov2011: 1 Time(s)
   /old/wp-admin/: 12 Time(s)
   /pipermail/engine-patches/2011-December/001453.html: 1 Time(s)
   /pipermail/engine-patches/2012-April/013386.html: 1 Time(s)
   /pipermail/engine-patches/2012-April/014348.html: 1 Time(s)
   /pipermail/engine-patches/2012-April/014383.html: 1 Time(s)
   /pipermail/engine-patches/2012-April/014624.html: 1 Time(s)
   /pipermail/engine-patches/2012-April/015936.html: 1 Time(s)
   /pipermail/engine-patches/2012-August/030538.html: 1 Time(s)
   /pipermail/engine-patches/2012-August/030575.html: 1 Time(s)
   /pipermail/engine-patches/2012-August/030821.html: 1 Time(s)
   /pipermail/engine-patches/2012-August/033035.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/043275.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/043627.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/043738.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/044886.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/044958.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/045227.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/045233.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/045626.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/045638.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/045780.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/046073.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/046398.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/046516.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/047465.html: 1 Time(s)

Re: [RFC] Proposal for dropping FC22 jenkins tests on master branch

2015-12-01 Thread Sandro Bonazzola 
On Mon, Nov 30, 2015 at 2:11 PM, Dan Kenigsberg  wrote:

> On Mon, Nov 30, 2015 at 01:11:25PM +0100, Sandro Bonazzola wrote:
> > On Thu, Nov 12, 2015 at 9:34 AM, Sandro Bonazzola 
> > wrote:
> >
> > > Hi,
> > > can we drop FC22 testing in jenkins now that FC23 jobs are up and
> running?
> > > it will reduce jenkins load. If needed we can keep FC22 builds, just
> > > dropping the check jobs.
> > > Comments?
> > >
> > >
> > This morning queue is up to 233 jobs, can we drop fc22 build on master?
>
> +1.
>
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/ and
>
> http://jenkins.ovirt.org/view/All/job/vdsm_master_install-rpm-sanity-fc23_created/
> seem good.
>
> Dan.
>

Note that the proposal is not limited to the above 2 jobs, it's a
master-wide change.
I need another +1 for dropping fc22 jobs on master.

-- 
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

3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread Tal Nisan 
The 3.6.1 branch is not treated by the hooks as a stable branch [1]
Aside for that, CI is not running on new patches there

[1]

   - Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
   ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4 ovirt-engine-3.3
   engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
   ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 ovirt-engine-3.3.1)
   - Check merged to previous::IGNORE, Not in stable branch
   (['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
   'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
   'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
   'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Change in ovirt-engine[ovirt-engine-3.6]: packaging: setup: pki: Do not fail if pkcs12 unreadable

2015-12-01 Thread David Caro 
On 12/01 10:27, Yedidyah Bar David wrote:
> On Tue, Dec 1, 2015 at 2:14 AM, Jenkins CI  wrote:
> > Jenkins CI has posted comments on this change.
> >
> > Change subject: packaging: setup: pki: Do not fail if pkcs12 unreadable
> > ..
> >
> >
> > Patch Set 1:
> >
> > Build Failed
> >
> > http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/537/
> >  : FAILURE
> 
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-6-x86_64/repodata/repomd.xml:
> [Errno 14] PYCURL ERROR 7 - "couldn't connect to host"
> 
> Shouldn't patternfly be cached somehow by our (jenkins) infra?

That specific job is not using the proxy, yet.

> 
> Perhaps we should pause jobs until copr is up?

I don't think that's a good idea, that means that you have to declare somewhere
a set of resources to monitor (in this case, patternfly repo on copr) and that
can very easily get out of hands (epel, fedora, centos, ovirt, maven,
artifactory...) and make the queue get frozen without a real reason to.
It might also depend on the slave it runs on (as it might be a local issue that
those urls are not reachable), and it's rather complicated to integrate with
jenkins (adding just a while !is_up $server in the script might do some of it,
but that will hang the jobs when they already have an executor, and block not
only that specific job, but any other from running).

I think that the best option here is to move it to use the local proxy server

> 
> >
> > http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/548/
> >  : FAILURE
> >
> > http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-el6-x86_64/275/ 
> > : SUCCESS
> >
> > http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-fc22-x86_64/272/ 
> > : SUCCESS
> >
> > http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-fc23-x86_64/101/ 
> > : SUCCESS
> >
> > http://jenkins.ovirt.org/job/ovirt-engine_3.6_unit-tests_merged/755/ : 
> > SUCCESS
> >
> > http://jenkins.ovirt.org/job/ovirt-engine_3.6_dao-unit-tests_merged/639/ : 
> > SUCCESS
> >
> > http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-el7-x86_64/278/ 
> > : SUCCESS
> >
> > --
> > To view, visit https://gerrit.ovirt.org/49408
> > To unsubscribe, visit https://gerrit.ovirt.org/settings
> >
> > Gerrit-MessageType: comment
> > Gerrit-Change-Id: Ibe88e38b073433a357ee7ac09f6ead159e22baa4
> > Gerrit-PatchSet: 1
> > Gerrit-Project: ovirt-engine
> > Gerrit-Branch: ovirt-engine-3.6
> > Gerrit-Owner: Yedidyah Bar David 
> > Gerrit-Reviewer: Jenkins CI
> > Gerrit-Reviewer: Piotr Kliczewski 
> > Gerrit-Reviewer: Sandro Bonazzola 
> > Gerrit-Reviewer: Tal Nisan 
> > Gerrit-Reviewer: Yedidyah Bar David 
> > Gerrit-Reviewer: gerrit-hooks 
> > Gerrit-HasComments: No
> -- 
> Didi
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Missing package on one of the Fedora 23 slaves?

2015-12-01 Thread Francesco Romani 
- Original Message -
> From: "Nir Soffer" 
> To: "David Caro" 
> Cc: "Tal Nisan" , "infra" 
> Sent: Monday, November 30, 2015 9:55:52 PM
> Subject: Re: Missing package on one of the Fedora 23 slaves?
> 
> Adding Francesco
> 
> On Mon, Nov 30, 2015 at 8:12 PM, David Caro  wrote:
> > On 11/30 20:09, Nir Soffer wrote:
> >> Another instance:
> >>
> >> 17:37:47 Error: nothing provides ovirt-vmconsole >= 1.0.0-0 needed by
> >> vdsm-4.17.11-9.gitdcd50d8.fc23.noarch.
> >> 17:37:47 nothing provides ovirt-vmconsole >= 1.0.0-0 needed by
> >> vdsm-4.17.11-9.gitdcd50d8.fc23.noarch.
> >
> > Has ovirt-vmconsole dependency changed lately? From which repo should it be
> > comming from?
> >
> > The repos available during the build are declared in the
> > automation/check-patch.repos file in the vdsm git repo, maybe something is
> > missing there for fc23?

I think we just need https://gerrit.ovirt.org/#/c/49503/

Bests,

-- 
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Change in ovirt-engine[ovirt-engine-3.6]: packaging: setup: pki: Do not fail if pkcs12 unreadable

2015-12-01 Thread Yedidyah Bar David 
On Tue, Dec 1, 2015 at 2:14 AM, Jenkins CI  wrote:
> Jenkins CI has posted comments on this change.
>
> Change subject: packaging: setup: pki: Do not fail if pkcs12 unreadable
> ..
>
>
> Patch Set 1:
>
> Build Failed
>
> http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/537/
>  : FAILURE

http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-6-x86_64/repodata/repomd.xml:
[Errno 14] PYCURL ERROR 7 - "couldn't connect to host"

Shouldn't patternfly be cached somehow by our (jenkins) infra?

Perhaps we should pause jobs until copr is up?

>
> http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/548/
>  : FAILURE
>
> http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-el6-x86_64/275/ : 
> SUCCESS
>
> http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-fc22-x86_64/272/ : 
> SUCCESS
>
> http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-fc23-x86_64/101/ : 
> SUCCESS
>
> http://jenkins.ovirt.org/job/ovirt-engine_3.6_unit-tests_merged/755/ : SUCCESS
>
> http://jenkins.ovirt.org/job/ovirt-engine_3.6_dao-unit-tests_merged/639/ : 
> SUCCESS
>
> http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-el7-x86_64/278/ : 
> SUCCESS
>
> --
> To view, visit https://gerrit.ovirt.org/49408
> To unsubscribe, visit https://gerrit.ovirt.org/settings
>
> Gerrit-MessageType: comment
> Gerrit-Change-Id: Ibe88e38b073433a357ee7ac09f6ead159e22baa4
> Gerrit-PatchSet: 1
> Gerrit-Project: ovirt-engine
> Gerrit-Branch: ovirt-engine-3.6
> Gerrit-Owner: Yedidyah Bar David 
> Gerrit-Reviewer: Jenkins CI
> Gerrit-Reviewer: Piotr Kliczewski 
> Gerrit-Reviewer: Sandro Bonazzola 
> Gerrit-Reviewer: Tal Nisan 
> Gerrit-Reviewer: Yedidyah Bar David 
> Gerrit-Reviewer: gerrit-hooks 
> Gerrit-HasComments: No
-- 
Didi
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 1059 - Failure!

2015-12-01 Thread jenkins 
Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1059/
Build Number: 1059
Build Status:  Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/49160

-
Changes Since Last Success:
-
Changes for Build #1059
[Juan Hernandez] restapi: Add model description as resource




-
Failed Tests:
-
No tests ran. 

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

Re: Missing package on one of the Fedora 23 slaves?

2015-12-01 Thread Dan Kenigsberg 
On Tue, Dec 01, 2015 at 04:19:19AM -0500, Francesco Romani wrote:
> - Original Message -
> > From: "Nir Soffer" 
> > To: "David Caro" 
> > Cc: "Tal Nisan" , "infra" 
> > Sent: Monday, November 30, 2015 9:55:52 PM
> > Subject: Re: Missing package on one of the Fedora 23 slaves?
> > 
> > Adding Francesco
> > 
> > On Mon, Nov 30, 2015 at 8:12 PM, David Caro  wrote:
> > > On 11/30 20:09, Nir Soffer wrote:
> > >> Another instance:
> > >>
> > >> 17:37:47 Error: nothing provides ovirt-vmconsole >= 1.0.0-0 needed by
> > >> vdsm-4.17.11-9.gitdcd50d8.fc23.noarch.
> > >> 17:37:47 nothing provides ovirt-vmconsole >= 1.0.0-0 needed by
> > >> vdsm-4.17.11-9.gitdcd50d8.fc23.noarch.
> > >
> > > Has ovirt-vmconsole dependency changed lately? From which repo should it 
> > > be
> > > comming from?
> > >
> > > The repos available during the build are declared in the
> > > automation/check-patch.repos file in the vdsm git repo, maybe something is
> > > missing there for fc23?
> 
> I think we just need https://gerrit.ovirt.org/#/c/49503/

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

[ANN] oVirt 3.5 won't receive further updates

2015-12-01 Thread Sandro Bonazzola 
Hi,
due to the release of recent 3.6.0 major release of the oVirt project,
and upcoming release of its first maintenance release 3.6.1,
the last 3.5 release is 3.5.6 we released today.

We recommend anyone hitting issued existing in 3.5
to upgrade to 3.6 to get the fixes since 3.5 won't receive further updates.

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