- Infra - oVirt List Archives

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by Barak Korren (oVirt JIRA) 24 Jul '17

24 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1479: ------------------------------------- This might get fixed by OVIRT-1468, so lets implement it first and then see what happens. > dnf install in jobs setup scripts fails due to corrupted rpmdb > -------------------------------------------------------------- > > Key: OVIRT-1479 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt Infra > Reporter: ngoldin(a)redhat.com > Assignee: infra > Labels: rpmdb, standard-ci > > {code} > 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML > 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: BDB1507 Thread died in Berkeley DB library > 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery > 10:24:59 error: cannot open Packages index using db5 - (-30973) > 10:24:59 error: cannot open Packages database in /var/lib/rpm > 10:24:59 Error: Error: rpmdb open failed > 10:24:59 + failed=true > {code} > http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/… -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[oVirt Jenkins] ovirt_4.1_hc-system-tests - Build # 145 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_281_1770636090.1500866314566 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/145/ Build Number: 145 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #145 [Daniel Belenky] use temp cache dir instead of yum's default [Barak Korren] Make GitHub jobs deploy to 'tested' ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.edit_cluster Error Message: None != True after 600 seconds Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt_4.1_hc-system-tests/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 105, in edit_cluster testlib.assert_true_within(_engine_is_up, timeout=10 * 60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 256, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 230, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: None != True after 600 seconds ------=_Part_281_1770636090.1500866314566--

1 0

[oVirt Jenkins] ovirt_master_hc-system-tests - Build # 177 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_226_347315730.1500607071299 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/177/ Build Number: 177 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #177 [Daniel Belenky] use temp cache dir instead of yum's default ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.py.junit.xml.[empty] Error Message: Stack Trace: Test report file /home/jenkins/workspace/ovirt_master_hc-system-tests/exported-artifacts/002_bootstrap.py.junit.xml was length 0 ------=_Part_226_347315730.1500607071299--

1 3

oVirt infra daily report - unstable production jobs - 392
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_273_1517028123.1500850802632 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/392//artifact/exported-a… Cheers, Jenkins ------=_Part_273_1517028123.1500850802632 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 23/07/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/">ovirt_master_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_273_1517028123.1500850802632--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7655 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_269_1402065394.1500821658332 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7655/, Build Number: 7655, Build Status: FAILURE ------=_Part_269_1402065394.1500821658332--

1 1

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by danken (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] danken commented on OVIRT-1549: ------------------------------- They do release RPMs as part of RDO https://trunk.rdoproject.org/centos7-master/current/ but not per patch. If ovirt-infra does not have resources to have this per patch, we can start with a nightly run. ovsdbapp said that they can wait 40 minutes for our vote. > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1157) Re-factor the standard-CI triggers file
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1157?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1157: ----------------------------------- Assignee: Barak Korren (was: infra) > Re-factor the standard-CI triggers file > --------------------------------------- > > Key: OVIRT-1157 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1157 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: standard-ci > > The {{/jobs/confs/yaml/triggers/standard.yaml}} file contains A LOT of needless code duplication. We need to re-factor it with templates and YAML inheritance. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1549: ------------------------------------- If they don't release RPMs, how are our users supposed to consume this? The point of OST is to emulate what the user does, so 1st decide what the user does... Also WRT CI-1 on Gerrit, OST was never designed to do this, it takes far too long and far too many resources to be reasonable to run for every patch set. This is why we keep the process semi-automatic even for oVirt's own repos... > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by danken (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] danken commented on OVIRT-1549: ------------------------------- Sorry for missing the link to gerrit: https://review.openstack.org/#/q/project:openstack/ovsdbapp * I believe they build RPMs daily from merged code, but... * I don't think they currently release them officially * I want ovsdbapp to get a CI-1 if they break OST. I think that means "tracking the project at the source level". I believe that ovsdbapp would not mind adding automation/build-artefacts.sh if this is required > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1549: ------------------------------------- Without going into too much detail yet, the instruction you posted seem to refer to Gerrit projects, while the project you linked to is on GitHub? Is that project actually maintained in Gerrit? If so, where? Some more questions: * Does the project build RPMs? * Are those RPMs officially released somewhere? * Do we really want to track the project at the source level? If so, will the maintainers be willing to add an 'automation' directory and the related scripts? > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 298 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_245_434408739.1500696006298 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build Number: 298 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #298 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_245_434408739.1500696006298--

1 2

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by danken (oVirt JIRA) 23 Jul '17

23 Jul '17

danken created OVIRT-1549: ----------------------------- Summary: run OST as a third-party tester for OpenStack's ovsdbapp Key: OVIRT-1549 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: infra https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1548) Better STD-CI for GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1548?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1548: ----------------------------------- Assignee: Barak Korren (was: infra) > Better STD-CI for GitHub > ------------------------ > > Key: OVIRT-1548 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1548 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > Labels: github, standard-ci > > We currently have some support for crating STD-CI jobs for projects running on GitHub. There are however, several issues with it: > * The job templates you use for GitHub are different then the ones you use for Gerrit: > ** Job names need to contain '\-github-' > ** In Gerrit you need a separate 'project' entry for the 'build-artifacts' jobs, in GitHub you need a separate one for 'check-patch'. > ** SCM checkout details are specified in the 'project' entry as opposed to a separate SCM file (We might want to adopt this for Gerrit). > * The 'check-patch' jobs do not have full STC-CI. They don't run the post-build steps. > * The triggering scheme is strange: > ** All jobs trigger when certain messages are posted in the PR comments. > ** Nothing is triggered automatically (As opposed to Gerrit where CI runs as soon as a patchset is submitted) > ** Nothing triggers when a PR is merged (As opposed to with Gerrit where 'check-merged' and 'build-artifacts' are triggered on merge). > * The white-listing scheme is different: > ** The 'jenkins-whiltelist' file does not effect theses jobs at all. > ** GitHub project/organisation membership determines white-listing > ** white-listing is determined by who added the comment to run CI, not who authored the patch. > Some of these issues and differences had already been tracked in other tickets. This ticket is for concentrating all related work. Other related tickets will be linked to it as blockers. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1548) Better STD-CI for GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

Barak Korren created OVIRT-1548: ----------------------------------- Summary: Better STD-CI for GitHub Key: OVIRT-1548 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1548 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: High We currently have some support for crating STD-CI jobs for projects running on GitHub. There are however, several issues with it: * The job templates you use for GitHub are different then the ones you use for Gerrit: ** Job names need to contain '\-github-' ** In Gerrit you need a separate 'project' entry for the 'build-artifacts' jobs, in GitHub you need a separate one for 'check-patch'. ** SCM checkout details are specified in the 'project' entry as opposed to a separate SCM file (We might want to adopt this for Gerrit). * The 'check-patch' jobs do not have full STC-CI. They don't run the post-build steps. * The triggering scheme is strange: ** All jobs trigger when certain messages are posted in the PR comments. ** Nothing is triggered automatically (As opposed to Gerrit where CI runs as soon as a patchset is submitted) ** Nothing triggers when a PR is merged (As opposed to with Gerrit where 'check-merged' and 'build-artifacts' are triggered on merge). * The white-listing scheme is different: ** The 'jenkins-whiltelist' file does not effect theses jobs at all. ** GitHub project/organisation membership determines white-listing ** white-listing is determined by who added the comment to run CI, not who authored the patch. Some of these issues and differences had already been tracked in other tickets. This ticket is for concentrating all related work. Other related tickets will be linked to it as blockers. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1548) Better STD-CI for GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1548?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1548: -------------------------------- Epic Link: OVIRT-400 > Better STD-CI for GitHub > ------------------------ > > Key: OVIRT-1548 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1548 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: github, standard-ci > > We currently have some support for crating STD-CI jobs for projects running on GitHub. There are however, several issues with it: > * The job templates you use for GitHub are different then the ones you use for Gerrit: > ** Job names need to contain '\-github-' > ** In Gerrit you need a separate 'project' entry for the 'build-artifacts' jobs, in GitHub you need a separate one for 'check-patch'. > ** SCM checkout details are specified in the 'project' entry as opposed to a separate SCM file (We might want to adopt this for Gerrit). > * The 'check-patch' jobs do not have full STC-CI. They don't run the post-build steps. > * The triggering scheme is strange: > ** All jobs trigger when certain messages are posted in the PR comments. > ** Nothing is triggered automatically (As opposed to Gerrit where CI runs as soon as a patchset is submitted) > ** Nothing triggers when a PR is merged (As opposed to with Gerrit where 'check-merged' and 'build-artifacts' are triggered on merge). > * The white-listing scheme is different: > ** The 'jenkins-whiltelist' file does not effect theses jobs at all. > ** GitHub project/organisation membership determines white-listing > ** white-listing is determined by who added the comment to run CI, not who authored the patch. > Some of these issues and differences had already been tracked in other tickets. This ticket is for concentrating all related work. Other related tickets will be linked to it as blockers. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1547?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1547: ------------------------------------- There is no bot here. This seems to be the logic on the GitHub pull-request trigger plugin when if is configured to filter by project/organisation membership. I suspect the amount of alerts matches the amount of jobs we have triggering on pull request events exactly. We probably need a staging environment for further testing and coming up with solutions, so adding OVIRT-1533 as a blocker > limit the amount of warnings the whitelist bots sends to GitHub > --------------------------------------------------------------- > > Key: OVIRT-1547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: infra > > I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: > https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1547?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1547: -------------------------------- Issue Type: Bug (was: Task) > limit the amount of warnings the whitelist bots sends to GitHub > --------------------------------------------------------------- > > Key: OVIRT-1547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: infra > > I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: > https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by eyal edri (oVirt JIRA) 23 Jul '17

23 Jul '17

eyal edri created OVIRT-1547: -------------------------------- Summary: limit the amount of warnings the whitelist bots sends to GitHub Key: OVIRT-1547 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri Assignee: infra I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1547) limit the amount of warnings the whitelist bots sends to GitHub
by eyal edri (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1547?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1547: ----------------------------- Epic Link: OVIRT-400 > limit the amount of warnings the whitelist bots sends to GitHub > --------------------------------------------------------------- > > Key: OVIRT-1547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1547 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > > I'm not sure how the logic of the whitelist bot is done, but it looks like its sending too many messages back to GitHub: > https://github.com/oVirt/ovirt-ansible/pull/23 - on 1 commits there were 13 alerts. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 200 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_243_976463564.1500696005282 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build Number: 200 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #200 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_243_976463564.1500696005282--

1 1

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 200 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_241_608899719.1500696005012 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build Number: 200 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_241_608899719.1500696005012--

1 1

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 483 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_247_1010026508.1500696265975 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 483 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #483 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_247_1010026508.1500696265975--

1 1

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #551
by jenkins＠jenkins.phx.ovirt.org 22 Jul '17

22 Jul '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/551/displa…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) Commit message: "Exclude big packages from mirrors" > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins5437237118876510709.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 904, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc26/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 391
by jenkins＠jenkins.phx.ovirt.org 22 Jul '17

22 Jul '17

------=_Part_250_2007816077.1500764401034 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/391//artifact/exported-a… Cheers, Jenkins ------=_Part_250_2007816077.1500764401034 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 22/07/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/">ovirt_master_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/">system-sync_mirrors-epel-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_250_2007816077.1500764401034--

1 0

[oVirt Jenkins] ovirt-release_master_build-artifacts-fc26-x86_64 - Build # 60 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Jul '17

21 Jul '17

------=_Part_222_1147400079.1500596379856 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fc26-x86_… Build: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fc26-x86_… Build Number: 60 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #60 [Ryan Barry] host-node: add vdsm-hook-vfio-mdev ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_222_1147400079.1500596379856--

1 1

oVirt infra daily report - unstable production jobs - 390
by jenkins＠jenkins.phx.ovirt.org 21 Jul '17

21 Jul '17

------=_Part_231_187681130.1500678003434 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/390//artifact/exported-a… Cheers, Jenkins ------=_Part_231_187681130.1500678003434 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 21/07/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/">ovirt_master_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_231_187681130.1500678003434--

1 0

[JIRA] (OVIRT-1546) update iDRAC firmware on ovirt-srv02
by Evgheni Dereveanchin (oVirt JIRA) 21 Jul '17

21 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1546?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1546: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > update iDRAC firmware on ovirt-srv02 > ------------------------------------ > > Key: OVIRT-1546 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1546 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > iDRAC on ovirt-srv02 does not show the admin page any more so it needs to be restarted. After doing that it's best to also upgrade firmware to the latest version. Workload needs to be evacuated off this server before doing maintenance tasks on it. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1546) update iDRAC firmware on ovirt-srv02
by Evgheni Dereveanchin (oVirt JIRA) 21 Jul '17

21 Jul '17

Evgheni Dereveanchin created OVIRT-1546: ------------------------------------------- Summary: update iDRAC firmware on ovirt-srv02 Key: OVIRT-1546 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1546 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra iDRAC on ovirt-srv02 does not show the admin page any more so it needs to be restarted. After doing that it's best to also upgrade firmware to the latest version. Workload needs to be evacuated off this server before doing maintenance tasks on it. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1292) make ovirt-release RPMs RHEL compatible
by sbonazzo (oVirt JIRA) 21 Jul '17

21 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1292?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1292: ---------------------------- Assignee: sbonazzo (was: infra) Status: In Progress (was: To Do) I'm on it. > make ovirt-release RPMs RHEL compatible > --------------------------------------- > > Key: OVIRT-1292 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1292 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: sbonazzo > > Some oVirt users are using the ovirt-release el7 RPMs to test oVirt on RHEL. > Unfortunately, RHEL uses the '7Server' link which doesn't exist in CentOS resulting in breakage like: > 'http://mirror.centos.org/centos/7Server/virt/x86_64/kvm-common/' > while 'http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/' exist > We should either ask CentOS to add that link on the repo or find a way to fix it ourselves in the release rpm. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

Build failed in Jenkins: system-mk_mirrors_index-yum #8981
by jenkins＠jenkins.phx.ovirt.org 21 Jul '17

21 Jul '17

See <http://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/8981/display/redir…> ------------------------------------------ Started by upstream project "system-sync_mirrors-fedora-updates-fc24-x86_64" build number 476 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/68/79068/9:patch --prune ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://gerrit.ovirt.org/jenkins.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:812) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1079) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1110) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:560) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:485) at hudson.model.Run.execute(Run.java:1735) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:405) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/68/79068/9:patch --prune" returned status code 128: stdout: stderr: fatal: unable to access 'http://gerrit.ovirt.org/jenkins.git/': Failed connect to gerrit.ovirt.org:80; Connection timed out at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1877) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1596) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:71) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:348) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) at ......remote call to mirrors.phx.ovirt.org(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:830) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy74.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810) ... 11 more ERROR: Error fetching remote repo 'origin'

1 1

oVirt infra daily report - unstable production jobs - 389
by jenkins＠jenkins.phx.ovirt.org 20 Jul '17

20 Jul '17

------=_Part_220_1518450489.1500591603313 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/389//artifact/exported-a… Cheers, Jenkins ------=_Part_220_1518450489.1500591603313 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 20/07/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> ------=_Part_220_1518450489.1500591603313--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7620 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Jul '17

20 Jul '17

------=_Part_160_551255177.1500475535820 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7620/, Build Number: 7620, Build Status: FAILURE ------=_Part_160_551255177.1500475535820--

1 18

[CQ]: 79645, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Jul '17

20 Jul '17

A system test invoked by the "ovirt-master" change queue including change 79645,1 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 79566,2 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 79566,2 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/79645/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/79566/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1445/

1 0

Change in stage-stdci1[master]: Make separate files for all CI stages
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/69 ) Change subject: Make separate files for all CI stages ...................................................................... Patch Set 1: Code-Review+2 Verified+1 ci please build -- To view, visit https://gerrit-staging.phx.ovirt.org/69 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I21e93c31d26799db0d7d69cc3c830094f7ac8e63 Gerrit-PatchSet: 1 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Make separate files for all CI stages
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/69 ) Change subject: Make separate files for all CI stages ...................................................................... Patch Set 1: ci please build -- To view, visit https://gerrit-staging.phx.ovirt.org/69 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I21e93c31d26799db0d7d69cc3c830094f7ac8e63 Gerrit-PatchSet: 1 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

[CQ]: 79640, 2 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Jul '17

20 Jul '17

A system test invoked by the "ovirt-master" change queue including change 79640,2 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 79566,2 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 79566,2 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/79640/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/79566/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1441/

1 0

[CQ]: 79561, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Jul '17

20 Jul '17

A system test invoked by the "ovirt-master" change queue including change 79561,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 79560,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 79560,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/79561/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/79560/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1439/

1 0

[CQ]: 79341, 4 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Jul '17

20 Jul '17

A system test invoked by the "ovirt-master" change queue including change 79341,4 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 79566,2 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 79566,2 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/79341/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/79566/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1437/

1 0

[CQ]: 79566,2 (otopi) failed "ovirt-master" system tests
by oVirt Jenkins 20 Jul '17

20 Jul '17

Change 79566,2 (otopi) 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 change see: https://gerrit.ovirt.org/#/c/79566/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1436/

1 0

Change in stage-stdci1[master]: Adding a README file and stub CI scripts
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/68 ) Change subject: Adding a README file and stub CI scripts ...................................................................... Adding a README file and stub CI scripts Checking if check-patch runs on such a change or not. Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- A README.markdown A automation/build-artifacts.sh A automation/check-merged.sh A automation/check-patch.sh 4 files changed, 14 insertions(+), 0 deletions(-) Approvals: Jenkins CI: Passed CI tests Barak Korren: Looks good to me, approved; Verified -- To view, visit https://gerrit-staging.phx.ovirt.org/68 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Gerrit-PatchSet: 6 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in stage-stdci1[master]: Adding a README file and stub CI scripts
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/68 ) Change subject: Adding a README file and stub CI scripts ...................................................................... Patch Set 6: Code-Review+2 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/68 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Gerrit-PatchSet: 6 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Adding a README file and stub CI scripts
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/68 ) Change subject: Adding a README file and stub CI scripts ...................................................................... Patch Set 6: ci please build -- To view, visit https://gerrit-staging.phx.ovirt.org/68 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Gerrit-PatchSet: 6 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Adding a README file and stub CI scripts
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/68 ) Change subject: Adding a README file and stub CI scripts ...................................................................... Patch Set 6: ci please build -- To view, visit https://gerrit-staging.phx.ovirt.org/68 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Gerrit-PatchSet: 6 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Adding a README file and stub CI scripts
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/68 ) Change subject: Adding a README file and stub CI scripts ...................................................................... Patch Set 6: ci please build -- To view, visit https://gerrit-staging.phx.ovirt.org/68 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Gerrit-PatchSet: 6 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Adding a README file and stub CI scripts
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/68 ) Change subject: Adding a README file and stub CI scripts ...................................................................... Patch Set 6: ci please build -- To view, visit https://gerrit-staging.phx.ovirt.org/68 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Gerrit-PatchSet: 6 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

vdsm ppc64le support
by Sandro Bonazzola 20 Jul '17

20 Jul '17

Hi, we dropped publishing vdsm ppc64le builds on snapshot repos due to issues keeping aligned nvr between x86_64 and ppc64le. Today we're still missing ppc64le builds on http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/el7/ppc64le/ Where do we stand with the support for the build of the same nvr ob both arches? Can we get it re-enabled? Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

3 6

Removing 4.0 build jobs from Jenkins
by Daniel Belenky 20 Jul '17

20 Jul '17

Hi all, In order to free space in our Jenkins master host (jenkins.ovirt.org) we'll need to remove some of the jobs and their artifacts. For now, we are planning to remove all 4.0 jobs. If there is any job that you want to keep, please reply to this email with details. Thanks, -- DANIEL BELENKY Associate sw engineer RHEV DEVOPS EMEA VIRTUALIZATION R&D Red Hat Israel <https://www.redhat.com/> dbelenky(a)redhat.com IRC: #rhev-integ, #rhev-dev <https://red.ht/sig>

3 2

Change in stage-stdci1[master]: Adding a README file and stub CI scripts
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/68 to look at the new patch set (#6). Change subject: Adding a README file and stub CI scripts ...................................................................... Adding a README file and stub CI scripts Checking if check-patch runs on such a change or not. Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- A README.markdown A automation/build-artifacts.sh A automation/check-merged.sh A automation/check-patch.sh 4 files changed, 14 insertions(+), 0 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/68/68/6 -- To view, visit https://gerrit-staging.phx.ovirt.org/68 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Gerrit-PatchSet: 6 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

[CQ]: 79544, 4 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Jul '17

20 Jul '17

A system test invoked by the "ovirt-master" change queue including change 79544,4 (ovirt-host) failed. However, this change seems not to be the root cause for this failure. Change 79627,1 (ovirt-host) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 79627,1 (ovirt-host) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/79544/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/79627/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1434/

1 0

Change in stage-stdci1[master]: Adding a README file and stub CI scripts
by review＠gerrit-staging.phx.ovirt.org 20 Jul '17

20 Jul '17

>From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/68 to look at the new patch set (#5). Change subject: Adding a README file and stub CI scripts ...................................................................... Adding a README file and stub CI scripts Checking if check-patch runs on such a change or not. Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- A README.markdown A automation/check-patch.sh 2 files changed, 13 insertions(+), 0 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/68/68/5 -- To view, visit https://gerrit-staging.phx.ovirt.org/68 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I3446f643f2acd843cfb8011edf5277fbfaa6a26e Gerrit-PatchSet: 5 Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0