Logwatch for linode01.ovirt.org (Linux)

### Logwatch 7.3.6 (05/19/07) Processing Initiated: Wed Jan 13 03:19:19 2016 Date Range Processed: yesterday ( 2016-Jan-12 ) Period is day. Detail Level of Output: 0

Re: removing 3.6.2 jobs

My question was why do we need the build artifacts for e.g? I'm OK with the check-patch jobs that verify compilation for e.g, but are we using the 3.6.2 build artifacts jobs? e. On Wed, Jan 13, 2016 at 9:59 AM, Sandro Bonazzola wrote: > > > On Wed, Jan 13, 2016 at 8:22 AM,

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 1742 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1742/ Build Number: 1742 Build Status: Still Failing Triggered By: Triggered by Gerrit:

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 1651 - Still Failing!

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/1651/ Build Number: 1651 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51727

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 1652 - Still Failing!

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/1652/ Build Number: 1652 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51761

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 770 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/770/ Build Number: 770 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51660

Re: Fwd: Request to mirror the open source project oVirt.org

Great :) I'll track it for a few days to see its all good and update our wiki pages/mirror list afterwards. thanks, Nadav. On Tue, Jan 12, 2016 at 11:04 AM, Lior Kaplan wrote: > Bingo (: > > http://mirror.isoc.org.il/pub/ovirt/ > > > I'll set a daily update. > > Kaplan >

Random jenkins failures

I have just submitted a set of 4 patches where 1 patch unit tests failed with the pasted text below. Those patches are absolutely unrelated to those failures. Please check into those issues - Thanks http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/2168/console 12:15:21

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 1654 - Still Failing!

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/1654/ Build Number: 1654 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51714

Re: Random jenkins failures

Looks like loop device issues. Nir - didn't you say you have a patch to fix this? In any case i think rebooting the slave fix this. E. On Wed, Jan 13, 2016 at 3:08 PM, Vinzenz Feenstra wrote: > > On Jan 13, 2016, at 1:20 PM, Vinzenz Feenstra wrote: >

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 1743 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1743/ Build Number: 1743 Build Status: Still Failing Triggered By: Triggered by Gerrit:

[JIRA] (OVIRT-375) add gamification to oVirt infra

Title: Message Title eyal edri

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 771 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/771/ Build Number: 771 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51723

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 1745 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1745/ Build Number: 1745 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51628

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 1744 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1744/ Build Number: 1744 Build Status: Still Failing Triggered By: Triggered by Gerrit:

Re: Random jenkins failures

> On Jan 13, 2016, at 1:20 PM, Vinzenz Feenstra wrote: > > I have just submitted a set of 4 patches where 1 patch unit tests failed with > the pasted text below. Those patches are absolutely unrelated to those > failures. > > Please check into those issues - Thanks It

[JIRA] (OVIRT-375) add gamification to oVirt infra

Title: Message Title bkorren commented on

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 778 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/778/ Build Number: 778 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51419

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 779 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/779/ Build Number: 779 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51715

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.5_el6_merged - Build # 790 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/790/ Build Number: 790 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51417

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

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/1660/ Build Number: 1660 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51720

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 780 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/780/ Build Number: 780 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51639

Re: Random jenkins failures

On Wed, Jan 13, 2016 at 7:57 PM, David Caro wrote: > On 01/13 15:37, Eyal Edri wrote: >> Looks like loop device issues. >> Nir - didn't you say you have a patch to fix this? >> >> In any case i think rebooting the slave fix this. > > I just logged in to the slave and I see some

"ovirt-engine_3.6_upgrade-from-3.5_el6_merged" job failure

all errors in the console log aren't related to Alexander's patch as implied by the original jenkins e-mail (forwarded below): ... ERROR with rpm_check_debug vs depsolve: ovirt-engine-sdk-python >= 3.5.2.1 is needed by (installed) ovirt-iso-uploader-3.5.2-1.el6.noarch ovirt-engine-sdk-python

Re: Random jenkins failures

On Wed, Jan 13, 2016 at 3:37 PM, Eyal Edri wrote: > Looks like loop device issues. > Nir - didn't you say you have a patch to fix this? The patch was merge today: https://gerrit.ovirt.org/51614/ It fixes incorrect umount in two tests, that may cause stale loop devices

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.5_el6_merged - Build # 796 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/796/ Build Number: 796 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51801

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 781 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/781/ Build Number: 781 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51801

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

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/1667/ Build Number: 1667 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51257

Re: My ssh public key

On Wed, Jan 13, 2016 at 5:00 PM, Lev Veyde wrote: > Hi, > > This is my key. > > Please grant me access to resource.ovirt.org server. > +1 > > Thanks in advance, > Lev Veyde. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration.

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 773 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/773/ Build Number: 773 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51747

DB upgrade jobs are not using engine-setup

Hi Currently DB upgrade jobs are using schema.sh script and not engine-setup This may cause CI upgrade tests to be successful while they are actually failed when running from engine-setup Since we are using engine-setup to upgrade the database, CI tests must use the same exact method in order

Re: DB upgrade jobs are not using engine-setup

I wonder if the upgrade jobs could somehow be converted into standard-CI. Are they running on every merge atm? On 13 January 2016 at 16:52, Eyal Edri wrote: > Also replacing support-infra with infra-support which is the right email to > open a ticket. > > e. > > On Wed, Jan 13,

My ssh public key

Hi, This is my key. Please grant me access to resource.ovirt.org server. Thanks in advance, Lev Veyde. lveyde.pub Description: Binary data ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Using oVirt VM pools in oVirt infra

VM Pools are a nice feature of oVirt. A VM pool lets you quickly create a pool of stateles VMs all based on the same template. A VM pool also seems to currently be the only way to create template-based thin QCOW2 VMs in oVirt. (Cloning from template creates a thick copy, this is why its relatively

Re: DB upgrade jobs are not using engine-setup

Hi, The scripts used to run the job can be found here [1]. Specifically: ovirt-engine_upgrade-db.cleanup.sh ovirt-engine_upgrade-db.sh If you can submit a patch to replace the logic to use engine-setup instead, the jobs will update automatically via yaml to use the new logic. infra team can

Re: DB upgrade jobs are not using engine-setup

Also replacing support-infra with infra-support which is the right email to open a ticket. e. On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri wrote: > Hi, > > The scripts used to run the job can be found here [1]. > Specifically: > > ovirt-engine_upgrade-db.cleanup.sh >

DB upgrade jobs are not using engine-setup

Hi Currently DB upgrade jobs are using schema.sh script and not engine-setup This may cause CI upgrade tests to be successful while they are actually failed when running from engine-setup Since we are using engine-setup to upgrade the database, CI tests must use the same exact method in

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 1655 - Still Failing!

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/1655/ Build Number: 1655 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51628

Re: My ssh public key

>> >> Please grant me access to resource.ovirt.org server. > Dear integration team, Please send patches like this: https://gerrit.ovirt.org/#/c/51673/1 instead of emails (But check it out and base on it as it creates the file you need to add to). This will streamline the process of you getting

Re: My ssh public key

On Wed, Jan 13, 2016 at 5:42 PM, Barak Korren wrote: > >> > >> Please grant me access to resource.ovirt.org server. > > > Dear integration team, > Please send patches like this: https://gerrit.ovirt.org/#/c/51673/1 I have no rights to see that patch. > > instead of

Re: My ssh public key

hmm... right this is the 'secret' repo... never mind then, keep emailing... unless david says otherwise... On 13 January 2016 at 18:49, Sandro Bonazzola wrote: > > > On Wed, Jan 13, 2016 at 5:47 PM, Sandro Bonazzola > wrote: >> >> >> >> On Wed, Jan

Re: Using oVirt VM pools in oVirt infra

On 01/13 18:02, Anton Marchukov wrote: > Hello All. > > > What this comes down to is that if you run 'shutdown' in a VM from a > > > pool, you will automatically get back a clean VM a few minutes later. > > > > > > > Is there an easy way to do so from jenknis job without failing the job > > with

Re: My ssh public key

On Wed, Jan 13, 2016 at 5:47 PM, Sandro Bonazzola wrote: > > > On Wed, Jan 13, 2016 at 5:42 PM, Barak Korren wrote: > >> >> >> >> Please grant me access to resource.ovirt.org server. >> > >> Dear integration team, >> Please send patches like this:

Re: My ssh public key

On 01/13 18:53, Barak Korren wrote: > hmm... right this is the 'secret' repo... never mind then, keep > emailing... unless david says otherwise... > I think sandro is a good candidate to also send patches to that repo :) > > On 13 January 2016 at 18:49, Sandro Bonazzola

Re: Using oVirt VM pools in oVirt infra

Hello All. > What this comes down to is that if you run 'shutdown' in a VM from a > > pool, you will automatically get back a clean VM a few minutes later. > > > > Is there an easy way to do so from jenknis job without failing the job > with slave connection error? Most projects I know that use

Re: Using oVirt VM pools in oVirt infra

On 01/13 18:23, Barak Korren wrote: > VM Pools are a nice feature of oVirt. > A VM pool lets you quickly create a pool of stateles VMs all based on > the same template. > A VM pool also seems to currently be the only way to create > template-based thin QCOW2 VMs in oVirt. (Cloning from template

Re: Random jenkins failures

On 01/13 15:37, Eyal Edri wrote: > Looks like loop device issues. > Nir - didn't you say you have a patch to fix this? > > In any case i think rebooting the slave fix this. I just logged in to the slave and I see some strange loop devices that don't look right: [dcaro@fc21-vm09 ~]$ losetup