- Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5806 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Mar '17

13 Mar '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #942 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Mar '17

13 Mar '17

------=_Part_34_160855325.1489435621177 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/942/, Build Number: 942, Build Status: FAILURE ------=_Part_34_160855325.1489435621177--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5804 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Mar '17

13 Mar '17

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5804/, Build Number: 5804, Build Status: FAILURE

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5802 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Mar '17

13 Mar '17

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

1 1

[JIRA] (OVIRT-1255) artifactory low space warning
by Evgheni Dereveanchin (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1255?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1255: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > artifactory low space warning > ----------------------------- > > Key: OVIRT-1255 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1255 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Artifactory is slowly running out of space. Currently free space is at 20% which triggered a nagios warning. Need to increase the data disk. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1255) artifactory low space warning
by Evgheni Dereveanchin (oVirt JIRA) 13 Mar '17

13 Mar '17

Evgheni Dereveanchin created OVIRT-1255: ------------------------------------------- Summary: artifactory low space warning Key: OVIRT-1255 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1255 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Artifactory is slowly running out of space. Currently free space is at 20% which triggered a nagios warning. Need to increase the data disk. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

Fwd: ** RECOVERY Service Alert: ovirt-mirrorchecker/www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync is OK **
by Nadav Goldin 13 Mar '17

13 Mar '17

Hi, The oVirt mirror seems out of sync again, Can you please check? Thanks, Nadav. ---------- Forwarded message ---------- From: icinga <icinga(a)monitoring.ovirt.org> Date: Mon, Mar 13, 2017 at 3:15 PM Subject: ** RECOVERY Service Alert: ovirt-mirrorchecker/www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync is OK ** To: ngoldin(a)redhat.com ***** Icinga ***** Notification Type: RECOVERY Service: www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync Host: ovirt-mirrorchecker Address: 66.187.230.105 State: OK Date/Time: Mon Mar 13 13:15:00 UTC 2017 Additional Info: OK - 233 seconds since last sync, which are 0.0647 hours.

1 0

[JIRA] (OVIRT-1254) add to infra docs on supporting building containers in std ci
by eyal edri [Administrator] (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1254?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1254: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > add to infra docs on supporting building containers in std ci > ------------------------------------------------------------- > > Key: OVIRT-1254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1254 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > Priority: High > > We now support building containers in standard CI. > we need to document how a developer will use it and to give example the ovirt-container-engine once it works. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1254) add to infra docs on supporting building containers in std ci
by eyal edri [Administrator] (oVirt JIRA) 13 Mar '17

13 Mar '17

eyal edri [Administrator] created OVIRT-1254: ------------------------------------------------ Summary: add to infra docs on supporting building containers in std ci Key: OVIRT-1254 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1254 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: High We now support building containers in standard CI. we need to document how a developer will use it and to give example the ovirt-container-engine once it works. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1254) add to infra docs on supporting building containers in std ci
by eyal edri [Administrator] (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1254?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1254: --------------------------------------------- Epic Link: OVIRT-400 > add to infra docs on supporting building containers in std ci > ------------------------------------------------------------- > > Key: OVIRT-1254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1254 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > We now support building containers in standard CI. > we need to document how a developer will use it and to give example the ovirt-container-engine once it works. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1073) Gradually remove jobs from master publisher
by eyal edri [Administrator] (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1073?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1073: ------------------------------------------------ Assignee: eyal edri [Administrator] (was: infra) > Gradually remove jobs from master publisher > ------------------------------------------- > > Key: OVIRT-1073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > > We saw how destructive using the current publishers can be during 4.1 cycle, > Problems we encountered: > 1. It hides missing RPMs from experimental flows > 2. It hides projects that needs to branch or using previous version released > 3. It creates confusion of which RPMs are really tested in OST and give different results than experimental instead of having a single source of RPMs for oVirt. > We should aim to drop it for 4.2 and use only experimental deployment. > However, since we have errors on deploy to experimental flow, we can't progress with this until they will be solved. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Barak Korren (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1250: ------------------------------------- Can we generalize it to the point where we will have just one pipeline job that will do all the triggering for all projects (E.g based on the existence of jobs for those projects)? > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5795 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Mar '17

13 Mar '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5793 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Mar '17

13 Mar '17

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

1 1

[JIRA] (OVIRT-1253) document PHX OpenVPN
by Evgheni Dereveanchin (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1253?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1253: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > document PHX OpenVPN > -------------------- > > Key: OVIRT-1253 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1253 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > document the service and how to add users -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1253) document PHX OpenVPN
by Evgheni Dereveanchin (oVirt JIRA) 13 Mar '17

13 Mar '17

Evgheni Dereveanchin created OVIRT-1253: ------------------------------------------- Summary: document PHX OpenVPN Key: OVIRT-1253 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1253 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra document the service and how to add users -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Pavel Zhukov (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] Pavel Zhukov commented on OVIRT-1250: ------------------------------------- [~bkorren(a)redhat.com] [~eedri] Right. But it's not purpose of this ticket. The problem is this "you're not in whitelist" message is sent 4 (or more) times. It's pointless. The only solution I can see now is pipeline (again). We have to check whitelist if user is not whitelisted then give them one single message otherwise trigger other jobs (per branch/OS). > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

ovirt_4.1_he-system-tests Failed!
by jenkins＠jenkins.phx.ovirt.org 12 Mar '17

12 Mar '17

------=_Part_20_1766333648.1489027049728 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/34/ Build Number: 34 Build Status: Still Failing Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #29 [Ondra Machacek] Add Ansible modules tests [Sandro Bonazzola] pywin32-py2.7: drop fc24 on master [Sandro Bonazzola] nsis-simple-service-plugin: drop fc24 on master [Eyal Edri] adding job for master ansible suite Changes for Build #30 [Ondra Machacek] Add Ansible modules tests Changes for Build #31 [Yaniv Kaul] Remove cockpit-ovirt installation test Changes for Build #32 [Yaniv Kaul] Remove cockpit-ovirt installation test [Yedidyah Bar David] ovirt-wgt: Built master only on fc25 [Greg Sheremeta] ovirt-engine-phantomjs: configure jobs Changes for Build #33 [Yaniv Kaul] Slim down the amount of packages we sync Changes for Build #34 [Yaniv Kaul] Slim down the amount of packages we sync [Eyal Edri] remove emails from repo closure jobs ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_20_1766333648.1489027049728--

1 3

oVirt infra daily report - unstable production jobs - 256
by jenkins＠jenkins.phx.ovirt.org 12 Mar '17

12 Mar '17

------=_Part_16_907299769.1489359617015 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/256//artifact/exported-a… Cheers, Jenkins ------=_Part_16_907299769.1489359617015 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 - 12/03/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_4.0_image-ng-system-tests/">ovirt_4.0_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/ovirt_4.1_hc-system-tests/">ovirt_4.1_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.  NOT STABLE YET </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_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_4.1_image-ng-system-tests/">ovirt_4.1_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/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_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/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</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/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</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/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</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/repos_master_check-closure_fc25_merged/">repos_master_check-closure_fc25_merged</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_16_907299769.1489359617015--

1 0

[ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.hotplug_nic ]
by Daniel Belenky 12 Mar '17

12 Mar '17

*Test failed: *basic_sanity.hotplug_nic *Link to failed job: *test-repo_ovirt_experimental_4.1/917/ <http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper…> *Link to all logs: *logs from Jenkins <http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper…> *May be related to: *https://bugzilla.redhat.com/show_bug.cgi?id=1417595 *Error snippet from log: *(from supervdsm.log): ifup/VLAN100_Network::DEBUG::2017-03-08 22:24:22,832::commands::93::root::(execCmd) FAILED: <err> = 'Running scope as unit ff994cde-b66d-4d54-9e36-fc253682608f.scope.\n/etc/sysconfig/network-scripts/ifup-eth: line 297: 16985 Terminated /sbin/dhclient ${DHCLIENTARGS} ${DEVICE}\nCannot find device "VLAN100_Network"\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\n'; <rc> = 1 ifup/VLAN100_Network::ERROR::2017-03-08 22:24:22,832::utils::371::root::(wrapper) Unhandled exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 368, in wrapper return f(*a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 180, in run return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 924, in _exec_ifup _exec_ifup_by_name(iface.name, cgroup) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 910, in _exec_ifup_by_name raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '') ConfigNetworkError: (29, 'Determining IPv6 information for VLAN100_Network... failed.') -- *Daniel Belenky* *RHV DevOps* *Red Hat Israel*

2 2

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Barak Korren (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1250: ------------------------------------- We probably shouldn't just add everyone to the oVirt org. instead we should probably instruct the maintainers to run 'ci test please' to confirm the PR. (Or add to the org of they choose to) > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1250: -------------------------------------------------- Until we fix this, can we replace the message with something like: You're not part of the oVirt organization, please request one of the oVirt infra members to add you to be able to send PR requests. > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1252: --------------------------------------------- Labels: standard-ci (was: ) > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by Barak Korren (oVirt JIRA) 12 Mar '17

12 Mar '17

Barak Korren created OVIRT-1252: ----------------------------------- Summary: post-merge build-artifacts jobs can run out of order Key: OVIRT-1252 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Barak Korren Assignee: infra Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by Barak Korren (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1252: -------------------------------- Epic Link: OVIRT-400 > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1251) create status.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1251?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1251: -------------------------------------------------- https://cachethq.io/ looks like a cool OSS project we can use for it. > create status.ovirt.org > ----------------------- > > Key: OVIRT-1251 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > Similar to other projects: > https://status.newrelic.com/ > https://status.centos.org/ > It should run probably using local storage so it won't get affected by a storage outage. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1251) create status.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1251?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1251: --------------------------------------------- Epic Link: OVIRT-840 > create status.ovirt.org > ----------------------- > > Key: OVIRT-1251 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > Similar to other projects: > https://status.newrelic.com/ > https://status.centos.org/ > It should run probably using local storage so it won't get affected by a storage outage. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1251) create status.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

eyal edri [Administrator] created OVIRT-1251: ------------------------------------------------ Summary: create status.ovirt.org Key: OVIRT-1251 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: eyal edri [Administrator] Assignee: infra Similar to other projects: https://status.newrelic.com/ https://status.centos.org/ It should run probably using local storage so it won't get affected by a storage outage. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plug… ] eyal edri [Administrator] updated OST-39: ----------------------------------------- Status: In Review (was: To Do) > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plug… ] eyal edri [Administrator] commented on OST-39: ---------------------------------------------- still trying to move it to blocked status, please ignore for now. > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plug… ] eyal edri [Administrator] updated OST-39: ----------------------------------------- Status: To Do (was: In Review) > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #146
by jenkins＠jenkins.phx.ovirt.org 12 Mar '17

12 Mar '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/146/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/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision ed4375cef5aea05f4940a81483eda9488f364078 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ed4375cef5aea05f4940a81483eda9488f364078 > git rev-list ed4375cef5aea05f4940a81483eda9488f364078 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson21156725790525527.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 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, 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 1451, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1429, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 911, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 899, 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-fc24/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5783 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Mar '17

12 Mar '17

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

1 1

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 07/02/17 ] [ add_secondary_storage_domains ]
by Nir Soffer 12 Mar '17

12 Mar '17

Is this 4.1 or 4.0 test? These vdsm logs are in 4.0 format. בתאריך 7 במרץ 2017 10:17 לפנה״צ,‏ "Yaniv Kaul" <ykaul(a)redhat.com> כתב: On Tue, Mar 7, 2017 at 9:44 AM Daniel Belenky <dbelenky(a)redhat.com> wrote: > *Test failed:* add_secondary_storage_domains > > *Link to failed Job: *test-repo_ovirt_experimental_4.1/889 > <http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper…> > > *Link to all logs: *logs from Jenkins > <http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper…> > > *Error snippet from log:* > > 2017-03-07 01:29:03,789::utils.py::_ret_via_queue::59::lago.utils::ERROR::Error > while running thread > > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue > queue.put({'return': func()}) > File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/002_bootstrap.py", line 574, in add_iso_storage_domain > add_generic_nfs_storage_domain(prefix, SD_ISO_NAME, SD_ISO_HOST_NAME, SD_ISO_PATH, sd_format='v1', sd_type='iso', nfs_version='v3') > File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/002_bootstrap.py", line 437, in add_generic_nfs_storage_domain > add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version) > File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/002_bootstrap.py", line 493, in add_generic_nfs_storage_domain_4 > _add_storage_domain_4(api, p) > File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/002_bootstrap.py", line 407, in _add_storage_domain_4 > id=sd.id, > File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 3488, in add > self._check_fault(response) > File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 98, in _check_fault > Service._raise_error(response, fault) > File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 71, in _raise_error > raise Error(msg) > Error: Fault reason is "Operation Failed". Fault detail is "[Storage domain cannot be reached. Please ensure it is accessible from the host(s).]". HTTP response code is 400. > > Looking at http://jenkins.ovirt.org/view/experimental%20jobs/job/ test-repo_ovirt_experimental_4.1/889/artifact/exported- artifacts/basic-suit-4.1-el7/test_logs/basic-suite-4.1/ post-002_bootstrap.py/lago-basic-suite-4-1-host1/_var_log/vdsm/supervdsm.log : I don't see the return of the mount command: MainProcess|jsonrpc/3::DEBUG::2017-03-06 20:26:01,872::supervdsmServer: :93::SuperVdsm.ServerCallback::(wrapper) call mount with (u'192.168.201.2: /exports/nfs/iso', u'/rhev/data-center/mnt/192.168.201.2:_exports_nfs_iso') {'vfstype': 'nfs', 'mntOpts': 'soft,nosharecache,timeo=600,retrans=6,nfsvers=3', 'timeout': None, 'cgroup': None} MainProcess|jsonrpc/3::DEBUG::2017-03-06 20:26:01,872::commands::69::root::(execCmd) /usr/bin/taskset --cpu-list 0-1 /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600,retrans=6,nfsvers=3 192.168.201.2:/exports/nfs/iso /rhev/data-center/mnt/192.168.201.2:_exports_nfs_iso (cwd None) MainProcess|jsonrpc/4::DEBUG::2017-03-06 20:29:02,501::supervdsmServer: :93::SuperVdsm.ServerCallback::(wrapper) call hbaRescan with () {} MainProcess|jsonrpc/4::DEBUG::2017-03-06 20:29:02,501::commands::69::storage.HBA::(execCmd) /usr/bin/taskset --cpu-list 0-1 /usr/libexec/vdsm/fc-scan (cwd None) MainProcess|jsonrpc/4::DEBUG::2017-03-06 20:29:02,573::supervdsmServer: :100::SuperVdsm.ServerCallback::(wrapper) return hbaRescan with None ... (I don't know why we do all those hbaRescan, but that's unrelated) Where on host0 it does return: MainProcess|jsonrpc/5::DEBUG::2017-03-06 20:25:20,369::supervdsmServer::93::SuperVdsm.ServerCallback::(wrapper) call mount with (u'192.168.201.2:/exports/nfs/iso', u'/rhev/data-center/mnt/192.168.201.2:_exports_nfs_iso') {'vfstype': 'nfs', 'mntOpts': 'soft,nosharecache,timeo=600,retrans=6,nfsvers=3', 'timeout': None, 'cgroup': None} MainProcess|jsonrpc/5::DEBUG::2017-03-06 20:25:20,369::commands::69::root::(execCmd) /usr/bin/taskset --cpu-list 0-1 /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600,retrans=6,nfsvers=3 192.168.201.2:/exports/nfs/iso /rhev/data-center/mnt/192.168.201.2:_exports_nfs_iso (cwd None) MainProcess|jsonrpc/5::DEBUG::2017-03-06 20:25:20,504::supervdsmServer::100::SuperVdsm.ServerCallback::(wrapper) return mount with None On the storage server, both requests are seen: Mar 6 20:25:20 lago-basic-suite-4-1-engine rpc.mountd[4279]: authenticated mount request from 192.168.201.4:970 for /exports/nfs/iso (/exports/nfs/iso) Mar 6 20:26:01 lago-basic-suite-4-1-engine rpc.mountd[4279]: authenticated mount request from 192.168.201.3:948 for /exports/nfs/iso (/exports/nfs/iso) -- > > *Daniel Belenky* > > *RHV DevOps* > > *Red Hat Israel* > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

2 3

oVirt infra daily report - unstable production jobs - 255
by jenkins＠jenkins.phx.ovirt.org 11 Mar '17

11 Mar '17

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/255//artifact/exported-a… Cheers, Jenkins

1 0

oVirt infra daily report - unstable production jobs - 254
by jenkins＠jenkins.phx.ovirt.org 10 Mar '17

10 Mar '17

------=_Part_2_1955332907.1489186819044 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/254//artifact/exported-a… Cheers, Jenkins ------=_Part_2_1955332907.1489186819044 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 - 10/03/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-system-tests_master_check-patch-el7-x86_…">ovirt-system-tests_master_check-patch-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> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_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.  NOT STABLE YET </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_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_4.1_image-ng-system-tests/">ovirt_4.1_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/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_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/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</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/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</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/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</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/repos_master_check-closure_fc25_merged/">repos_master_check-closure_fc25_merged</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_2_1955332907.1489186819044--

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Pavel Zhukov (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] Pavel Zhukov updated OVIRT-1250: -------------------------------- Issue Type: Bug (was: Improvement) > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Pavel Zhukov (oVirt JIRA) 10 Mar '17

10 Mar '17

Pavel Zhukov created OVIRT-1250: ----------------------------------- Summary: Github PR builder plugin generates too many messages Key: OVIRT-1250 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Pavel Zhukov Assignee: infra Seems like GH PR builder plugin posts one message like: Can one of the admins verify this patch? Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1249) spamming in github pull requests by ...not sure what it is.
by Pavel Zhukov (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1249?page=com.atlassian.jira.… ] Pavel Zhukov reassigned OVIRT-1249: ----------------------------------- Assignee: Pavel Zhukov (was: infra) > spamming in github pull requests by ...not sure what it is. > ----------------------------------------------------------- > > Key: OVIRT-1249 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1249 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: Pavel Zhukov > > See https://github.com/oVirt/ovirt-web-ui/pull/98 > There's a series of comments: > @lago-bot lago-bot commented 2 days ago > Can one of the admins verify this patch? > - spamming is not useful > - i'm not clear what is it actually trying to say -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1249) spamming in github pull requests by ...not sure what it is.
by Pavel Zhukov (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1249?page=com.atlassian.jira.… ] Pavel Zhukov commented on OVIRT-1249: ------------------------------------- [~eedri] Can we create more "neutral" github bot like "Testbot/jenkinsbot" or something similar (without project name in the bot name) and share it between both projects? With adopting of default GH PR Builder messages to make them more clear for users. > spamming in github pull requests by ...not sure what it is. > ----------------------------------------------------------- > > Key: OVIRT-1249 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1249 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > See https://github.com/oVirt/ovirt-web-ui/pull/98 > There's a series of comments: > @lago-bot lago-bot commented 2 days ago > Can one of the admins verify this patch? > - spamming is not useful > - i'm not clear what is it actually trying to say -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1249) spamming in github pull requests by ...not sure what it is.
by Pavel Zhukov (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1249?page=com.atlassian.jira.… ] Pavel Zhukov commented on OVIRT-1249: ------------------------------------- Hi Michal, I completely agree with you. The reason is the sender (author) of the patch is not a member of the oVirt organization (whitelist). Lago-bot is used because of jenkins github pull request builder limitation and the fact we use single Jenkins instance for both ovirt and lago-project organization. See OVIRT-1239 for more details. > spamming in github pull requests by ...not sure what it is. > ----------------------------------------------------------- > > Key: OVIRT-1249 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1249 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > See https://github.com/oVirt/ovirt-web-ui/pull/98 > There's a series of comments: > @lago-bot lago-bot commented 2 days ago > Can one of the admins verify this patch? > - spamming is not useful > - i'm not clear what is it actually trying to say -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1249) spamming in github pull requests by ...not sure what it is.
by Michal Skrivanek (oVirt JIRA) 10 Mar '17

10 Mar '17

Michal Skrivanek created OVIRT-1249: --------------------------------------- Summary: spamming in github pull requests by ...not sure what it is. Key: OVIRT-1249 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1249 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra See https://github.com/oVirt/ovirt-web-ui/pull/98 There's a series of comments: @lago-bot lago-bot commented 2 days ago Can one of the admins verify this patch? - spamming is not useful - i'm not clear what is it actually trying to say -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1248 at 3/10/17 4:16 PM: -------------------------------------------------------------- [~jhernand(a)redhat.com] This is so we remember to fix what we saw today. was (Author: bkorren(a)redhat.com) [~jhernand(a)redhat.com] This is so we remember to fix what we say today. > Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist > -------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Summary: Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist (was: Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist) > Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist > -------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1248: ------------------------------------- [~jhernand(a)redhat.com] This is so we remember to fix what we say today. > Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist > ------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Description: Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. The SDK jobs set CI -1 instead. It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. We need to fix this unless OVIRT-1247 gets fixed sooner. was: Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. The SDK jobs set CI -1 instead. It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. We need to fix this unless OVIRT-1247 get fixed sooner. > Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist > ------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Description: Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. The SDK jobs set CI -1 instead. It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. We need to fix this unless OVIRT-1247 get fixed sooner. was: Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. The SDK jobs set CI -1 instead. It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. This is probably because the YAML of the SDK jobs is different from all other jobs, so they got overlooked when some if the whitelist changes were introduced. > Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist > ------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 get fixed sooner. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

Barak Korren created OVIRT-1248: ----------------------------------- Summary: Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist Key: OVIRT-1248 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Barak Korren Assignee: infra Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. The SDK jobs set CI -1 instead. It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. This is probably because the YAML of the SDK jobs is different from all other jobs, so they got overlooked when some if the whitelist changes were introduced. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1248: -------------------------------- Epic Link: OVIRT-400 > Make SDK Standard-CI jobs show "friedly" output when blocked by whitelist > ------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs, so they got overlooked when some if the whitelist changes were introduced. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0

[JIRA] (OVIRT-1247) Re-factor SDK standard-CI jobs to not be different from other jobs
by Barak Korren (oVirt JIRA) 10 Mar '17

10 Mar '17

Barak Korren created OVIRT-1247: ----------------------------------- Summary: Re-factor SDK standard-CI jobs to not be different from other jobs Key: OVIRT-1247 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1247 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Right now the SDK building jobs use specialized YAML. This makes them different from all other Standard-CI jobs. Need to find a way make them like all the rest. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

1 0