- Infra - oVirt List Archives

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #2903 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '17

28 Jun '17

------=_Part_96_1183555987.1498644245387 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/2903/ Build Name: 2903 ovirt-engine-api-model (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/78769 - title: [maven-release-plugin] prepare release 4.2.13 - project: ovirt-engine-api-model - branch: master - author: Juan Hernandez <juan.hernandez(a)redhat.com> ------=_Part_96_1183555987.1498644245387--

1 1

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #2902 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '17

28 Jun '17

------=_Part_98_352701053.1498644304141 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/2902/ Build Name: 2902 ovirt-engine-api-model (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/78770 - title: [maven-release-plugin] prepare for next development iteration - project: ovirt-engine-api-model - branch: master - author: Juan Hernandez <juan.hernandez(a)redhat.com> ------=_Part_98_352701053.1498644304141--

1 0

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

28 Jun '17

------=_Part_94_1253429974.1498644010136 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: 171 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #171 [Barak Korren] Filter builds sent to change queues by version [Barak Korren] Make change queue invoke OST basic suit [Barak Korren] Various UX improvements in change-queue jobs [Barak Korren] Add a job for direct deployments to 'tested' [Barak Korren] Use new job to update 'tested' from experimental [Barak Korren] Use new tested deploy job in timed builders [Eyal Edri] update build retention policy for big artifacts [Yuval Turgeman] Bump version to 4.1.3 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_94_1253429974.1498644010136--

1 0

[oVirt Jenkins] ovirt_4.1_he-system-tests - Build # 163 - Failure!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '17

28 Jun '17

------=_Part_78_789507950.1498617108009 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/163/ Build Number: 163 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #163 [Daniel Belenky] Exclude packages from ovirt-master.repo [Barak Korren] Filter builds sent to change queues by version [Barak Korren] Make change queue invoke OST basic suit [Barak Korren] Various UX improvements in change-queue jobs [Barak Korren] Add a job for direct deployments to 'tested' [Barak Korren] Use new job to update 'tested' from experimental [Barak Korren] Use new tested deploy job in timed builders [Eyal Edri] update build retention policy for big artifacts ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_78_789507950.1498617108009--

1 1

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #2898 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '17

28 Jun '17

------=_Part_86_1357356482.1498634547636 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/2898/ Build Name: 2898 ovirt-engine-api-model (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/78199 - title: Add ability to synchronize a direct lun - project: ovirt-engine-api-model - branch: master - author: Idan Shaby <ishaby(a)redhat.com> ------=_Part_86_1357356482.1498634547636--

1 0

[JIRA] (OVIRT-723) check/add support for python3 + dnf on standard CI
by Barak Korren (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-723?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-723: ------------------------------- Resolution: Fixed Status: Done (was: To Do) Closing as par Did's last comment. > check/add support for python3 + dnf on standard CI > -------------------------------------------------- > > Key: OVIRT-723 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > Patch [1] fails jenkins [2] like this: > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ INFO ] Stage: Environment packages setup > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ ERROR ] DNF Cannot queue package 'iproute': no package matched > 11:35:21 [ ERROR ] Failed to execute stage 'Environment packages > setup': no package matched > I suspected, based on the log, that something is broken about dnf > configuration, so pushed [3] and ran the job again [4] with [3] > cherry-picked, and it succeeded. I thought that's enough for a > verification, so asked to merge it, and it was merged. Later on, lago > tests started breaking [5] with: > 09:37:44 Error: nothing provides repoman >= 2.0.12 needed by > python-lago-ovirt-0.24.0-1.fc23.noarch > So [3] was reverted [6], Currently pending, but I expect it to be merged soon. > So we need a better solution. > While investigating this, Nadav partially understood the issue - we have, at > certain points in mock_runner, both /etc/yum.conf and /etc/yum/yum.conf. > Not sure why and whether we need both. > We tried also various variations on this patch in [7][8][9][10], none worked. > Probably better to fully support dnf instead of this hack, not sure > what this requires. > Thanks, > [1] https://gerrit.ovirt.org/59831 > [2] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/44/console > [3] https://gerrit.ovirt.org/63249 > [4] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/46/ > [5] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/conso… > [6] https://gerrit.ovirt.org/63405 > [7] https://gerrit.ovirt.org/63386 > [8] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/203 > [9] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/204/ > [10] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/ > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-723) check/add support for python3 + dnf on standard CI
by Yedidyah Bar David (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-723?page=com.atlassian.jira.p… ] Yedidyah Bar David commented on OVIRT-723: ------------------------------------------ On Tue, Jun 27, 2017 at 9:50 PM, Barak Korren (oVirt JIRA) < At the time it didn't work for me, see Description. At some point we reverted the relevant patches for other reasons. I now pushed again a variation [1] of the patch that then failed, and it now passes. So I guess it was fixed since then. Thanks. You can close this ticket. If we have problems once we decide to continue with the effort to support python3 (sadly not soon, it seems), I'll open other tickets as needed. [1] https://gerrit.ovirt.org/78760 -- Didi > check/add support for python3 + dnf on standard CI > -------------------------------------------------- > > Key: OVIRT-723 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > Patch [1] fails jenkins [2] like this: > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ INFO ] Stage: Environment packages setup > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ ERROR ] DNF Cannot queue package 'iproute': no package matched > 11:35:21 [ ERROR ] Failed to execute stage 'Environment packages > setup': no package matched > I suspected, based on the log, that something is broken about dnf > configuration, so pushed [3] and ran the job again [4] with [3] > cherry-picked, and it succeeded. I thought that's enough for a > verification, so asked to merge it, and it was merged. Later on, lago > tests started breaking [5] with: > 09:37:44 Error: nothing provides repoman >= 2.0.12 needed by > python-lago-ovirt-0.24.0-1.fc23.noarch > So [3] was reverted [6], Currently pending, but I expect it to be merged soon. > So we need a better solution. > While investigating this, Nadav partially understood the issue - we have, at > certain points in mock_runner, both /etc/yum.conf and /etc/yum/yum.conf. > Not sure why and whether we need both. > We tried also various variations on this patch in [7][8][9][10], none worked. > Probably better to fully support dnf instead of this hack, not sure > what this requires. > Thanks, > [1] https://gerrit.ovirt.org/59831 > [2] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/44/console > [3] https://gerrit.ovirt.org/63249 > [4] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/46/ > [5] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/conso… > [6] https://gerrit.ovirt.org/63405 > [7] https://gerrit.ovirt.org/63386 > [8] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/203 > [9] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/204/ > [10] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/ > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1410) Please update #ovirt motd with oVirt 4.1.2
by Marc Dequènes (Duck) (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1410?page=com.atlassian.jira.… ] Marc Dequènes (Duck) commented on OVIRT-1410: --------------------------------------------- So this is called ENTRYMSG and defined in CHANSERV. Here is the list of people whi can do that: bq. Channel masters: pmyers, mburns, apevec Asked Alan Pevec about it. > Please update #ovirt motd with oVirt 4.1.2 > ------------------------------------------ > > Key: OVIRT-1410 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1410 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Joining #ovirt channel gives: > *oVirt 4.1.0 is now available. Please register your nick to participate in > this channel.* > Please, update with oVirt 4.1.2. > -- > 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 JIRA (v1000.1092.0#100053)

1 0

[oVirt Jenkins] ovirt-release_master_build-artifacts-fc25-x86_64 - Build # 149 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_11_270144878.1498525976803 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fc25-x86_… Build: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fc25-x86_… Build Number: 149 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #149 [Sandro Bonazzola] el7: update qemu-kvm-ev gpg key url ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_11_270144878.1498525976803--

1 1

[oVirt Jenkins] ovirt-release_master_build-artifacts-fc26-x86_64 - Build # 36 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_8_1138139607.1498522929161 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: 36 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #36 [Sandro Bonazzola] el7: update qemu-kvm-ev gpg key url ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_8_1138139607.1498522929161--

1 1

[oVirt Jenkins] ovirt-release_master_build-artifacts-el7-x86_64 - Build # 427 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_4_1515219848.1498521855529 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_6… Build Number: 427 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #427 [Sandro Bonazzola] el7: update qemu-kvm-ev gpg key url ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_4_1515219848.1498521855529--

1 1

oVirt infra daily report - unstable production jobs - 366
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_66_482710562.1498604402635 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/366//artifact/exported-a… Cheers, Jenkins ------=_Part_66_482710562.1498604402635 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 - 27/06/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_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/test-repo_ovirt_experimental_4.1/">test-repo_ovirt_experimental_4.1</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_66_482710562.1498604402635--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7385 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

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

1 1

Change 78740,1 (ovirt-log-collector) failed system tests
by oVirt Jenkins 27 Jun '17

27 Jun '17

Change 78740,1 (ovirt-log-collector) 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/78740/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/954/

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7379 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

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

1 4

[JIRA] (OVIRT-723) check/add support for python3 + dnf on standard CI
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-723?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-723: ------------------------------------ We're using both DNF and Pytohn3 in the '{{check-patch.sh}}' of the Jenkins repo. So we know they work. Is there other requirement in this ticket besides just checking? > check/add support for python3 + dnf on standard CI > -------------------------------------------------- > > Key: OVIRT-723 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > Patch [1] fails jenkins [2] like this: > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ INFO ] Stage: Environment packages setup > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ ERROR ] DNF Cannot queue package 'iproute': no package matched > 11:35:21 [ ERROR ] Failed to execute stage 'Environment packages > setup': no package matched > I suspected, based on the log, that something is broken about dnf > configuration, so pushed [3] and ran the job again [4] with [3] > cherry-picked, and it succeeded. I thought that's enough for a > verification, so asked to merge it, and it was merged. Later on, lago > tests started breaking [5] with: > 09:37:44 Error: nothing provides repoman >= 2.0.12 needed by > python-lago-ovirt-0.24.0-1.fc23.noarch > So [3] was reverted [6], Currently pending, but I expect it to be merged soon. > So we need a better solution. > While investigating this, Nadav partially understood the issue - we have, at > certain points in mock_runner, both /etc/yum.conf and /etc/yum/yum.conf. > Not sure why and whether we need both. > We tried also various variations on this patch in [7][8][9][10], none worked. > Probably better to fully support dnf instead of this hack, not sure > what this requires. > Thanks, > [1] https://gerrit.ovirt.org/59831 > [2] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/44/console > [3] https://gerrit.ovirt.org/63249 > [4] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/46/ > [5] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/conso… > [6] https://gerrit.ovirt.org/63405 > [7] https://gerrit.ovirt.org/63386 > [8] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/203 > [9] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/204/ > [10] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/ > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1485?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1485: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Create a GitHub releases deployment token for ovirt-containers > -------------------------------------------------------------- > > Key: OVIRT-1485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Juan Hernández > Assignee: Daniel Belenky > Labels: containers > > The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: > Configure Travis CI to do GitHub releases > https://gerrit.ovirt.org/78732 > That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1485?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1485: -------------------------------- Labels: containers (was: ) > Create a GitHub releases deployment token for ovirt-containers > -------------------------------------------------------------- > > Key: OVIRT-1485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Juan Hernández > Assignee: infra > Labels: containers > > The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: > Configure Travis CI to do GitHub releases > https://gerrit.ovirt.org/78732 > That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1485?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1485: -------------------------------- Issue Type: New Feature (was: Task) > Create a GitHub releases deployment token for ovirt-containers > -------------------------------------------------------------- > > Key: OVIRT-1485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Juan Hernández > Assignee: infra > > The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: > Configure Travis CI to do GitHub releases > https://gerrit.ovirt.org/78732 > That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 28 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_593_1515763556.1497982382061 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1_build-artifacts-el7-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1_build-artifacts-el7-… Build Number: 28 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #28 [Gil Shinar] Added shubham dubey to jenkins whitelist [Tomas Jelinek] adding pkotas to CI whitelist [Sandro Bonazzola] ovirt-engine-sdk: disable fc26 ppc64le [Sandro Bonazzola] ioprocess: add fc26 support [Shirly Radco] ovirt-engine-metrics: add build-on-demand job [Yuval Turgeman] Revert "engine-appliance: build in selinux enforcing mode" ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_593_1515763556.1497982382061--

1 1

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Juan Hernández (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1485?page=com.atlassian.jira.… ] Juan Hernández commented on OVIRT-1485: --------------------------------------- /cc [~ybronhei(a)redhat.com] [~stirabos(a)redhat.com] [~oourfali(a)redhat.com] [~fdeutsch] > Create a GitHub releases deployment token for ovirt-containers > -------------------------------------------------------------- > > Key: OVIRT-1485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Juan Hernández > Assignee: infra > > The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: > Configure Travis CI to do GitHub releases > https://gerrit.ovirt.org/78732 > That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Juan Hernández (oVirt JIRA) 27 Jun '17

27 Jun '17

Juan Hernández created OVIRT-1485: ------------------------------------- Summary: Create a GitHub releases deployment token for ovirt-containers Key: OVIRT-1485 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 Project: oVirt - virtualization made easy Issue Type: Task Components: General Reporter: Juan Hernández Assignee: infra The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: Configure Travis CI to do GitHub releases https://gerrit.ovirt.org/78732 That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-723) check/add support for python3 + dnf on standard CI
by Yedidyah Bar David (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-723?page=com.atlassian.jira.p… ] Yedidyah Bar David commented on OVIRT-723: ------------------------------------------ On Tue, Jun 27, 2017 at 5:55 PM, eedri (oVirt JIRA) Can't see why not - we still want python3 support eventually. Didn't check recently about actual status, and this was postponed to oVirt 4.3. -- Didi > check/add support for python3 + dnf on standard CI > -------------------------------------------------- > > Key: OVIRT-723 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > Patch [1] fails jenkins [2] like this: > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ INFO ] Stage: Environment packages setup > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ ERROR ] DNF Cannot queue package 'iproute': no package matched > 11:35:21 [ ERROR ] Failed to execute stage 'Environment packages > setup': no package matched > I suspected, based on the log, that something is broken about dnf > configuration, so pushed [3] and ran the job again [4] with [3] > cherry-picked, and it succeeded. I thought that's enough for a > verification, so asked to merge it, and it was merged. Later on, lago > tests started breaking [5] with: > 09:37:44 Error: nothing provides repoman >= 2.0.12 needed by > python-lago-ovirt-0.24.0-1.fc23.noarch > So [3] was reverted [6], Currently pending, but I expect it to be merged soon. > So we need a better solution. > While investigating this, Nadav partially understood the issue - we have, at > certain points in mock_runner, both /etc/yum.conf and /etc/yum/yum.conf. > Not sure why and whether we need both. > We tried also various variations on this patch in [7][8][9][10], none worked. > Probably better to fully support dnf instead of this hack, not sure > what this requires. > Thanks, > [1] https://gerrit.ovirt.org/59831 > [2] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/44/console > [3] https://gerrit.ovirt.org/63249 > [4] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/46/ > [5] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/conso… > [6] https://gerrit.ovirt.org/63405 > [7] https://gerrit.ovirt.org/63386 > [8] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/203 > [9] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/204/ > [10] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/ > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-723) check/add support for python3 + dnf on standard CI
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-723?page=com.atlassian.jira.p… ] eedri commented on OVIRT-723: ----------------------------- [~didi(a)redhat.com] is this still relevant? > check/add support for python3 + dnf on standard CI > -------------------------------------------------- > > Key: OVIRT-723 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > Patch [1] fails jenkins [2] like this: > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ INFO ] Stage: Environment packages setup > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ ERROR ] DNF Cannot queue package 'iproute': no package matched > 11:35:21 [ ERROR ] Failed to execute stage 'Environment packages > setup': no package matched > I suspected, based on the log, that something is broken about dnf > configuration, so pushed [3] and ran the job again [4] with [3] > cherry-picked, and it succeeded. I thought that's enough for a > verification, so asked to merge it, and it was merged. Later on, lago > tests started breaking [5] with: > 09:37:44 Error: nothing provides repoman >= 2.0.12 needed by > python-lago-ovirt-0.24.0-1.fc23.noarch > So [3] was reverted [6], Currently pending, but I expect it to be merged soon. > So we need a better solution. > While investigating this, Nadav partially understood the issue - we have, at > certain points in mock_runner, both /etc/yum.conf and /etc/yum/yum.conf. > Not sure why and whether we need both. > We tried also various variations on this patch in [7][8][9][10], none worked. > Probably better to fully support dnf instead of this hack, not sure > what this requires. > Thanks, > [1] https://gerrit.ovirt.org/59831 > [2] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/44/console > [3] https://gerrit.ovirt.org/63249 > [4] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/46/ > [5] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/conso… > [6] https://gerrit.ovirt.org/63405 > [7] https://gerrit.ovirt.org/63386 > [8] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/203 > [9] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/204/ > [10] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/ > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

2 1

[JIRA] (OVIRT-768) Decomission of MD5 Password Hashes for Infra Users
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-768?page=com.atlassian.jira.p… ] eedri updated OVIRT-768: ------------------------ Issue Type: Improvement (was: By-EMAIL) > Decomission of MD5 Password Hashes for Infra Users > -------------------------------------------------- > > Key: OVIRT-768 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-768 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > During the work of moving password parameters from foreman to internal > hiera I noted that there are some users that still have their passwords > hashed by MD5 algorithm. > MD5 has known crypto research that make it no longer suitable for storing > passwords securely: > https://en.wikipedia.org/wiki/MD5#Security (and corresponding links). > While the hashes are stored in internal repo it is still shared and prone > to information leaks. We should ask all users to rehash their passwords > with SHA-512 and when it is done we can remove MD5 exception > in site/ovirt_infra/manifests/user.pp so MD5 hashed passwords are no > longer accepted. > The current list of users left is available in infra-hiera repo. > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-769) infra-hiera Autodeploy via Gerrit Hooks
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-769?page=com.atlassian.jira.p… ] eedri updated OVIRT-769: ------------------------ Issue Type: Improvement (was: By-EMAIL) > infra-hiera Autodeploy via Gerrit Hooks > --------------------------------------- > > Key: OVIRT-769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-769 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > infra-hiera repo is already used and configured in r10k to deploy from git. > However in gerrit there is not hooks that run CI on it and that trigger > publish when it is merged to git. > Looks like it is easy to fix and we can reuse most of the hooks we have for > infra-puppet. Basically the deploy should be done using the same jenkins > job and it already does that just not triggered. > As for CI check than we need to check if puppetlint we use is sufficient. > But it might be a good start. > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-978?page=com.atlassian.jira.p… ] eedri updated OVIRT-978: ------------------------ Issue Type: Improvement (was: By-EMAIL) > Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service > ---------------------------------------------------------------------------------------- > > Key: OVIRT-978 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: danken > Assignee: infra > > Occasionally, e.g. > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso… > I see these failures > 07:29:50 Manually triggered by user ishaby(a)redhat.com for Gerrit: > https://gerrit.ovirt.org/68804 > 07:29:50 [EnvInject] - Loading node environment variables. > 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx > local_disk nested) in workspace > /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64 > 07:29:50 > git rev-parse --is-inside-work-tree # timeout=10 > 07:29:50 Fetching changes from the remote Git repository > 07:29:50 > git config remote.origin.url > git://gerrit.ovirt.org/vdsm.git # timeout=10 > 07:29:50 Cleaning workspace > 07:29:50 > git rev-parse --verify HEAD # timeout=10 > 07:29:50 Resetting working tree > 07:29:50 > git reset --hard # timeout=10 > 07:29:51 > git clean -fdx # timeout=10 > 07:29:51 Pruning obsolete local branches > 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git > 07:29:51 > git --version # timeout=10 > 07:29:51 > git -c core.askpass=true fetch --tags --progress > git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune > 07:29:51 ERROR: Error fetching remote repo 'origin' > 07:29:51 hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/vdsm.git -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1128) Add Jenkins job for testing
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1128?page=com.atlassian.jira.… ] eedri updated OVIRT-1128: ------------------------- Issue Type: New Feature (was: By-EMAIL) > Add Jenkins job for testing > --------------------------- > > Key: OVIRT-1128 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1128 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Pavel Zhukov > Assignee: infra > Labels: staging > > it'd be good to have jenkins job to test and regenerate jenkins jobs :) > which uses "good" jjb configuration and available for infra team from > any machine. > Currently local JJB instances and configs are used which is not perfect > because configs can be different as well as jjb versions, not rebased > repos can be used for testing Besides of that it requires copying of > configs between machines and so on. > -- > Pavel -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jira.… ] eedri updated OVIRT-1156: ------------------------- Issue Type: Bug (was: By-EMAIL) > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1173) Please use git shallow clone as jobs default
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1173?page=com.atlassian.jira.… ] eedri updated OVIRT-1173: ------------------------- Issue Type: New Feature (was: By-EMAIL) > Please use git shallow clone as jobs default > -------------------------------------------- > > Key: OVIRT-1173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: rgolan(a)redhat.com > Assignee: infra > Labels: standard-ci > > Most if not all the git clone of the jobs don't need history at all. > For ovirt-engine I see it downloading *11Mb* using --depth 1 vs. *157Mb* > for regular clone. > R -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1198) Job times out on: 'Removing the used loop devices' on the initial clean up stage
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1198?page=com.atlassian.jira.… ] eedri commented on OVIRT-1198: ------------------------------ [~ngoldin(a)redhat.com] have you seen it again since? > Job times out on: 'Removing the used loop devices' on the initial clean up stage > -------------------------------------------------------------------------------- > > Key: OVIRT-1198 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1198 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: ngoldin(a)redhat.com > Assignee: infra > > 15:44:38 Making sure there are no device mappings... > 15:44:38 Removing the used loop devices... > 21:44:37 Build timed out (after 360 minutes). Marking the build as failed. > 21:44:37 Build was aborted > (Notice the 6 hours between). > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/710/con… > I think I saw another one earlier this week, also on fc25. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1226?page=com.atlassian.jira.… ] eedri updated OVIRT-1226: ------------------------- Resolution: Fixed Status: Done (was: Blocked) this should already be solved by moving find bugs code to check-patch.sh > https://gerrit.ovirt.org/#/c/73161 marked with CI-1 > --------------------------------------------------- > > Key: OVIRT-1226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1226 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yevgeny Zaspitsky > Assignee: infra > > Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful > CI runs it had. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1424) Re: Build timed out in Vdsm check-merged (was: False OST failure)
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1424?page=com.atlassian.jira.… ] eedri updated OVIRT-1424: ------------------------- Resolution: Duplicate Status: Done (was: To Do) ovirt-1442 > Re: Build timed out in Vdsm check-merged (was: False OST failure) > ----------------------------------------------------------------- > > Key: OVIRT-1424 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1424 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: infra > > adding infra-support to open a ticket. > On Thu, Jun 1, 2017 at 10:28 AM, Milan Zamazal <mzamazal(a)redhat.com> wrote: > > Another "Build timed out": > > > > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1870/ > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1477) Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1477?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1477: ---------------------------- Assignee: Barak Korren (was: infra) > Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own > --------------------------------------------------------------------------------------- > > Key: OVIRT-1477 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1477 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > Labels: repositories > > The 4.1 nightly publisher jobs are still using the old scheme of collecting packages directly from build-artifacts jobs instead of from 'tested'. We should move them to collect from 'tested' like the 'master' niightly publisher jobs. > As part of this work we should re-factor the YAML for the publisher jobs to make all of them use the same YAML job template instead of hard-coded job definitions. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eedri updated OVIRT-1479: ------------------------- Epic Link: OVIRT-403 (was: OVIRT-400) > 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.1089.0#100053)

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eedri updated OVIRT-1479: ------------------------- Epic Link: OVIRT-403 (was: OVIRT-400) > 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.1089.0#100053)

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eedri updated OVIRT-1479: ------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > 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.1089.0#100053)

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eedri updated OVIRT-1479: ------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > 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.1089.0#100053)

1 0

[JIRA] (OVIRT-1257) Setup mail delivery from Jenkins and slaves
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1257?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1257: ---------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Setup mail delivery from Jenkins and slaves > ------------------------------------------- > > Key: OVIRT-1257 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1257 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Marc Dequènes (Duck) > Priority: High > > I'm setting up some jobs that will require Jenkins and/or the slaves to send email to various places. Jenkins and the slaves seem to currently run Postfix in a default configuration that makes them attempt to deliver email directly to its destination. This causes sent email to get delayed. > We typically don't notice this because our SPF setting for ovirt.org are quite lax (We allow anyone to say he is from @ovirt.org, but delay messages that are not from "{{lists.phx.ovirt.org}}, "{{mail.phx.ovirt.org}}", or "{{gerrit.ovirt.org}}") abd because our ML server where we typically send to, only imposes a 60second delay. > We need to have a better setup. I suggest we configure Jenkins and the slaves to use some other server as a smart host (maybe "{{mail.phx.ovirt.org}}"?). To make the configuration as generic as possible I suggest we make the slaves deliver via Jenkins and only make Jenkins deliver to the smart host. > I think smart host configuration on Postfix is simple enough that we can make our usual job-embedded slave setup scrips set it up insead of having to resort to Puppet or Ansible. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1471) Add SSL to jenkins.ovirt.org
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1471?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1471: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Add SSL to jenkins.ovirt.org > ---------------------------- > > Key: OVIRT-1471 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1471 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > > We probably need SSL for '{{jenkins.ovirt.org}}'. That server has privileges on most stuff that is running in PHX, so better not have passwords to it be exposed to MITM attacks... -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1476) Infra-Ansible needs a CI
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1476?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1476: ----------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Infra-Ansible needs a CI > ------------------------ > > Key: OVIRT-1476 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1476 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, oVirt CI > Reporter: Marc Dequènes (Duck) > Assignee: Marc Dequènes (Duck) > Labels: ansible, standard-ci > > I have no knowledge of Gerrit administration and never touched the oVirt CI, and I would like avoiding breaking the universe, so I'm requesting help here :-). -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1477) Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1477?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1477: -------------------------------- Labels: repositories (was: ) > Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own > --------------------------------------------------------------------------------------- > > Key: OVIRT-1477 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1477 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: repositories > > The 4.1 nightly publisher jobs are still using the old scheme of collecting packages directly from build-artifacts jobs instead of from 'tested'. We should move them to collect from 'tested' like the 'master' niightly publisher jobs. > As part of this work we should re-factor the YAML for the publisher jobs to make all of them use the same YAML job template instead of hard-coded job definitions. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1061) Update http://monitoring.ovirt.org/ovirt.apps/
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1061?page=com.atlassian.jira.… ] eedri updated OVIRT-1061: ------------------------- Epic Link: OVIRT-403 > Update http://monitoring.ovirt.org/ovirt.apps/ > ---------------------------------------------- > > Key: OVIRT-1061 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1061 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please update http://monitoring.ovirt.org/ovirt.apps/ with all monitoring > and production services currently being used in oVirt infra. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1061) Update http://monitoring.ovirt.org/ovirt.apps/
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1061?page=com.atlassian.jira.… ] eedri updated OVIRT-1061: ------------------------- Epic Link: OVIRT-403 > Update http://monitoring.ovirt.org/ovirt.apps/ > ---------------------------------------------- > > Key: OVIRT-1061 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1061 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please update http://monitoring.ovirt.org/ovirt.apps/ with all monitoring > and production services currently being used in oVirt infra. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1420) Add timeout to Docker setup and cleanup operations
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1420?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1420: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Add timeout to Docker setup and cleanup operations > -------------------------------------------------- > > Key: OVIRT-1420 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1420 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Daniel Belenky > Priority: Highest > > It seems that some docker operation cat get stuck forever if some docker configuration stages fail. > We need to add time-outs for those operations and generate proper error messages. > for example failure see: > http://jenkins.ovirt.org/job/ovirt-release_4.1_build-artifacts-el7-x86_64/2… -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1275) Allow anonymous access to nagios dashboard
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1275?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1275: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Allow anonymous access to nagios dashboard > ------------------------------------------ > > Key: OVIRT-1275 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1275 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: Evgheni Dereveanchin > > Right now you need a password to just view the main page of monitoring.ovirt.org. > It will be better if you won't need to login just to view the status, that way anyone can look at current status w/o logging in and verify if there is an outage. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1410) Please update #ovirt motd with oVirt 4.1.2
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1410?page=com.atlassian.jira.… ] eedri updated OVIRT-1410: ------------------------- Epic Link: OVIRT-403 > Please update #ovirt motd with oVirt 4.1.2 > ------------------------------------------ > > Key: OVIRT-1410 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1410 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Joining #ovirt channel gives: > *oVirt 4.1.0 is now available. Please register your nick to participate in > this channel.* > Please, update with oVirt 4.1.2. > -- > 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 JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1410) Please update #ovirt motd with oVirt 4.1.2
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1410?page=com.atlassian.jira.… ] eedri updated OVIRT-1410: ------------------------- Epic Link: OVIRT-403 > Please update #ovirt motd with oVirt 4.1.2 > ------------------------------------------ > > Key: OVIRT-1410 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1410 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Joining #ovirt channel gives: > *oVirt 4.1.0 is now available. Please register your nick to participate in > this channel.* > Please, update with oVirt 4.1.2. > -- > 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 JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1410) Please update #ovirt motd with oVirt 4.1.2
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1410?page=com.atlassian.jira.… ] eedri commented on OVIRT-1410: ------------------------------ [~duck], [~misc(a)redhat.com] [~bproffit(a)redhat.com] do you know how we can update the irc channel motd w/o being a moderator on it? > Please update #ovirt motd with oVirt 4.1.2 > ------------------------------------------ > > Key: OVIRT-1410 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1410 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Joining #ovirt channel gives: > *oVirt 4.1.0 is now available. Please register your nick to participate in > this channel.* > Please, update with oVirt 4.1.2. > -- > 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 JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1424) Re: Build timed out in Vdsm check-merged (was: False OST failure)
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1424?page=com.atlassian.jira.… ] eedri updated OVIRT-1424: ------------------------- Epic Link: OVIRT-400 > Re: Build timed out in Vdsm check-merged (was: False OST failure) > ----------------------------------------------------------------- > > Key: OVIRT-1424 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1424 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: infra > > adding infra-support to open a ticket. > On Thu, Jun 1, 2017 at 10:28 AM, Milan Zamazal <mzamazal(a)redhat.com> wrote: > > Another "Build timed out": > > > > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1870/ > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0