- Infra - oVirt List Archives

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

20 Sep '17

------=_Part_622_688795696.1505862006356 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/449//artifact/exported-a… Cheers, Jenkins ------=_Part_622_688795696.1505862006356 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 - 19/09/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/system-sync_mirrors-centos-updates-el7-x86_64/">system-sync_mirrors-centos-updates-el7-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_622_688795696.1505862006356--

1 0

[CQ]: 81921,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 19 Sep '17

19 Sep '17

Change 81921,3 (ovirt-engine) 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/81921/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2719/

1 0

[JIRA] (OVIRT-1658) Potential issue coming to CentOS7 slaves (glibc, missing UTF-8 locale)
by Barak Korren (oVirt JIRA) 19 Sep '17

19 Sep '17

Barak Korren created OVIRT-1658: ----------------------------------- Summary: Potential issue coming to CentOS7 slaves (glibc, missing UTF-8 locale) Key: OVIRT-1658 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1658 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra Seems there is an issue with locale files in recent CentOS versions, and we're hitting it in slaves that have been updated recently. The symptoms are that Jenkins disconnects from the slave and then refuses to reconnect to it. The agent log in Jenkins shows: [09/19/17 15:42:56] [SSH] Connection closed. [09/19/17 15:58:48] [SSH] Opening SSH connection to vm0002.workers-phx.ovirt.org:22. [09/19/17 15:58:48] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection. [09/19/17 15:58:48] [SSH] Authentication successful. SSH connection reports a garbage before a command execution. Check your .bashrc, .profile, and so on to make sure it is quiet. The received junk text is as follows: /etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot change locale (en_US.utf8): No such file or directory /etc/profile.d/lang.sh: line 20: warning: setlocale: LC_COLLATE: cannot change locale (en_US.utf8): No such file or directory /etc/profile.d/lang.sh: line 23: warning: setlocale: LC_MESSAGES: cannot change locale (en_US.utf8): No such file or directory /etc/profile.d/lang.sh: line 26: warning: setlocale: LC_NUMERIC: cannot change locale (en_US.utf8): No such file or directory /etc/profile.d/lang.sh: line 29: warning: setlocale: LC_TIME: cannot change locale (en_US.utf8): No such file or directory null [09/19/17 15:58:48] Launch failed - cleaning up connection [09/19/17 15:58:48] [SSH] Connection closed. The same locale error messages can also be reproduced on the slave by running an interactive login from the console or 'su -'. When running 'locale -a' you can also see the en_US.UTF-8 locale is somehow missing. Looking around for this I found the following: https://github.com/CentOS/sig-cloud-instance-images/issues/71 I tried downgrading glibc back to the version we had before, but that did not seem to resolve the issue. Eventually I managed to resolve it by running 'localedef -i en_US -f UTF-8 en_US.UTF-8' on the slave. I've seen this happen on 'vm0002.workers-phx.ovirt.org' which is attached to the staging Jenkins, but I've no reason to believe this won't start impacting production slaves. We need to research this further and find out if we need to do something to prevent this issue from surfacing on production slaves. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)

1 0

[JIRA] (OVIRT-1657) Unity CI whitelist mechanism for GitHub and Gerrit
by Barak Korren (oVirt JIRA) 19 Sep '17

19 Sep '17

This is a multi-part message in MIME format... ------------=_1505835477-31751-486 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1657?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1657: ----------------------------------- Assignee: Barak Korren (was: infra) > Unity CI whitelist mechanism for GitHub and Gerrit > -------------------------------------------------- > > Key: OVIRT-1657 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1657 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > > Right now we have two separate CI mechanisms: > # A mechanism based on the '{{jenkins-whitelist}}' repository that is used by CI jobs for Gerrit projects > # A mechanism that is part of the 'GitHub pull request builder' plugin that is used for GitHub based projects. > The '{{jenkins-whitelist}}' has a few shortcomings: > * Its impossible for maintainers to manually override it > * Maintainers hate to send patches to an unrelated repo > * Its impossible to have a per-project whitelist > The GitHub style whitelist has a few shortcomings as well: > * Whitelist members that were added via comments on PRs are stored in the job configuration and can vanish if jobs are updated via JJB > * The GHPRB plugin forces us to create jobs in a very specific way (One job per project) > * The whitelist can prevent GitHub events without specific people behind them from triggering the jobs - For example jobs are not triggered when commits are added to an existing PR because such events are sent by the 'null' user whihc typically is not in the whitelist... (This is probably a bug with the plugin). -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060) ------------=_1505835477-31751-486 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1657?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1657:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>Unity CI whitelist mechanism for GitHub and Gerrit</h3> <pre> Key: OVIRT-1657 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1657 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: Barak Korren</pre> <p>Right now we have two separate CI mechanisms: # A mechanism based on the ‘{{jenkins-whitelist}}’ repository that is used by CI jobs for Gerrit projects # A mechanism that is part of the ‘GitHub pull request builder’ plugin that is used for GitHub based projects. The ‘{{jenkins-whitelist}}’ has a few shortcomings:</p> <ul><li><p>Its impossible for maintainers to manually override it</p></li> <li><p>Maintainers hate to send patches to an unrelated repo</p></li> <li><p>Its impossible to have a per-project whitelist</p></li></ul> <p>The GitHub style whitelist has a few shortcomings as well:</p> <ul><li><p>Whitelist members that were added via comments on PRs are stored in the job configuration and can vanish if jobs are updated via JJB</p></li> <li><p>The GHPRB plugin forces us to create jobs in a very specific way (One job per project)</p></li> <li><p>The whitelist can prevent GitHub events without specific people behind them from triggering the jobs – For example jobs are not triggered when commits are added to an existing PR because such events are sent by the ‘null’ user whihc typically is not in the whitelist… (This is probably a bug with the plugin).</p></li></ul></blockquote> <p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1505835477-31751-486--

1 0

[JIRA] (OVIRT-1657) Unity CI whitelist mechanism for GitHub and Gerrit
by Barak Korren (oVirt JIRA) 19 Sep '17

19 Sep '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1657?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1657: -------------------------------- Epic Link: OVIRT-400 > Unity CI whitelist mechanism for GitHub and Gerrit > -------------------------------------------------- > > Key: OVIRT-1657 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1657 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Right now we have two separate CI mechanisms: > # A mechanism based on the '{{jenkins-whitelist}}' repository that is used by CI jobs for Gerrit projects > # A mechanism that is part of the 'GitHub pull request builder' plugin that is used for GitHub based projects. > The '{{jenkins-whitelist}}' has a few shortcomings: > * Its impossible for maintainers to manually override it > * Maintainers hate to send patches to an unrelated repo > * Its impossible to have a per-project whitelist > The GitHub style whitelist has a few shortcomings as well: > * Whitelist members that were added via comments on PRs are stored in the job configuration and can vanish if jobs are updated via JJB > * The GHPRB plugin forces us to create jobs in a very specific way (One job per project) > * The whitelist can prevent GitHub events without specific people behind them from triggering the jobs - For example jobs are not triggered when commits are added to an existing PR because such events are sent by the 'null' user whihc typically is not in the whitelist... (This is probably a bug with the plugin). -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)

1 0

[JIRA] (OVIRT-1657) Unity CI whitelist mechanism for GitHub and Gerrit
by Barak Korren (oVirt JIRA) 19 Sep '17

19 Sep '17

Barak Korren created OVIRT-1657: ----------------------------------- Summary: Unity CI whitelist mechanism for GitHub and Gerrit Key: OVIRT-1657 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1657 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Right now we have two separate CI mechanisms: # A mechanism based on the '{{jenkins-whitelist}}' repository that is used by CI jobs for Gerrit projects # A mechanism that is part of the 'GitHub pull request builder' plugin that is used for GitHub based projects. The '{{jenkins-whitelist}}' has a few shortcomings: * Its impossible for maintainers to manually override it * Maintainers hate to send patches to an unrelated repo * Its impossible to have a per-project whitelist The GitHub style whitelist has a few shortcomings as well: * Whitelist members that were added via comments on PRs are stored in the job configuration and can vanish if jobs are updated via JJB * The GHPRB plugin forces us to create jobs in a very specific way (One job per project) * The whitelist can prevent GitHub events without specific people behind them from triggering the jobs - For example jobs are not triggered when commits are added to an existing PR because such events are sent by the 'null' user whihc typically is not in the whitelist... (This is probably a bug with the plugin). -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)

1 0

[JIRA] (OVIRT-1655) Groovy script failed
by Dafna Ron (oVirt JIRA) 19 Sep '17

19 Sep '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1655?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-1655: ---------------------------------- All 3 failed tasks ran on the same vm. I marked the vm as offline: vm0090.workers-phx.ovirt.org and the reason for offline is the failed job: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… > Groovy script failed > -------------------- > > Key: OVIRT-1655 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1655 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, I had an ovirt-node-ng build failure and didn't get logs about what > happened due to: > *Groovy script failed:* > java.lang.NullPointerException: Cannot invoke method child() on null object > Failed job is > http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… > CAn you please check what happened? > -- > 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> -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)

1 0

[JIRA] (OVIRT-1656) upgrade jenkins.ovirt.org to latest LTS version
by Evgheni Dereveanchin (oVirt JIRA) 19 Sep '17

19 Sep '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1656?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1656: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > upgrade jenkins.ovirt.org to latest LTS version > ----------------------------------------------- > > Key: OVIRT-1656 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1656 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Jenkins 2.73.1 LTS is out, our instance needs to be updated. > We should also update the OS to CentOS 7.4 and check if it's worth to bump plugin versions again. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)

1 0

[JIRA] (OVIRT-1656) upgrade jenkins.ovirt.org to latest LTS version
by Evgheni Dereveanchin (oVirt JIRA) 19 Sep '17

19 Sep '17

Evgheni Dereveanchin created OVIRT-1656: ------------------------------------------- Summary: upgrade jenkins.ovirt.org to latest LTS version Key: OVIRT-1656 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1656 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Jenkins 2.73.1 LTS is out, our instance needs to be updated. We should also update the OS to CentOS 7.4 and check if it's worth to bump plugin versions again. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)

1 0

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

19 Sep '17

------=_Part_608_659902070.1505824513264 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: 279 Build Status: Failure Triggered By: Started by user Sandro Bonazzola ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #279 [Yuval Turgeman] automation: adding loop devices ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_608_659902070.1505824513264--

1 3