- Infra - oVirt List Archives

[JIRA] (OVIRT-879) check if we can analayze oVirt RPM with whitesource
by eyal edri [Administrator] (oVirt JIRA) 29 Nov '16

29 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-879?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-879: -------------------------------------------- Epic Link: OVIRT-400 > check if we can analayze oVirt RPM with whitesource > --------------------------------------------------- > > Key: OVIRT-879 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-879 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > following ticket: https://whitesource.freshdesk.com/support/tickets/12091# > It might be possible to analyze licenses via the File system Agent: > Example: > We can support this use case by using the File System Agent (FSA) to unarchive all of the RPM files and then importing all specified file extensions (e.g. *.js, *.py, *.tgz, etc) that are contained within each RPM. These settings are specified in the configuration file for the File System Agent. It will probably be easier to explain if we schedule a call by phone, but here is an example of the FSA config file with archive extraction: > ############################################################################################# > # Includes/Excludes Glob patterns - PLEASE USE ONLY ONE EXCLUDE LINE AND ONE INCLUDE LINE > ############################################################################################# > includes=**/*.c **/*.cc **/*.cp**/*.cpp **/*.tgz **/*.c++ **/*.h **/*.py **/*.js > excludes=**/*sources.jar **/*javadoc.jar > case.sensitive.glob=false > followSymbolicLink=true > > ################# > # Archive Properties > ################# > archiveExtractionDepth=5 > archiveIncludes=**/*.rpm **/*.zip > ############################################################################################# -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-879) check if we can analayze oVirt RPM with whitesource
by eyal edri [Administrator] (oVirt JIRA) 29 Nov '16

29 Nov '16

eyal edri [Administrator] created OVIRT-879: ----------------------------------------------- Summary: check if we can analayze oVirt RPM with whitesource Key: OVIRT-879 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-879 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: eyal edri [Administrator] Assignee: infra following ticket: https://whitesource.freshdesk.com/support/tickets/12091# It might be possible to analyze licenses via the File system Agent: Example: We can support this use case by using the File System Agent (FSA) to unarchive all of the RPM files and then importing all specified file extensions (e.g. *.js, *.py, *.tgz, etc) that are contained within each RPM. These settings are specified in the configuration file for the File System Agent. It will probably be easier to explain if we schedule a call by phone, but here is an example of the FSA config file with archive extraction: ############################################################################################# # Includes/Excludes Glob patterns - PLEASE USE ONLY ONE EXCLUDE LINE AND ONE INCLUDE LINE ############################################################################################# includes=**/*.c **/*.cc **/*.cp**/*.cpp **/*.tgz **/*.c++ **/*.h **/*.py **/*.js excludes=**/*sources.jar **/*javadoc.jar case.sensitive.glob=false followSymbolicLink=true ################# # Archive Properties ################# archiveExtractionDepth=5 archiveIncludes=**/*.rpm **/*.zip ############################################################################################# -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-878) [gerrit hooks] add more checks to set_modified hook
by Shlomo Ben David (oVirt JIRA) 29 Nov '16

29 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-878?page=com.atlassian.jira.p… ] Shlomo Ben David updated OVIRT-878: ----------------------------------- Epic Link: OVIRT-411 > [gerrit hooks] add more checks to set_modified hook > ---------------------------------------------------- > > Key: OVIRT-878 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-878 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Shlomo Ben David > Assignee: infra > > set_modified hook is setting bug status to MODIFIED although there are open patches > We need to add more checks to test if there are still open patches (in the external tracker section) > If there are ==> don't change the bug status to MODIFIED -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-878) [gerrit hooks] add more checks to set_modified hook
by Shlomo Ben David (oVirt JIRA) 29 Nov '16

29 Nov '16

Shlomo Ben David created OVIRT-878: -------------------------------------- Summary: [gerrit hooks] add more checks to set_modified hook Key: OVIRT-878 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-878 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomo Ben David Assignee: infra set_modified hook is setting bug status to MODIFIED although there are open patches We need to add more checks to test if there are still open patches (in the external tracker section) If there are ==> don't change the bug status to MODIFIED -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-682) Improve CI logging - check if its possible to include mock errors in console output
by eyal edri [Administrator] (oVirt JIRA) 29 Nov '16

29 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-682: ------------------------------------------------- unfortunately I still see some jobs doing tar.gz on the logs, while others don't. So need to find where we have additional places doing this. > Improve CI logging - check if its possible to include mock errors in console output > ----------------------------------------------------------------------------------- > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-825) re: Assistance
by eyal edri [Administrator] (oVirt JIRA) 29 Nov '16

29 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-825?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-825: -------------------------------------------- Resolution: Won't Do Status: Done (was: Blocked) as discussed, please continue the discussion on users or devel lists of oVirt. If there is any issue with the oVirt infra, please feel free to open a ticket again. > re: Assistance > -------------- > > Key: OVIRT-825 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-825 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Billy Boulden > Assignee: infra > Attachments: image002.png > > > Hello, > Having issues installing and configuring OVIRT with the virtual switch. Need to speak with someone > Billy Boulden, C|EH, C|HFI > Systems Engineer > Information Systems Worldwide > A Wholly-Owned Subsidiary of ECS Federal. Inc. > 3865 Wilson Blvd, #600 > Arlington, VA 22203 > Phone: 571-482-4900 x6004 -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project
by eyal edri [Administrator] (oVirt JIRA) 29 Nov '16

29 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-612: -------------------------------------------- Resolution: Won't Do Status: Done (was: Blocked) > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4056 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 29 Nov '16

29 Nov '16

------=_Part_1026_1734711022.1480419236061 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4056/, Build Number: 4056, Build Status: SUCCESS ------=_Part_1026_1734711022.1480419236061--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4037 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Nov '16

29 Nov '16

------=_Part_1020_1550991880.1480371259595 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4037/, Build Number: 4037, Build Status: FAILURE ------=_Part_1020_1550991880.1480371259595--

1 1

oVirt infra daily report - unstable production jobs - 152
by jenkins＠jenkins.phx.ovirt.org 29 Nov '16

29 Nov '16

------=_Part_1022_1255132179.1480374008548 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/152//artifact/exported-a… Cheers, Jenkins ------=_Part_1022_1255132179.1480374008548 Content-Type: application/octet-stream; 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 - 28/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-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/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-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-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-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-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-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-engine_master_upgrade-from-3.6_el7_merge…">ovirt-engine_master_upgrade-from-3.6_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/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-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-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-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-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-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-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-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-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-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-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-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-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-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-provider-ovn_master_build-artifacts-el7-…">ovirt-provider-ovn_master_build-artifacts-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-provider-ovn_master_check-merged-el7-x86…">ovirt-provider-ovn_master_check-merged-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_master_system-tests_debug/">ovirt_master_system-tests_debug</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_fc24_merged/">repos_master_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/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</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/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_1022_1255132179.1480374008548--

1 0

Add ovirt-engine-4.0.6 branch to the list of stable branches
by Tal Nisan 28 Nov '16

28 Nov '16

Otherwise gerrit-hooks ignores it: (taken from gerrit.ovirt.org/67324) gerrit-hooks Nov 25 19:19 ↩ Patch Set 1: - Update Tracker::#1398550::IGNORE, not relevant for Red Hat classification - Check Bug-Url::IGNORE, not relevant for 'Red Hat' classification - Check Public Bug::#1398550::OK, public bug - Check Product::#1398550::IGNORE, not relevant for classification: Red Hat - Check TM::#1398550::IGNORE, not relevant for classification: Red Hat - Set POST::#1398550::IGNORE, not relevant for Red Hat classification - Check merged to previous::IGNORE, Not in stable branch (['ovirt-engine-3.6', 'ovirt-engine-4.0', 'ovirt-engine-3.6.9', 'ovirt-engine-4.0.2', 'ovirt-engine-4.0.4'])

3 2

Seems like every user can remove Gerrit-hooks vote on stable branch
by Tal Nisan 28 Nov '16

28 Nov '16

This is wrong, please revert it to how it was before when only stable branch maintainers could remove it

3 2

[JIRA] (OVIRT-877) [gerrit hooks] remove unused hooks
by Shlomo Ben David (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-877?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-877: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] remove unused hooks > ---------------------------------- > > Key: OVIRT-877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-877 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > > Remove all the unused hooks -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-877) [gerrit hooks] remove unused hooks
by Shlomo Ben David (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-877?page=com.atlassian.jira.p… ] Shlomo Ben David updated OVIRT-877: ----------------------------------- Epic Link: OVIRT-403 > [gerrit hooks] remove unused hooks > ---------------------------------- > > Key: OVIRT-877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-877 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: infra > > Remove all the unused hooks -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-877) [gerrit hooks] remove unused hooks
by Shlomo Ben David (oVirt JIRA) 28 Nov '16

28 Nov '16

Shlomo Ben David created OVIRT-877: -------------------------------------- Summary: [gerrit hooks] remove unused hooks Key: OVIRT-877 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-877 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Shlomo Ben David Assignee: infra Remove all the unused hooks -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-876) create check_backport hook
by Shlomo Ben David (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-876?page=com.atlassian.jira.p… ] Shlomo Ben David updated OVIRT-876: ----------------------------------- Issue Type: Task (was: Improvement) > create check_backport hook > -------------------------- > > Key: OVIRT-876 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-876 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: infra > > The new hook should replace the old > patchset-created.warn_if_not_merged_to_previous_branch > - It should check that the current patch has been backported to all newer branches > that are relevant for the patch. > - It should bypass the use of the configuration file params (STABLE_BRANCH) > -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-876) create check_backport hook
by Shlomo Ben David (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-876?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-876: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > create check_backport hook > -------------------------- > > Key: OVIRT-876 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-876 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > > The new hook should replace the old > patchset-created.warn_if_not_merged_to_previous_branch > - It should check that the current patch has been backported to all newer branches > that are relevant for the patch. > - It should bypass the use of the configuration file params (STABLE_BRANCH) > -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-876) create check_backport hook
by Shlomo Ben David (oVirt JIRA) 28 Nov '16

28 Nov '16

Shlomo Ben David created OVIRT-876: -------------------------------------- Summary: create check_backport hook Key: OVIRT-876 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-876 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Shlomo Ben David Assignee: infra The new hook should replace the old patchset-created.warn_if_not_merged_to_previous_branch - It should check that the current patch has been backported to all newer branches that are relevant for the patch. - It should bypass the use of the configuration file params (STABLE_BRANCH) -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-876) create check_backport hook
by Shlomo Ben David (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-876?page=com.atlassian.jira.p… ] Shlomo Ben David updated OVIRT-876: ----------------------------------- Epic Link: OVIRT-403 > create check_backport hook > -------------------------- > > Key: OVIRT-876 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-876 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Shlomo Ben David > Assignee: infra > > The new hook should replace the old > patchset-created.warn_if_not_merged_to_previous_branch > - It should check that the current patch has been backported to all newer branches > that are relevant for the patch. > - It should bypass the use of the configuration file params (STABLE_BRANCH) > -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-875) Build oVirt 4.0.6 RC3
by sbonazzo (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-875?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-875: --------------------------- Assignee: sbonazzo (was: infra) Status: In Progress (was: To Do) > Build oVirt 4.0.6 RC3 > --------------------- > > Key: OVIRT-875 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-875 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: sbonazzo > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-875) Build oVirt 4.0.6 RC3
by sbonazzo (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-875?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-875: --------------------------- Epic Link: OVIRT-411 > Build oVirt 4.0.6 RC3 > --------------------- > > Key: OVIRT-875 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-875 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-875) Build oVirt 4.0.6 RC3
by sbonazzo (oVirt JIRA) 28 Nov '16

28 Nov '16

sbonazzo created OVIRT-875: ------------------------------ Summary: Build oVirt 4.0.6 RC3 Key: OVIRT-875 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-875 Project: oVirt - virtualization made easy Issue Type: Task Components: Repositories Mgmt Reporter: sbonazzo Assignee: infra Priority: Highest -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

oVirt 4.0.6 RC3 merge / branch / tag / bugzilla reminder
by Sandro Bonazzola 28 Nov '16

28 Nov '16

All stable branch maintainers, please make sure to merge all relevant open bugs until Wednesday morning 11:00 AM TLV time (10:00 AM CET). For each package that need to be built (i.e oVirt product) please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.6, tr: 4.0.6) A list of bugs that require attention is here: https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!
by Evgheni Dereveanchin (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-867?page=com.atlassian.jira.p… ] Evgheni Dereveanchin commented on OVIRT-867: -------------------------------------------- I think this may bring unwanted overhead and eventually even more serious consistency issues than when using the mirrorlist from upstream providers. For now I'd go with a plain squid+mirrorlist (or predefined list of three fastest mirrors) defined for jobs that currently use repoproxy. > Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing! > ------------------------------------------------------------------------------------ > > Key: OVIRT-867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > *00:01:53.955* Can't download or revert repomd.xml for > check-epel-el7*00:01:53.955* Some dependencies may not be complete for > this repository*00:01:53.956* Run as root to get all dependencies or > use -t to enable a user temp cache > Can you check? looks like it's not possible to update local cache of metadata. > On Fri, Nov 25, 2016 at 1:07 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/ > > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/ > > Build Number: 92 > > Build Status: Still Failing > > Triggered By: Started by user Sandro Bonazzola > > > > ------------------------------------- > > Changes Since Last Success: > > ------------------------------------- > > Changes for Build #89 > > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well > > > > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead > > of snapshot > > > > > > Changes for Build #90 > > No changes > > > > Changes for Build #91 > > No changes > > > > Changes for Build #92 > > No changes > > > > > > > > ----------------- > > Failed Tests: > > ----------------- > > No tests ran. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/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.571.2#100021)

1 0

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-867?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-867: ------------------------------------------------- I guess our only way to avoid mirroring broken repos is to use Pulp or Katello? > Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing! > ------------------------------------------------------------------------------------ > > Key: OVIRT-867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > *00:01:53.955* Can't download or revert repomd.xml for > check-epel-el7*00:01:53.955* Some dependencies may not be complete for > this repository*00:01:53.956* Run as root to get all dependencies or > use -t to enable a user temp cache > Can you check? looks like it's not possible to update local cache of metadata. > On Fri, Nov 25, 2016 at 1:07 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/ > > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/ > > Build Number: 92 > > Build Status: Still Failing > > Triggered By: Started by user Sandro Bonazzola > > > > ------------------------------------- > > Changes Since Last Success: > > ------------------------------------- > > Changes for Build #89 > > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well > > > > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead > > of snapshot > > > > > > Changes for Build #90 > > No changes > > > > Changes for Build #91 > > No changes > > > > Changes for Build #92 > > No changes > > > > > > > > ----------------- > > Failed Tests: > > ----------------- > > No tests ran. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/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.571.2#100021)

1 0

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!
by Evgheni Dereveanchin (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-867?page=com.atlassian.jira.p… ] Evgheni Dereveanchin commented on OVIRT-867: -------------------------------------------- Eyal, this is a valid option, and even for the job in question we'd need to mirror the following repos: CENTOS_MIRROR="http://centos.mirror.constant.com/" EPEL_MIRROR="http://mirror.switch.ch/ftp/mirror" FEDORA_MIRROR="http://mirrors.kernel.org/" GLUSTER_MIRROR="http://download.gluster.org" JPACKAGE_MIRROR="http://vesta.informatik.rwth-aachen.de/ftp/pub/comp/Linux/" COPR="http://copr-be.cloud.fedoraproject.org/results" So it's at least CentOS, Fedora (2-3 releases), EPEL, Gluster and jpackage. We'd need to maange all of these and if upstream produces a corrupted repo this will still be mirrored. I think 1TB of disk should be enough for this (I managed a Fedora+CentOS+EPEL mirror without ISOs and that was usually enough). > Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing! > ------------------------------------------------------------------------------------ > > Key: OVIRT-867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > *00:01:53.955* Can't download or revert repomd.xml for > check-epel-el7*00:01:53.955* Some dependencies may not be complete for > this repository*00:01:53.956* Run as root to get all dependencies or > use -t to enable a user temp cache > Can you check? looks like it's not possible to update local cache of metadata. > On Fri, Nov 25, 2016 at 1:07 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/ > > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/ > > Build Number: 92 > > Build Status: Still Failing > > Triggered By: Started by user Sandro Bonazzola > > > > ------------------------------------- > > Changes Since Last Success: > > ------------------------------------- > > Changes for Build #89 > > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well > > > > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead > > of snapshot > > > > > > Changes for Build #90 > > No changes > > > > Changes for Build #91 > > No changes > > > > Changes for Build #92 > > No changes > > > > > > > > ----------------- > > Failed Tests: > > ----------------- > > No tests ran. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/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.571.2#100021)

1 0

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!
by Evgheni Dereveanchin (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-867?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-867: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing! > ------------------------------------------------------------------------------------ > > Key: OVIRT-867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > *00:01:53.955* Can't download or revert repomd.xml for > check-epel-el7*00:01:53.955* Some dependencies may not be complete for > this repository*00:01:53.956* Run as root to get all dependencies or > use -t to enable a user temp cache > Can you check? looks like it's not possible to update local cache of metadata. > On Fri, Nov 25, 2016 at 1:07 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/ > > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/ > > Build Number: 92 > > Build Status: Still Failing > > Triggered By: Started by user Sandro Bonazzola > > > > ------------------------------------- > > Changes Since Last Success: > > ------------------------------------- > > Changes for Build #89 > > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well > > > > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead > > of snapshot > > > > > > Changes for Build #90 > > No changes > > > > Changes for Build #91 > > No changes > > > > Changes for Build #92 > > No changes > > > > > > > > ----------------- > > Failed Tests: > > ----------------- > > No tests ran. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/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.571.2#100021)

1 0

Build failed in Jenkins: ovirt_3.6_he-system-tests #726
by jenkins＠jenkins.phx.ovirt.org 28 Nov '16

28 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/726/changes> Changes: [Eyal Edri] adding missing python-simplejson to epel repo ------------------------------------------ [...truncated 669 lines...] ## took 383 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 234 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=3.6 SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_3.6_he-system-tests] $ /bin/bash -xe /tmp/hudson4348854621409241755.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=3.6 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + OVIRT_SUITE=3.6 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/726/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/726/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/726/artifact/exporte…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then for log in "${logs[@]}" do echo "Copying ${log} to exported-artifacts" mv $log exported-artifacts/ done fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" # Drop all left over libvirt domains for UUID in $(virsh list --all --uuid); do virsh destroy $UUID || : sleep 2 virsh undefine --remove-all-storage --storage vda --snapshots-metadata $UUID || : done [ovirt_3.6_he-system-tests] $ /bin/bash -xe /tmp/hudson3096197047870703775.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + for log in '"${logs[@]}"' + echo 'Copying ./ovirt-system-tests/logs to exported-artifacts' Copying ./ovirt-system-tests/logs to exported-artifacts + mv ./ovirt-system-tests/logs exported-artifacts/ + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-epel-7-x86_64.el7.cfg + mock_root=mocker-epel-7-x86_64.el7 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-epel-7-x86_64.el7' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + mock_root=epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + [[ -n epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> ++ virsh list --all --uuid POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Archiving artifacts

3 5

Re: [JIRA] (OVIRT-874) Move github project to gerrit
by Eyal Edri 28 Nov '16

28 Nov '16

this might work for small or independent projects, not for something that is integrated with ovirt like user portal. we don't have Gerrit hooks for github and many of existing ci flows are available only for Gerrit. we can consider testing the github plugin for Gerrit to see if its possible to get pull requests into Gerrit from githib, but its not high priority for now and will need to wait for checking. On Nov 28, 2016 12:02, "eyal edri [Administrator] (oVirt JIRA)" < jira(a)ovirt-jira.atlassian.net> wrote: [ https://ovirt-jira.atlassian.net/browse/OVIRT-874?page=com. atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-874: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) Can you please help with this ? Lets make sure adding a new project has the new permisisons for all projects we have and its mirrored to GitHub > Move github project to gerrit > ----------------------------- > > Key: OVIRT-874 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-874 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Marek Libra > Assignee: Shlomo Ben David > > Hi, > please move following github project > https://github.com/mareklibra/userportal > to gerrit as 'ovirt-web-ui' project. > Please keep git history. > What is needed for automatic read-only syncing the gerrit back to the github? > Thanks, > Marek -- This message was sent by Atlassian JIRA (v1000.571.2#100021) _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

1 0

[JIRA] (OVIRT-874) Move github project to gerrit
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-874?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-874: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) Can you please help with this ? Lets make sure adding a new project has the new permisisons for all projects we have and its mirrored to GitHub > Move github project to gerrit > ----------------------------- > > Key: OVIRT-874 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-874 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Marek Libra > Assignee: Shlomo Ben David > > Hi, > please move following github project > https://github.com/mareklibra/userportal > to gerrit as 'ovirt-web-ui' project. > Please keep git history. > What is needed for automatic read-only syncing the gerrit back to the github? > Thanks, > Marek -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-874) Move github project to gerrit
by Marek Libra (oVirt JIRA) 28 Nov '16

28 Nov '16

Marek Libra created OVIRT-874: --------------------------------- Summary: Move github project to gerrit Key: OVIRT-874 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-874 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Marek Libra Assignee: infra Hi, please move following github project https://github.com/mareklibra/userportal to gerrit as 'ovirt-web-ui' project. Please keep git history. What is needed for automatic read-only syncing the gerrit back to the github? Thanks, Marek -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-758) Vdsm docker testing images
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-758?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-758: -------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) Status: In Progress (was: To Do) > Vdsm docker testing images > -------------------------- > > Key: OVIRT-758 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-758 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: eyal edri [Administrator] > > Hi all, > Vdsm includes now 2 Dockerfiles, building CentOS 7 and Fedora 24 images. > See https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:d… > Currently I maintain the images in docker hub: > - https://hub.docker.com/r/nirs/vdsm-centos/ > - https://hub.docker.com/r/nirs/vdsm-fedora/ > I configured automatic build, so each time I push a change to this branch: > https://github.com/nirs/vdsm/tree/dockerfile > Docker go and rebuilds the images. > We want to move the images to docker hub ovirt account: > https://hub.docker.com/u/ovirt/ > And configure vdsm github project so docker will rebuild > the images when we push a changes to the dockerfile branch, > or another solution to allow easy update of the images by > merging a new dockerfile. > Nir -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-758) Vdsm docker testing images
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-758?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-758: ------------------------------------------------- I created a new organization for oVirt under: https://hub.docker.com/u/ovirtinfra/ (ovirt wasn't available) please let me know which permissions do you need to create the VDSM images repos under it. > Vdsm docker testing images > -------------------------- > > Key: OVIRT-758 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-758 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Hi all, > Vdsm includes now 2 Dockerfiles, building CentOS 7 and Fedora 24 images. > See https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:d… > Currently I maintain the images in docker hub: > - https://hub.docker.com/r/nirs/vdsm-centos/ > - https://hub.docker.com/r/nirs/vdsm-fedora/ > I configured automatic build, so each time I push a change to this branch: > https://github.com/nirs/vdsm/tree/dockerfile > Docker go and rebuilds the images. > We want to move the images to docker hub ovirt account: > https://hub.docker.com/u/ovirt/ > And configure vdsm github project so docker will rebuild > the images when we push a changes to the dockerfile branch, > or another solution to allow easy update of the images by > merging a new dockerfile. > Nir -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-712) Use repoman extra sources feature in VDSM check merge
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-712?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-712: ----------------------------------------------- Assignee: Nadav Goldin (was: infra) Nadav, I think this is what you're doing now on the check-merged job right? > Use repoman extra sources feature in VDSM check merge > ------------------------------------------------------ > > Key: OVIRT-712 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-712 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: Nadav Goldin > > When running check merge, new rpms with the latest patch are being generated. > currently those repos are being copied by reposync to /var/lib/lago/reposync. > Those rpms shouldn't be saved to the cache, thus we need to use repoman to include those rpms in the internal repo. -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.pl… ] eyal edri [Administrator] commented on OVIRT-95: ------------------------------------------------ we'll implement this as part of #OVIRT-567, as second step for upgrading hypervisors after engine upgrade. > [jenkins] add job to run upgrade vdsm from version X to version Y > ----------------------------------------------------------------- > > Key: OVIRT-95 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Lowest > Labels: infra,vdsm,jenkins > > vdsm upgrade should be tested. (following on bug that was found). > suggested flow: > 1. install vdsm version X (e.g from 3.2) > 2. build latest vdsm version (3.3 or master) > 3. yum update vdsm > 4. check if service is up and running. -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.pl… ] eyal edri [Administrator] updated OVIRT-95: ------------------------------------------- Resolution: Duplicate Status: Done (was: To Do) > [jenkins] add job to run upgrade vdsm from version X to version Y > ----------------------------------------------------------------- > > Key: OVIRT-95 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Lowest > Labels: infra,vdsm,jenkins > > vdsm upgrade should be tested. (following on bug that was found). > suggested flow: > 1. install vdsm version X (e.g from 3.2) > 2. build latest vdsm version (3.3 or master) > 3. yum update vdsm > 4. check if service is up and running. -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-753?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-753: ------------------------------------------------- [~fdeutsch] this job is still not working, is it using the new experimental rpms? Anything infra team can help with? > ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands > ----------------------------------------------------------------------------- > > Key: OVIRT-753 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In: > http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… > After appliance shutdown: > *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~ > --in-place ]] && ( virt-sparsify --in-place > ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2 > ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify: > error: libguestfs error: guestfs_launch failed.*00:25:53.735* This > usually means the libguestfs appliance failed to start or > crashed.*00:25:53.735* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:25:53.735* bug report or message to the libguestfs mailing list. > The job should have failed here. Instead, the job continues and fails in a > later stage: > *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G > -rwxr-xr-x. 1 root root 1.4G Oct 6 14:13 > ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance > done*00:33:01.290* all appliance done*00:33:01.291* + make > check*00:33:01.299* make -f image-tools/build.mk > ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering > directory `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305* > guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort > -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs: > error: appliance closed the connection unexpectedly.*00:41:58.044* > This usually means the libguestfs appliance crashed.*00:41:58.044* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045* > for information about how to debug libguestfs and report > bugs.*00:41:58.045* libguestfs: error: guestfs_launch > failed.*00:41:58.045* This usually means the libguestfs appliance > failed to start or crashed.*00:41:58.045* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:41:58.046* bug report or message to the libguestfs mailing > list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm] > Error 1*00:41:58.059* make[1]: Leaving directory > `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060* > make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065* > Took 2325 seconds > wasting 20 minutes of jenkins slave time testing something already known > broken. > While working on fixing this job, please investigate while it's failing and > open a separate issue or bugzilla for it. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-869: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) First priority should be fixing the DNS errors we see, second is to reinstall the service as Squid as we talked before and stop using the custom python script we have now. > Investigate proxy errors from proxy.phx.ovirt.org > ------------------------------------------------- > > Key: OVIRT-869 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > Priority: Highest > > We need to make sure jobs don't fail on proxy like [1]. > Either use original repos if proxy is down or add watchdog / alerts for the proxy service. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artif… -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-848) Add support for building containers in oVirt CI
by Barak Korren (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-848?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-848: ------------------------------------ Some details and considerations about the interaction between containers (specifically Docker-based) and "Standard CI": There are two possible ways to use Docker from inside mock: # Install Docker inside the mock environment, and start up the Docker daemon inside it as well. # Install Docker on the slave VM (The host under mock), Docker client in the mock env, and bind-mount the docket socket ({{/var/run/docker.sock}}) into it. The obvious benefit of method #1 is that it does not require any adjustments to the existing CI infrastructure (We just need to teach devs how to implement it). I have doubts, however, that mock will not cause some difficulties with this (For example, are cgroups mounted inside mock?). We will need to test this and verify it works. Method #1 will also cause issues when we come around to implementing something like OVIRT-873 ([Nested Docker is possible but far from recommneded|https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/]) or do anything that causes us to run Docker on the hosts themselves. Method #2 will not have the same issues as method #1, but it will require us to distribute and maintain Docker on the slaves which is a step back to the pre-Standard-CI era. I think we should actually implement _both_ methods like this: # Try to mount the Docker socket into the mock env. # If it works use method #2 # If it doesn't, use method #1. This will require a little change to {{mock_runner.sh}} to allow bind mounts to be optional, but this change may provide other benefits so we may as well go for it. > Add support for building containers in oVirt CI > ----------------------------------------------- > > Key: OVIRT-848 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-848 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > more and more projects in oVirt are starting to build containers and using Docker files in their reops. > We need to start preparing oVirt CI to know how to handle containers and support containers the same way we support rpms today. > This will be a parent task with multiple sub-tasks that will follow, the following is a draft list of what we might need to do to add this support: > # Install Registry server ( maybe use openshift.ovirt.org ) > # Add for standard CI 'build-containers.sh' support > # Add verification steps for the build before publishing to registry > # Look at 3rd party OSS projects that might help and integrate with existing solutions -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-873) Implement Standard-CI with containers
by Nadav Goldin (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-873?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-873: ------------------------------------ +1 - I think containers support would be great, especially if we use openshift. Few issues that come to mind from my little experience with docker: 1. docker has limitation, for example: running systemd is almost impossible, also I doubt if you can run qemu inside docker, so this is not relevant for OST. 2. docker wants one process per container(as for the guidelines), I think we have jobs that need to do more than that. 3. docker images are not always one-to-one with the images we want to test on, i.e. can we claim that centos7:latest on docker hub is equivalent to centos7 we "support"? not sure. Moreover, this means we will need to start maintaining images, what we don't do now(in a way we maintain mock configurations which might be considered as maintaining Dockerfiles). either way, every solution we go with would probably need to be hybrid one(maintaining both flows). > Implement Standard-CI with containers > ------------------------------------- > > Key: OVIRT-873 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-873 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Barak Korren > Assignee: infra > > oVirt's Standard-CI is currently implemented using mock, and this has worked well for us so far. > Changing the implementation to use containers will provide several benefits: > * Faster start-up times - Most container provides have some form of image layering and caching that will be faster as bringing up a basic OS image then installing it with yum like mock does. > * Broader OS support - mock can only run on the Red Hat family of operating systems, and can only emulate those operating systems. Most container providers can both run on and emulate a broader range of operating systems. > * Better isolation and cleanup - Mock only isolates the file system, containers can isolate the file system as well as the networking layer and the process space. > Depending on the container provider, we may gain additional benefits: > * Some container providers like Kubernetes, can manage distributed compute resources across many nodes. This means can can stop managing Jenkins slaves and instead just have the Jenkins master start up containers on the provider. > * Some providers like OpenShift have built-in CI processes for creating and testing container images. > *Note:* At some point, David started an effort going this way: https://gerrit.ovirt.org/#/c/54376/ -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-873) Implement Standard-CI with containers
by eyal edri [Administrator] (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-873?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-873: ------------------------------------------------- I think its the right way going forward as version 2.0 of the standard CI. At some point we considered moving to stateless slaves instead mock , but I think this approach might prove to be better, because of the advantages of less maintenance of keeping various VMs with multiple operating systems + the overhead of ensuring the stateless mechanism works. Worth also looking into fabric8.io, it has integration with Kubernetes & OpenShift already. more info @ https://fabric8.io/articles/index.html > Implement Standard-CI with containers > ------------------------------------- > > Key: OVIRT-873 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-873 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Barak Korren > Assignee: infra > > oVirt's Standard-CI is currently implemented using mock, and this has worked well for us so far. > Changing the implementation to use containers will provide several benefits: > * Faster start-up times - Most container provides have some form of image layering and caching that will be faster as bringing up a basic OS image then installing it with yum like mock does. > * Broader OS support - mock can only run on the Red Hat family of operating systems, and can only emulate those operating systems. Most container providers can both run on and emulate a broader range of operating systems. > * Better isolation and cleanup - Mock only isolates the file system, containers can isolate the file system as well as the networking layer and the process space. > Depending on the container provider, we may gain additional benefits: > * Some container providers like Kubernetes, can manage distributed compute resources across many nodes. This means can can stop managing Jenkins slaves and instead just have the Jenkins master start up containers on the provider. > * Some providers like OpenShift have built-in CI processes for creating and testing container images. > *Note:* At some point, David started an effort going this way: https://gerrit.ovirt.org/#/c/54376/ -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-873) Implement Standard-CI with containers
by Barak Korren (oVirt JIRA) 28 Nov '16

28 Nov '16

Barak Korren created OVIRT-873: ---------------------------------- Summary: Implement Standard-CI with containers Key: OVIRT-873 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-873 Project: oVirt - virtualization made easy Issue Type: Task Components: General Reporter: Barak Korren Assignee: infra oVirt's Standard-CI is currently implemented using mock, and this has worked well for us so far. Changing the implementation to use containers will provide several benefits: * Faster start-up times - Most container provides have some form of image layering and caching that will be faster as bringing up a basic OS image then installing it with yum like mock does. * Broader OS support - mock can only run on the Red Hat family of operating systems, and can only emulate those operating systems. Most container providers can both run on and emulate a broader range of operating systems. * Better isolation and cleanup - Mock only isolates the file system, containers can isolate the file system as well as the networking layer and the process space. Depending on the container provider, we may gain additional benefits: * Some container providers like Kubernetes, can manage distributed compute resources across many nodes. This means can can stop managing Jenkins slaves and instead just have the Jenkins master start up containers on the provider. * Some providers like OpenShift have built-in CI processes for creating and testing container images. *Note:* At some point, David started an effort going this way: https://gerrit.ovirt.org/#/c/54376/ -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-873) Implement Standard-CI with containers
by Barak Korren (oVirt JIRA) 28 Nov '16

28 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-873?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-873: ------------------------------- Epic Link: OVIRT-403 > Implement Standard-CI with containers > ------------------------------------- > > Key: OVIRT-873 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-873 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Barak Korren > Assignee: infra > > oVirt's Standard-CI is currently implemented using mock, and this has worked well for us so far. > Changing the implementation to use containers will provide several benefits: > * Faster start-up times - Most container provides have some form of image layering and caching that will be faster as bringing up a basic OS image then installing it with yum like mock does. > * Broader OS support - mock can only run on the Red Hat family of operating systems, and can only emulate those operating systems. Most container providers can both run on and emulate a broader range of operating systems. > * Better isolation and cleanup - Mock only isolates the file system, containers can isolate the file system as well as the networking layer and the process space. > Depending on the container provider, we may gain additional benefits: > * Some container providers like Kubernetes, can manage distributed compute resources across many nodes. This means can can stop managing Jenkins slaves and instead just have the Jenkins master start up containers on the provider. > * Some providers like OpenShift have built-in CI processes for creating and testing container images. > *Note:* At some point, David started an effort going this way: https://gerrit.ovirt.org/#/c/54376/ -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3717 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 Nov '16

28 Nov '16

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

1 1

oVirt infra daily report - unstable production jobs - 151
by jenkins＠jenkins.phx.ovirt.org 28 Nov '16

28 Nov '16

------=_Part_1014_2136723980.1480287606307 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/151//artifact/exported-a… Cheers, Jenkins ------=_Part_1014_2136723980.1480287606307 Content-Type: application/octet-stream; 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/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-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/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-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-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-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-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-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-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-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-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-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-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-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-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-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-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-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-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-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-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-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-provider-ovn_master_build-artifacts-el7-…">ovirt-provider-ovn_master_build-artifacts-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-provider-ovn_master_check-merged-el7-x86…">ovirt-provider-ovn_master_check-merged-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_master_system-tests_debug/">ovirt_master_system-tests_debug</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_fc24_merged/">repos_master_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/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_1014_2136723980.1480287606307--

1 0

Re: [ovirt-devel] Gerrit headers are not added to commits in vdsm repo
by Nir Soffer 27 Nov '16

27 Nov '16

On Fri, Nov 25, 2016 at 4:45 PM, Tomáš Golembiovský <tgolembi(a)redhat.com> wrote: > Hi, > > I've noticed that in vdsm repo the merged commits do not contain the > info headers added by Gerrit any more (Reviewed-by/Reviewed-on/etc.). > > Is that intentional? If yes, what was the motivation behind this? > > The change seem to have happened about 4 days ago. Sometime between the > following two commits: > > * 505f5da API: Introduce getQemuImageInfo API. [Maor Lipchuk] > * 1c4a39c protocoldetector: Avoid unneeded getpeername() [Nir Soffer] We switched vdsm to fast-forward 4 days ago, maybe this was unintended side effect of this change? The gerrit headers are very useful, please add back. Nir

4 6

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org
by Gil Shinar (oVirt JIRA) 27 Nov '16

27 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-869?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-869: ---------------------------------- In the log I'm seeing the following error messages: *ConnectionError: HTTPConnectionPool(host='ftp.linux.ncsu.edu', port=80): Max retries exceeded with url: /pub/fedora/linux/updates/23/x86_64/// (Caused by <class 'socket.error'>: [Errno 110] Connection timed out) ConnectionError: HTTPConnectionPool(host='mirror.evolvedservers.com', port=80): Max retries exceeded with url: /CentOS/7.1.1503/os/x86_64//repodata/repomd.xml (Caused by <class 'socket.error'>: [Errno 113] No route to host)* and *ConnectionError: HTTPConnectionPool(host='mirror.evolvedservers.com', port=80): Max retries exceeded with url: /CentOS/7.1.1503/os/x86_64//repodata/repomd.xml (Caused by <class 'socket.error'>: [Errno 101] Network is unreachable)* This one as well: *ConnectionError: HTTPConnectionPool(host='mirror.symnds.com', port=80): Max retries exceeded with url: /CentOS/7.2.1511/os/x86_64//repodata/repomd.xml (Caused by <class 'httplib.BadStatusLine'>: '')* After restart looks like they have gone but we need to find the core of the problem > Investigate proxy errors from proxy.phx.ovirt.org > ------------------------------------------------- > > Key: OVIRT-869 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need to make sure jobs don't fail on proxy like [1]. > Either use original repos if proxy is down or add watchdog / alerts for the proxy service. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artif… -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-871) unrelated CI failure
by Gil Shinar (oVirt JIRA) 27 Nov '16

27 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-871?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-871: ---------------------------------- We had an Artifactory issue. Now looks like it is back to normal > unrelated CI failure > -------------------- > > Key: OVIRT-871 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-871 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Change https://gerrit.ovirt.org/#/c/67101/ just failed on > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/80… > which I believe is utterly unrelated to the patch. please resolved the underlying problem. > [ERROR] Failed to execute goal on project restapi-definition: Could not resolve dependencies for project org.ovirt.engine.api:restapi-definition:jar:4.1.0-SNAPSHOT: Failed to collect dependencies at org.ovirt.engine.api:metamodel-runtime:jar:1.1.8: Failed to read artifact descriptor for org.ovirt.engine.api:metamodel-runtime:jar:1.1.8: Could not transfer artifact org.ovirt.engine.api:metamodel-runtime:pom:1.1.8 from/to ovirt-maven-repository (http://artifactory.ovirt.org/artifactory/ovirt-mirror) Failed to transfer file: http://artifactory.ovirt.org/artifactory/ovirt-mirror/org/ovirt/engine/api/…. Return code is: 502 , ReasonPhrase:Proxy Error. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExcept… > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :restapi-definition > Makefile:256: recipe for target 'maven' failed > make[1]: *** [maven] Error 1 > make[1]: Leaving directory '/home/jenkins/workspace/ovirt-engine_master_check-patch-fc24-x86_64/ovirt-engine/rpmbuild/BUILD/ovirt-engine-4.1.0' > Makefile:263: recipe for target 'tmp.built' failed > make: *** [tmp.built] Error 2 > error: Bad exit status from /var/tmp/rpm-tmp.2ykGhi (%build) -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-872) Re: [ovirt-devel] Gerrit headers are not added to commits in vdsm repo
by Barak Korren (oVirt JIRA) 27 Nov '16

27 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-872?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-872: ------------------------------- Resolution: Won't Fix Status: Done (was: To Do) This has to do with the maintainers` chosen working mode for the Gerrit repo - as I replied in the mailing thread. The maintainers need to the decide if they want to change it, and understand the consequences. > Re: [ovirt-devel] Gerrit headers are not added to commits in vdsm repo > ---------------------------------------------------------------------- > > Key: OVIRT-872 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-872 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > I don't see any options to control this from project config, it will > require more investigating to see if its a config option or only available > via cherry-pick. > opening a ticket to track this. > On Sun, Nov 27, 2016 at 1:38 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > > On Sun, Nov 27, 2016 at 12:31:21PM +0200, Eyal Edri wrote: > > > Not sure I understand what do you mean by Gerrit Headers. > > > Can you give examples? > > > > > > On Fri, Nov 25, 2016 at 4:57 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > > > > > > On Fri, Nov 25, 2016 at 4:45 PM, Tomáš Golembiovský < > > tgolembi(a)redhat.com> > > > > wrote: > > > > > Hi, > > > > > > > > > > I've noticed that in vdsm repo the merged commits do not contain the > > > > > info headers added by Gerrit any more (Reviewed-by/Reviewed-on/etc.) > > . > > > > > > > > > > Is that intentional? If yes, what was the motivation behind this? > > > > > > > > > > The change seem to have happened about 4 days ago. Sometime between > > the > > > > > following two commits: > > > > > > > > > > * 505f5da API: Introduce getQemuImageInfo API. [Maor Lipchuk] > > > > > * 1c4a39c protocoldetector: Avoid unneeded getpeername() [Nir > > Soffer] > > > > > > > > We switched vdsm to fast-forward 4 days ago, maybe this was unintended > > > > side effect of this change? > > > > > > > > The gerrit headers are very useful, please add back. > > > > > > https://gerrit.ovirt.org/#/c/66295/ is the last one which had them: > > > > Reviewed-on: https://gerrit.ovirt.org/66295 > > Reviewed-by: Nir Soffer <nsoffer(a)redhat.com> > > Continuous-Integration: Jenkins CI > > > > they are added to the commit message during cherry-pick, and I find them > > very useful. > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0

[JIRA] (OVIRT-872) Re: [ovirt-devel] Gerrit headers are not added to commits in vdsm repo
by eyal edri [Administrator] (oVirt JIRA) 27 Nov '16

27 Nov '16

eyal edri [Administrator] created OVIRT-872: ----------------------------------------------- Summary: Re: [ovirt-devel] Gerrit headers are not added to commits in vdsm repo Key: OVIRT-872 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-872 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra I don't see any options to control this from project config, it will require more investigating to see if its a config option or only available via cherry-pick. opening a ticket to track this. On Sun, Nov 27, 2016 at 1:38 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > On Sun, Nov 27, 2016 at 12:31:21PM +0200, Eyal Edri wrote: > > Not sure I understand what do you mean by Gerrit Headers. > > Can you give examples? > > > > On Fri, Nov 25, 2016 at 4:57 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > > > > On Fri, Nov 25, 2016 at 4:45 PM, Tomáš Golembiovský < > tgolembi(a)redhat.com> > > > wrote: > > > > Hi, > > > > > > > > I've noticed that in vdsm repo the merged commits do not contain the > > > > info headers added by Gerrit any more (Reviewed-by/Reviewed-on/etc.) > . > > > > > > > > Is that intentional? If yes, what was the motivation behind this? > > > > > > > > The change seem to have happened about 4 days ago. Sometime between > the > > > > following two commits: > > > > > > > > * 505f5da API: Introduce getQemuImageInfo API. [Maor Lipchuk] > > > > * 1c4a39c protocoldetector: Avoid unneeded getpeername() [Nir > Soffer] > > > > > > We switched vdsm to fast-forward 4 days ago, maybe this was unintended > > > side effect of this change? > > > > > > The gerrit headers are very useful, please add back. > > > https://gerrit.ovirt.org/#/c/66295/ is the last one which had them: > > Reviewed-on: https://gerrit.ovirt.org/66295 > Reviewed-by: Nir Soffer <nsoffer(a)redhat.com> > Continuous-Integration: Jenkins CI > > they are added to the commit message during cherry-pick, and I find them > very useful. > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.571.2#100021)

1 0