[oVirt Jenkins] system-tests_hc-suite-4.1 - Build # 1 - Failure!

Project: http://jenkins.ovirt.org/job/system-tests_hc-suite-4.1/ Build: http://jenkins.ovirt.org/job/system-tests_hc-suite-4.1/1/ Build Number: 1 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] system-tests_hc-suite-master - Build # 1 - Failure!

Project: http://jenkins.ovirt.org/job/system-tests_hc-suite-master/ Build: http://jenkins.ovirt.org/job/system-tests_hc-suite-master/1/ Build Number: 1 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] system-tests_he-suite-master - Build # 1 - Failure!

Project: http://jenkins.ovirt.org/job/system-tests_he-suite-master/ Build: http://jenkins.ovirt.org/job/system-tests_he-suite-master/1/ Build Number: 1 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] ovirt-release_master_build-artifacts-fc25-x86_64 - Build # 178 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fc25-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fc25-x86_64/178/ Build Number: 178 Build Status: Fixed Triggered By: Started by timer - Changes

oVirt infra daily report - unstable production jobs - 393

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/393//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

[oVirt Jenkins] system-tests_he-basic-suite-4.1 - Build # 3 - Fixed!

Project: http://jenkins.ovirt.org/job/system-tests_he-basic-suite-4.1/ Build: http://jenkins.ovirt.org/job/system-tests_he-basic-suite-4.1/3/ Build Number: 3 Build Status: Fixed Triggered By: Started by user Gil Shinar - Changes Since Last Success:

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7678 - SUCCESS!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7678/, Build Number: 7678, Build Status: SUCCESS___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt_master_he-system-tests_archived_for_deletion - Build # 34 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt_master_he-system-tests_archived_for_deletion/ Build: http://jenkins.ovirt.org/job/ovirt_master_he-system-tests_archived_for_deletion/34/ Build Number: 34 Build Status: Fixed Triggered By: Started by user Gil Shinar

Re: [CQ]: 79700,5 (vdsm) failed "ovirt-master" system tests

Note: This is a false positive. We got this in the log: 14:40:46 [upgrade-from-prevrelease-suit] + sudo yum -y install python34-PyYAML PyYAML 14:40:46 [upgrade-from-prevrelease-suit] Loaded plugins: fastestmirror 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit]

[oVirt Jenkins] ovirt_4.1_he-system-tests_archived_for_deletion - Build # 195 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests_archived_for_deletion/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests_archived_for_deletion/195/ Build Number: 195 Build Status: Failure Triggered By: Started by user Gil Shinar

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7677 - FAILURE!

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7677/, Build Number: 7677, Build Status: FAILURE___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: [CQ]: 79771, 1 (ovirt-log-collector) failed "ovirt-4.1" system tests

On Tue, Jul 25, 2017 at 10:23 AM, Barak Korren wrote: > It was actually a failure of the build job, not the CQ test job (It makes > the test job fail as well because it needs the build, but the job output is > clear about that). > > I re-triggered both this morning and

[CQ]: 79700,5 (vdsm) failed "ovirt-master" system tests

Change 79700,5 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the

[oVirt Jenkins] system-tests_he-basic-suite-4.1 - Build # 2 - Still Failing!

Project: http://jenkins.ovirt.org/job/system-tests_he-basic-suite-4.1/ Build: http://jenkins.ovirt.org/job/system-tests_he-basic-suite-4.1/2/ Build Number: 2 Build Status: Still Failing Triggered By: Started by user Gil Shinar - Changes Since Last Success:

Re: [CQ]: 79771, 1 (ovirt-log-collector) failed "ovirt-4.1" system tests

It was actually a failure of the build job, not the CQ test job (It makes the test job fail as well because it needs the build, but the job output is clear about that). I re-triggered both this morning and everything already passed. On 25 July 2017 at 15:38, Eyal Edri wrote:

review on new docs on reposync flow on OST

All, Gal has prepared a very nice documentation on how OST reposync works, which should help in debugging future issues in oVirt CI. Please review it and add your thoughts/remarks, We'll wait until EOW and merge if no objections will be made. https://gerrit.ovirt.org/#/c/79108/7 -- Eyal

[oVirt Jenkins] system-tests_he-basic-suite-4.1 - Build # 1 - Failure!

Project: http://jenkins.ovirt.org/job/system-tests_he-basic-suite-4.1/ Build: http://jenkins.ovirt.org/job/system-tests_he-basic-suite-4.1/1/ Build Number: 1 Build Status: Failure Triggered By: Started by user Gil Shinar - Changes Since Last Success:

Re: [oVirt Jenkins] system-tests_he-suite-4.1 - Build # 1 - Failure!

please ignore this error, we're fixing something with the new naming scheme of the jobs. On Tue, Jul 25, 2017 at 3:48 PM, wrote: > Project: http://jenkins.ovirt.org/job/system-tests_he-suite-4.1/ > Build: http://jenkins.ovirt.org/job/system-tests_he-suite-4.1/1/ >

[oVirt Jenkins] system-tests_he-suite-4.1 - Build # 1 - Failure!

Project: http://jenkins.ovirt.org/job/system-tests_he-suite-4.1/ Build: http://jenkins.ovirt.org/job/system-tests_he-suite-4.1/1/ Build Number: 1 Build Status: Failure Triggered By: Started by user Eyal Edri - Changes Since Last Success:

Re: [CQ]: 79771, 1 (ovirt-log-collector) failed "ovirt-4.1" system tests

We had an infra issue in the morning, which failed due to an issue on the Jenkins master which was fixed. Currently, the CQ doesn't have capabilities to differ between a real issue to an infra issue, hopefully, its something we can address in future versions. On Tue, Jul 25, 2017 at 3:23 PM,

Re: [CQ]: 79771, 1 (ovirt-log-collector) failed "ovirt-4.1" system tests

On Tue, Jul 25, 2017 at 8:23 AM, Sandro Bonazzola wrote: > > > On Tue, Jul 25, 2017 at 11:09 AM, oVirt Jenkins wrote: > >> Change 79771,1 (ovirt-log-collector) is probably the reason behind recent >> system test failures in the "ovirt-4.1" change queue

Re: [CQ]: 79771, 1 (ovirt-log-collector) failed "ovirt-4.1" system tests

On Tue, Jul 25, 2017 at 11:09 AM, oVirt Jenkins wrote: > Change 79771,1 (ovirt-log-collector) is probably the reason behind recent > system test failures in the "ovirt-4.1" change queue and needs to be fixed. > > This change had been removed from the testing queue. Artifacts

Jenkins build is back to normal : deploy-to_ovirt-master_tested #306

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

Re: [vdsm][tag][ovirt-4.1] Vdsm tagged: v4.19.24

Adding Lev so he'll be aware of vdsm rebuild needs for 4.1.4 GA which was planned for today. On Tue, Jul 25, 2017 at 12:46 PM, Anton Marchukov wrote: > Hello Francesco. > > Ok. Let me know how it goes. > > Anton. > > On Tue, Jul 25, 2017 at 10:45 AM, Francesco Romani

Jenkins build is back to normal : ovirt_4.1_publish-rpms_nightly #258

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

Build failed in Jenkins: deploy-to_ovirt-master_tested #305

See -- Started by upstream project "ovirt-master_change-queue-tester" build number 1494 originally caused by: Started by upstream project "ovirt-master_change-queue" build

Build failed in Jenkins: deploy-to_ovirt-master_tested #304

See -- Started by upstream project "ovirt-master_change-queue-tester" build number 1493 originally caused by: Started by upstream project "ovirt-master_change-queue" build

Re: [vdsm][tag][ovirt-4.1] Vdsm tagged: v4.19.24

Hello Francesco. Ok. Let me know how it goes. Anton. On Tue, Jul 25, 2017 at 10:45 AM, Francesco Romani wrote: > Unfortunately tag 4.19.24 may be broken (albeit differently broken) as > well. > > We got word the revert may break storage flows, most notably LSM. > > We are

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3799 - FAILURE!

Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3799/ Build Name: 3799 ovirt-engine-api-model (4.1) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79791 - title: Clarify the meaning of 'current' for consoles - project: ovirt-engine-api-model - branch: model_4.1 -

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3798 - FAILURE!

Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3798/ Build Name: 3798 ovirt-engine-api-model (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79371 - title: Clarify the meaning of 'current' for consoles - project: ovirt-engine-api-model - branch: master -

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3796 - FAILURE!

Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3796/ Build Name: 3796 ovirt-engine-api-model (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79501 - title: Add more detailed description to SshPublicKeys request - project: ovirt-engine-api-model - branch:

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3797 - FAILURE!

Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3797/ Build Name: 3797 ovirt-engine-api-model (4.1) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79788 - title: Add more detailed description to SshPublicKeys request - project: ovirt-engine-api-model - branch:

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3794 - FAILURE!

Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3794/ Build Name: 3794 ovirt-engine-api-model (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79545 - title: Clarify that the CloudInit type is deprecated - project: ovirt-engine-api-model - branch: master -

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3795 - FAILURE!

Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3795/ Build Name: 3795 ovirt-engine-api-model (4.1) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79787 - title: Clarify that the CloudInit type is deprecated - project: ovirt-engine-api-model - branch: model_4.1 -

'change-queue' is now in full production for the 'master' flow

Yesterday we've applied a patch with JJB that made the 'master' change queue push updates into 'tested' instead of the 'experimental' flow. This essentially means that the change queue is now the main production flow for 'master'. A quick refresher on how to find and handle issues with CQ jobs:

Re: [vdsm][tag][ovirt-4.1] Vdsm tagged: v4.19.24

Unfortunately tag 4.19.24 may be broken (albeit differently broken) as well. We got word the revert may break storage flows, most notably LSM. We are now investigating those claims. Bests, On 07/25/2017 10:19 AM, Francesco Romani wrote: > Hi infra, > > we have a new Vdsm tag on branch

Jenkins build is back to normal : system-sync_mirrors-centos-updates-el6-x86_64 #574

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

Re: [vdsm][tag][ovirt-4.1] Vdsm tagged: v4.19.24

Hello Francesco. Thanks. On Tue, Jul 25, 2017 at 10:19 AM, Francesco Romani wrote: > Hi infra, > > we have a new Vdsm tag on branch ovirt-4.1 for oVirt 4.1.4: > > tag v4.19.24 > Tagger: Francesco Romani > Date: Tue Jul 25 10:18:01 2017 +0200 > > Vdsm

[vdsm][tag][ovirt-4.1] Vdsm tagged: v4.19.24

Hi infra, we have a new Vdsm tag on branch ovirt-4.1 for oVirt 4.1.4: tag v4.19.24 Tagger: Francesco Romani Date: Tue Jul 25 10:18:01 2017 +0200 Vdsm 4.19.24 for oVirt 4.1.4 commit 0636c7f0aba95477699d812237cc8bc6d951cb0b Bests, -- Francesco Romani Senior SW Eng.,

[CQ]: 79771,1 (ovirt-log-collector) failed "ovirt-4.1" system tests

Change 79771,1 (ovirt-log-collector) is probably the reason behind recent system test failures in the "ovirt-4.1" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details

[JIRA] (OVIRT-1551) Add slaves to staging Jenkins instance

Barak Korren created OVIRT-1551: --- Summary: Add slaves to staging Jenkins instance Key: OVIRT-1551 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1551 Project: oVirt - virtualization made easy

[JIRA] (OVIRT-1551) Add slaves to staging Jenkins instance

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1551: Epic Link: OVIRT-403 > Add slaves to staging Jenkins instance >

Re: Jenkins error: java.io.FileNotFoundException: ... (Too many open files)

On 25 July 2017 at 09:03, Barak Korren wrote: > Maybe we need to increase the 'nofiles', but please link to the job > when ever you want to report something (And even better, send to > infra-support). > > Did re-triggering work? > > @Evegheny can you have a look? Ok. I

[JIRA] (OVIRT-1550) Configure and monitor nofiles on Jenkins

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1550: Epic Link: OVIRT-403 > Configure and monitor nofiles on Jenkins >

[JIRA] (OVIRT-1550) Configure and monitor nofiles on Jenkins

Barak Korren created OVIRT-1550: --- Summary: Configure and monitor nofiles on Jenkins Key: OVIRT-1550 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1550 Project: oVirt - virtualization made easy

Jenkins was restarted

Jenkins ran out of file descriptors so we had to restart it to bump the number. Jobs should be running jobs already but the UI will probably take 30-40 minutes to become available. Issues seem to have started around 15:00 UTC yesterday (18:00 IST) so you may need to re-trigger jobs for patches

Re: Jenkins error: java.io.FileNotFoundException: ... (Too many open files)

Maybe we need to increase the 'nofiles', but please link to the job when ever you want to report something (And even better, send to infra-support). Did re-triggering work? @Evegheny can you have a look? On 25 July 2017 at 02:48, Nir Soffer wrote: > Jenkins needs restart? >