[JIRA] (OVIRT-1635) jenkins not marking CI +1

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=34857#comment-34857 ] sbonazzo commented on OVIRT-1635: - Here as well:https://gerrit.ovirt.org/#/c/81475/ > jenkins not marking CI

[JIRA] (OVIRT-1635) jenkins not marking CI +1

sbonazzo created OVIRT-1635: --- Summary: jenkins not marking CI +1 Key: OVIRT-1635 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1635 Project: oVirt - virtualization made easy Issue Type:

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 22 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/22/ Build Number: 22 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 20 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/20/ Build Number: 20 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[CQ]: 81449, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81449,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 81416, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81416,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 81415, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81415,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

oVirt infra daily report - unstable production jobs - 435

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

[CQ]: 81358, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81358,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 81068, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81068,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

Re: [ovirt-devel] New design for the Gerrit UI

Hi, it looks nice. Is there any plan * to actually deploy this skin on gerrit.ovirt.org? * skin new gerrit UI (PolyGerrit) as well? * use blue theme as webadmin recently adopted and VM Portal is going to adopt? Thanks Jakub On Wed, May 10, 2017 at 10:56 PM, Phillip Bailey

[CQ]: 81400, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81400,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 21 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/21/ Build Number: 21 Build Status: Still Failing Triggered By: Started by user Eyal Edri - Changes

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #686

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

[CQ]: 81357, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81357,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 81380, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81380,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JIRA] (OVIRT-1634) Re: please add me to whitelist. thanks

eyal edri created OVIRT-1634: Summary: Re: please add me to whitelist. thanks Key: OVIRT-1634 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1634 Project: oVirt - virtualization made easy

Re: please add me to whitelist. thanks

Sending to infra-support to open a ticket. On Tue, Sep 5, 2017 at 4:47 PM, Eitan Raviv wrote: > > No Builds Executed > > http://jenkins.ovirt.org/job/ovirt-engine_master_check- > patch-fc25-x86_64/13489/ : To avoid overloading the infrastructure, a > whitelist for running

[CQ]: 81437, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81437,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JIRA] (OVIRT-1633) Jenkins doesn't copy CI's ack

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Belenky updated OVIRT-1633: -- Resolution: Won't Fix Status: Done (was: To Do) > Jenkins doesn't copy CI's ack >

[JIRA] (OVIRT-1633) Jenkins doesn't copy CI's ack

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=34856#comment-34856 ] Daniel Belenky commented on OVIRT-1633: --- This is an old and known issue. The code doing the marking is

[JIRA] (OVIRT-1633) Jenkins doesn't copy CI's ack

Arik Hadas created OVIRT-1633: - Summary: Jenkins doesn't copy CI's ack Key: OVIRT-1633 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1633 Project: oVirt - virtualization made easy Issue

[JIRA] (OVIRT-1632) slave cleanup fails with ERROR: Failed to clean docker images

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=34855#comment-34855 ] Daniel Belenky commented on OVIRT-1632: --- Hey [~ederevea], the problem is probably due to a race

[JIRA] (OVIRT-1632) slave cleanup fails with ERROR: Failed to clean docker images

Evgheni Dereveanchin created OVIRT-1632: --- Summary: slave cleanup fails with ERROR: Failed to clean docker images Key: OVIRT-1632 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1632 Project:

[CQ]: 81431, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81431,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 81433, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81433,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 81432, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 81432,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

Re: [oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 4 - Failure!

I notice the build job is failing more often recently due to cleanup of the loop devices [1], Any thoughts how we can solve it? are there other tools we can use that will use loop devices differently which won't require cleanups? [1] down. *08:01:07* 2017-09-05 08:01:07,254: Shutting down

[CQ]: 81205,9 (ovirt-dwh) failed "ovirt-master" system tests

Change 81205,9 (ovirt-dwh) 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

[CQ]: 81445,1 (ovirt-dwh) failed "ovirt-4.1" system tests

Change 81445,1 (ovirt-dwh) 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 about the

[JIRA] (OVIRT-1631) hosted engine tests failing on Cannot detect virualization

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-1631: --- Assignee: Evgheni Dereveanchin (was: infra) > hosted engine tests failing

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-snapshot_build-artifacts-el7-x86_64 - Build # 2 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-snapshot_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-snapshot_build-artifacts-el7-x86_64/2/ Build Number: 2 Build Status: Still Failing Triggered By: Started by timer

[CQ]: 80795, 30 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 80795,30 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #685

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 2 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64/2/ Build Number: 2 Build Status: Still Failing Triggered By: Started by timer

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 4 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/4/ Build Number: 4 Build Status: Failure Triggered By: Started by user Daniel -

[CQ]: 80102, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 80102,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 3 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/3/ Build Number: 3 Build Status: Fixed Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 5 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/5/ Build Number: 5 Build Status: Failure Triggered By: Started by user Daniel -

Please go vote for issue on Jenkins Jira

We use HTML in build description for many things, but it is not shown properly by Blue Ocean. Here is the ticket to solve it: https://issues.jenkins-ci.org/browse/JENKINS-45719 Its currently in low priority, please go and vote for it if you can to hopefully raise the priority. -- Barak Korren

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 245 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/245/ Build Number: 245 Build Status: Fixed Triggered By: Started by timer

[CQ]: 78307, 46 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 78307,46 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79034,6 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JIRA] (OVIRT-1631) hosted engine tests failing on Cannot detect virualization

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=34852#comment-34852 ] Barak Korren commented on OVIRT-1631: - {quote} Anything changed on host configuration / lago that prevent

Re: hc test failing 'Physical Volume Exists' not in result.msg'

There was an error setting up environment prior to this - I've posted https://gerrit.ovirt.org/#/c/81429/ to fix that. On Tue, Sep 5, 2017 at 12:24 PM, Sandro Bonazzola wrote: >

hc test failing 'Physical Volume Exists' not in result.msg'

http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/19/artifact/exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.hc-basic_suite_master.sh/hc-basic_suite_master.sh.log Looks like it's failing preparing storage on the vms. Can you please have a look? TASK [Create Physical

Re: Change in ovirt-system-tests[master]: Remove MAC Address from hosted-engine answer files

Looking at the hc failures, the issue seems to be a missing package since Sep 1 [1]. I think the reposync config may need to be updated 2017-09-05 02:33:55,423::ssh.py::ssh::96::lago.ssh::DEBUG::Command a243ce7a on lago-hc-basic-suite-master-host0 errors: Error: Package:

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 2 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/2/ Build Number: 2 Build Status: Still Failing Triggered By: Started by timer -