- Infra - oVirt List Archives

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

24 Nov '16

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

1 31

Re: Change in jenkins[master]: master_upgrade_from_master: Upgrade to self instead of snapshot
by Yedidyah Bar David 24 Nov '16

24 Nov '16

On Thu, Nov 24, 2016 at 1:13 PM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI: > > Jenkins CI has posted comments on this change. > > Change subject: master_upgrade_from_master: Upgrade to self instead of snapshot > ...................................................................... > > > Patch Set 1: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/5/ : FAILURE 11:08:53 Unable to find mock env fc25.*x86_64 use one of el6:epel-6-x86_64 el7:epel-7-x86_64 el7:epel-7-ppc64le fc23:fedora-23-x86_64 fc24:fedora-24-x86_64 fc24:fedora-24-ppc64le 11:08:53 Build step 'Execute shell' marked build as failure Any idea? > > http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/120/ : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/67263 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: I63e09056cabd420b93be059183fcc5b22c2ae0e0 > Gerrit-PatchSet: 1 > Gerrit-Project: jenkins > Gerrit-Branch: master > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Martin Peřina <mperina(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No -- Didi

3 2

[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
by eyal edri [Administrator] (oVirt JIRA) 24 Nov '16

24 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-416: -------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) Status: In Progress (was: To Do) > [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any > ------------------------------------------------------------------------------------- > > Key: OVIRT-416 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: eyal edri [Administrator] > > Right now most projects just rebuild twice the artifacts, what for some means a big waste of resources, if we could just reuse what was built previously there would be no rebuilding. > Something to take into account is that the distributions that check-merged and build-artifacts run for might not match, so you can be running check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an example), maybe we should not allow different distros on each stage?| -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

master deps broken for el7
by Sandro Bonazzola 24 Nov '16

24 Nov '16

Hi, FYI, jenkins detected broken dependencies issues withing vdsm package. It seems that some package are missing so I'm rebuilding the repository. Some failures may happen in the next 45 minutes. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[JIRA] (OVIRT-864) Shipment delivery problem #00000870089
by Anonymous (oVirt JIRA) 24 Nov '16

24 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-864?page=com.atlassian.jira.p… ] Anonymous commented on OVIRT-864: --------------------------------- An error occurred while adding attachments to this issue from the source email. Please check the attachments and re-send the email. > Shipment delivery problem #00000870089 > -------------------------------------- > > Key: OVIRT-864 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-864 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: FedEx 2Day A.M. > Assignee: infra > > Dear Customer, > Courier was unable to deliver the parcel to you. > Please, open email attachment to print shipment label. > Regards, > Andy Mccormick, > Support Manager. -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

[JIRA] (OVIRT-864) Shipment delivery problem #00000870089
by FedEx 2Day A.M. (oVirt JIRA) 24 Nov '16

24 Nov '16

FedEx 2Day A.M. created OVIRT-864: ------------------------------------- Summary: Shipment delivery problem #00000870089 Key: OVIRT-864 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-864 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: FedEx 2Day A.M. Assignee: infra Dear Customer, Courier was unable to deliver the parcel to you. Please, open email attachment to print shipment label. Regards, Andy Mccormick, Support Manager. -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

[JIRA] (OVIRT-863) Delivery Notification, ID 1285359132561
by FedEx Standard Overnight (oVirt JIRA) 24 Nov '16

24 Nov '16

FedEx Standard Overnight created OVIRT-863: ---------------------------------------------- Summary: Delivery Notification, ID 1285359132561 Key: OVIRT-863 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-863 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: FedEx Standard Overnight Assignee: infra Attachments: FedEx.doc Hello, We could not deliver your parcel. You can review complete details of your order in the find attached. Letizia Nenninger - Area Manager FedEx , CA Sincerely. -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

[ ERROR ] schema.sh: Please fix numbering to interval 04010491 to 04010500 and run the upgrade script.
by Sandro Bonazzola 24 Nov '16

24 Nov '16

engine master CI is failing on $subject, please fix or revert as soon as possible, thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

7 13

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

24 Nov '16

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

1 0

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

24 Nov '16

------=_Part_843_897633339.1479942009563 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/147//artifact/exported-a… Cheers, Jenkins ------=_Part_843_897633339.1479942009563 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 - 23/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_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-engine_master_upgrade-from-master_el7_me…">ovirt-engine_master_upgrade-from-master_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_build-artifacts-fc24…">ovirt-provider-ovn_master_build-artifacts-fc24-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/">ovirt_master_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_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/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repoman_master_check-merged-el7-x86_64/">repoman_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/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/system_update_puppet/">system_update_puppet</a> </td><td> No Description </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</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_843_897633339.1479942009563--

1 0

[JIRA] (OVIRT-862) Please give Denis Chalygin the usual developer permissions
by eyal edri [Administrator] (oVirt JIRA) 23 Nov '16

23 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-862?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-862: ------------------------------------------------- jenkins user updated. gerrit doesn't need any special configuration, any registered user has all the permissions needed to submit a patch > Please give Denis Chalygin the usual developer permissions > ---------------------------------------------------------- > > Key: OVIRT-862 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-862 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Sivak > Assignee: infra > > We need the usual permissions for Gerrit and Jenkins. His email is > dchaplyg. > -- > Martin Sivak > SLA / oVirt -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

[JIRA] (OVIRT-862) Please give Denis Chalygin the usual developer permissions
by eyal edri [Administrator] (oVirt JIRA) 23 Nov '16

23 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-862?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-862: -------------------------------------------- Description: We need the usual permissions for Gerrit and Jenkins. His email is dchaplyg. -- Martin Sivak SLA / oVirt was: We need the usual permissions for Gerrit and Jenkins. His email is dchaplyg. He is a new RH employee under Doron. -- Martin Sivak SLA / oVirt > Please give Denis Chalygin the usual developer permissions > ---------------------------------------------------------- > > Key: OVIRT-862 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-862 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Sivak > Assignee: infra > > We need the usual permissions for Gerrit and Jenkins. His email is > dchaplyg. > -- > Martin Sivak > SLA / oVirt -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

[JIRA] (OVIRT-862) Please give Denis Chalygin the usual developer permissions
by Martin Sivak (oVirt JIRA) 23 Nov '16

23 Nov '16

Martin Sivak created OVIRT-862: ---------------------------------- Summary: Please give Denis Chalygin the usual developer permissions Key: OVIRT-862 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-862 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Martin Sivak Assignee: infra We need the usual permissions for Gerrit and Jenkins. His email is dchaplyg. He is a new RH employee under Doron. -- Martin Sivak SLA / oVirt -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

CI ovirt-engine_master_upgrade-from-master_el7_created failing spontaniously
by Maor Lipchuk 23 Nov '16

23 Nov '16

Hi all, I'm not sure if this is a known issue but it seems that ovirt-engine_master_upgrade-from-master_el7_created is failing almost all the time. I also see other patches than mine that fail on it. Is there anything I can help with to make it fixed Thanks, Maor

2 2

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

23 Nov '16

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

1 35

Restoring ovirt-release-master rpm
by Sandro Bonazzola 23 Nov '16

23 Nov '16

Looks like someone deleted ovirt-release-master rpm from http://resources.ovirt.org/pub/yum-repo/ breaking several stuff including website documentation. I'm restoring it, please avoid removing rpms without discussing it. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

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

23 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/718/changes> Changes: [Aleksei Slaikovkii] Fixed link to installation script in documentation. ------------------------------------------ [...truncated 1415 lines...] ## Wed Nov 23 08:44:37 UTC 2016 Finished env: el7:epel-7-x86_64 ## took 3147 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 3001 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/hudson3087457139323256851.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/718/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/718/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/ws/ovirt-system-test…> <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/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/718/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/hudson5140279264763435422.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 Archiving artifacts

1 1

Build failed in Jenkins: ovirt_master_system-tests #825
by jenkins＠jenkins.phx.ovirt.org 23 Nov '16

23 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_master_system-tests/825/changes> Changes: [Aleksei Slaikovkii] Fixed link to installation script in documentation. ------------------------------------------ [...truncated 743 lines...] ## Wed Nov 23 08:00:42 UTC 2016 Finished env: el7:epel-7-x86_64 ## took 1772 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.basic_suite_master.sh/basic_suite_master.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_master_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 1624 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=master 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_master_system-tests] $ /bin/bash -xe /tmp/hudson4250281846607287772.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=master + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> + OVIRT_SUITE=master + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_master_system-tests/825/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_master_system-tests/825/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/825/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_master_system-tests] $ /bin/bash -xe /tmp/hudson6756566173867007386.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_master_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_master_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_master_system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-epel-7-x86_64.el7' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_master_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_master_system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_master_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_master_system-tests/ws/ovirt-system-test…> + mock_root=epel-7-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + [[ -n epel-7-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/epel-7-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> ++ virsh list --all --uuid POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 1

[JIRA] (OVIRT-861) Upload Fedora 25 images to Glance
by Barak Korren (oVirt JIRA) 23 Nov '16

23 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-861?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-861: ---------------------------------- Assignee: Barak Korren (was: infra) > Upload Fedora 25 images to Glance > --------------------------------- > > Key: OVIRT-861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-861 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > FC25 was released, we should have the images available in oVirt. -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

[JIRA] (OVIRT-861) Upload Fedora 25 images to Glance
by Barak Korren (oVirt JIRA) 23 Nov '16

23 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-861?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-861: ------------------------------- Epic Link: OVIRT-403 > Upload Fedora 25 images to Glance > --------------------------------- > > Key: OVIRT-861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-861 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > FC25 was released, we should have the images available in oVirt. -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

[JIRA] (OVIRT-861) Upload Fedora 25 images to Glance
by Barak Korren (oVirt JIRA) 23 Nov '16

23 Nov '16

Barak Korren created OVIRT-861: ---------------------------------- Summary: Upload Fedora 25 images to Glance Key: OVIRT-861 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-861 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: High FC25 was released, we should have the images available in oVirt. -- This message was sent by Atlassian JIRA (v1000.571.1#100021)

1 0

Project ovirt-engine-api-model_4.0_build-artifacts-fc24-x86_64 is failing
by Sandro Bonazzola 23 Nov '16

23 Nov '16

http://jenkins.ovirt.org/job/ovirt-engine-api-model_4.0_build-artifacts-fc2… *00:04:35.993* + mv target/model.json exported-artifacts*00:04:35.993* mv: cannot stat 'target/model.json': No such file or directory*00:04:35.993* Took 93 seconds Can you please have a look? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 6

problem to see draft patches in gerrit.ovirt.org
by Maor Lipchuk 23 Nov '16

23 Nov '16

Hi all, There is a permission issue in gerrit.ovirt.org that blocks seeing draft patches. Once I try to see a draft patch I'm getting the following message: "The page you requested was not found, or you do not have permission to view this page." Will appreciate your help. Regards, Maor

4 3

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

23 Nov '16

------=_Part_774_1521482638.1479855607022 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/146//artifact/exported-a… Cheers, Jenkins ------=_Part_774_1521482638.1479855607022 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 - 22/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-appliance_master_build-artifacts-el7-x86…">ovirt-appliance_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-appliance_ovirt-4.0-pre_build-artifacts-…">ovirt-appliance_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-engine-api-model_4.0_build-artifacts-fc2…">ovirt-engine-api-model_4.0_build-artifacts-fc24-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-model_master_build-artifacts-…">ovirt-engine-api-model_master_build-artifacts-fc24-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_4.0-create-iso/">ovirt-live_4.0-create-iso</a> </td><td> <h3>This job generates a nightly iso of ovirt-live 4.0</h3> Need to move to std-ci or yamlize </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_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/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repoman_master_check-merged-el7-x86_64/">repoman_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/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/scan_security_and_license_ovirt-engine_master/">scan_security_and_license_ovirt-engine_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system_update_puppet/">system_update_puppet</a> </td><td> No Description </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</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_774_1521482638.1479855607022--

1 0

[JIRA] (OVIRT-822) prepare to remove fc23 and add fc25 to CI
by Evgheni Dereveanchin (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-822?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-822: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > prepare to remove fc23 and add fc25 to CI > ----------------------------------------- > > Key: OVIRT-822 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-822 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > Priority: High > > We might want to consider moving some of the configuration to use centos, > to avoid such a massive infra update every 6 months. -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

oVirt mirror sites - monitoring
by Nadav Goldin 22 Nov '16

22 Nov '16

Hi all, You are CC'ed to this email because you are listed as an oVirt mirror site maintainer in[1]. Recently, we developed a new system that triggers an alert once a mirror site is out of sync with resources.ovirt.org, it is called 'mirrorchecker'[1]. Up until now these alerts were sent to the infra members, and now, after seeing the system is stable I'd like to add per-mirror-maintainer alerts. The alerts will be specific for each mirror-site-maintainer, and are configured with a threshold of 48 hours. If any mirror maintainer doesn't want me to add his email, or would like to have a different email added than the one available at [1], feel free to contact me, I'll start adding the alerts next week. Thanks again for your bandwidth! Nadav [1] https://www.ovirt.org/develop/infra/repository-mirrors/ [2] http://mirrorchecker.readthedocs.io/en/latest/

1 0

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by Greg Sheremeta (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] Greg Sheremeta updated OVIRT-858: --------------------------------- Resolution: Done Status: Done (was: To Do) > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by Greg Sheremeta (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-858: -------------------------------------- I will put it there, thanks! > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-860) duplicate gerrit accounts - fromani
by Francesco Romani (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-860?page=com.atlassian.jira.p… ] Francesco Romani commented on OVIRT-860: ---------------------------------------- [~ederevea] I see 1000260 (FAS) and 1001396 (gmail/redhat) > duplicate gerrit accounts - fromani > ----------------------------------- > > Key: OVIRT-860 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-860 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Evgheni Dereveanchin > > Adding infra support > On Tue, Nov 22, 2016 at 9:26 AM, Francesco Romani <fromani(a)redhat.com> > wrote: > > Hi Infra, > > > > I used to authenticate on gerrit using FAS provider > > (https://admin.fedoraproject.org/accounts) > > and my FAS account. > > > > In the recent days it became too shaky, so I decided to try out > > the Google OAuth2 (gerrit-oauth-provider plugin) method, linking > > my @redhat.com account and the related gmail account. > > > > Apparently this caused split brain on gerrit, so now I have duplicated > > entry and I cannot be added to reviews. > > Plus: > > 1. if I log through fedora accounts (old method) I can review as usual > > 2. if I log through google/redhat, I only have +/-1 score and no special > > powers > > > > I'd like to switch to google oauth2 entirely or, if not possible, to solve > > the split brain issue. > > > > Can anybody help? :) > > > > Bests and thanks, > > > > -- > > Francesco Romani > > Red Hat Engineering Virtualization R & D > > Phone: 8261328 > > IRC: fromani > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-860) duplicate gerrit accounts - fromani
by Evgheni Dereveanchin (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-860?page=com.atlassian.jira.p… ] Evgheni Dereveanchin commented on OVIRT-860: -------------------------------------------- [~fromani(a)redhat.com] could you please tell me IDs of both accounts so that I can merge them? They are shown here: https://gerrit.ovirt.org/#/settings/ The field I'm interested in is "Account ID" > duplicate gerrit accounts - fromani > ----------------------------------- > > Key: OVIRT-860 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-860 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Evgheni Dereveanchin > > Adding infra support > On Tue, Nov 22, 2016 at 9:26 AM, Francesco Romani <fromani(a)redhat.com> > wrote: > > Hi Infra, > > > > I used to authenticate on gerrit using FAS provider > > (https://admin.fedoraproject.org/accounts) > > and my FAS account. > > > > In the recent days it became too shaky, so I decided to try out > > the Google OAuth2 (gerrit-oauth-provider plugin) method, linking > > my @redhat.com account and the related gmail account. > > > > Apparently this caused split brain on gerrit, so now I have duplicated > > entry and I cannot be added to reviews. > > Plus: > > 1. if I log through fedora accounts (old method) I can review as usual > > 2. if I log through google/redhat, I only have +/-1 score and no special > > powers > > > > I'd like to switch to google oauth2 entirely or, if not possible, to solve > > the split brain issue. > > > > Can anybody help? :) > > > > Bests and thanks, > > > > -- > > Francesco Romani > > Red Hat Engineering Virtualization R & D > > Phone: 8261328 > > IRC: fromani > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-860) duplicate gerrit accounts - fromani
by Evgheni Dereveanchin (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-860?page=com.atlassian.jira.p… ] Evgheni Dereveanchin updated OVIRT-860: --------------------------------------- Summary: duplicate gerrit accounts - fromani (was: Re: gerrit login troubles) > duplicate gerrit accounts - fromani > ----------------------------------- > > Key: OVIRT-860 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-860 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Evgheni Dereveanchin > > Adding infra support > On Tue, Nov 22, 2016 at 9:26 AM, Francesco Romani <fromani(a)redhat.com> > wrote: > > Hi Infra, > > > > I used to authenticate on gerrit using FAS provider > > (https://admin.fedoraproject.org/accounts) > > and my FAS account. > > > > In the recent days it became too shaky, so I decided to try out > > the Google OAuth2 (gerrit-oauth-provider plugin) method, linking > > my @redhat.com account and the related gmail account. > > > > Apparently this caused split brain on gerrit, so now I have duplicated > > entry and I cannot be added to reviews. > > Plus: > > 1. if I log through fedora accounts (old method) I can review as usual > > 2. if I log through google/redhat, I only have +/-1 score and no special > > powers > > > > I'd like to switch to google oauth2 entirely or, if not possible, to solve > > the split brain issue. > > > > Can anybody help? :) > > > > Bests and thanks, > > > > -- > > Francesco Romani > > Red Hat Engineering Virtualization R & D > > Phone: 8261328 > > IRC: fromani > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-855) Duplicate gerrit accounts - trichard
by Evgheni Dereveanchin (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-855?page=com.atlassian.jira.p… ] Evgheni Dereveanchin updated OVIRT-855: --------------------------------------- Summary: Duplicate gerrit accounts - trichard (was: Duplicate gerrit accounts - ) > Duplicate gerrit accounts - trichard > ------------------------------------ > > Key: OVIRT-855 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-855 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > Sending to infra-support to open a ticket. > On Fri, Nov 18, 2016 at 8:17 AM, Tahlia Richardson <trichard(a)redhat.com> > wrote: > > Hello, > > > > I cannot be added as a reviewer to Gerrit patches. > > The issue appears to be multiple accounts existing for the same user ( > > trichard(a)redhat.com) > > Please merge the duplicate accounts. > > The account ID for the correct trichard(a)redhat.com is 1001376. > > > > Thanks, > > > > Tahlia Richardson > > Technical Writer, RHEV/RHV > > Red Hat APAC > > Brisbane, Australia (GMT +10) > > IRC: trichard > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > 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.552.6#100018)

1 0

[JIRA] (OVIRT-855) Duplicate gerrit accounts -
by Evgheni Dereveanchin (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-855?page=com.atlassian.jira.p… ] Evgheni Dereveanchin updated OVIRT-855: --------------------------------------- Summary: Duplicate gerrit accounts - (was: Duplicate gerrit accounts) > Duplicate gerrit accounts - > ---------------------------- > > Key: OVIRT-855 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-855 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > Sending to infra-support to open a ticket. > On Fri, Nov 18, 2016 at 8:17 AM, Tahlia Richardson <trichard(a)redhat.com> > wrote: > > Hello, > > > > I cannot be added as a reviewer to Gerrit patches. > > The issue appears to be multiple accounts existing for the same user ( > > trichard(a)redhat.com) > > Please merge the duplicate accounts. > > The account ID for the correct trichard(a)redhat.com is 1001376. > > > > Thanks, > > > > Tahlia Richardson > > Technical Writer, RHEV/RHV > > Red Hat APAC > > Brisbane, Australia (GMT +10) > > IRC: trichard > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > 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.552.6#100018)

1 0

[JIRA] (OVIRT-855) Duplicate gerrit accounts
by Evgheni Dereveanchin (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-855?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-855: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Duplicate gerrit accounts > ------------------------- > > Key: OVIRT-855 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-855 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > Sending to infra-support to open a ticket. > On Fri, Nov 18, 2016 at 8:17 AM, Tahlia Richardson <trichard(a)redhat.com> > wrote: > > Hello, > > > > I cannot be added as a reviewer to Gerrit patches. > > The issue appears to be multiple accounts existing for the same user ( > > trichard(a)redhat.com) > > Please merge the duplicate accounts. > > The account ID for the correct trichard(a)redhat.com is 1001376. > > > > Thanks, > > > > Tahlia Richardson > > Technical Writer, RHEV/RHV > > Red Hat APAC > > Brisbane, Australia (GMT +10) > > IRC: trichard > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > 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.552.6#100018)

1 0

[JIRA] (OVIRT-860) Re: gerrit login troubles
by Evgheni Dereveanchin (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-860?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-860: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Re: gerrit login troubles > ------------------------- > > Key: OVIRT-860 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-860 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Evgheni Dereveanchin > > Adding infra support > On Tue, Nov 22, 2016 at 9:26 AM, Francesco Romani <fromani(a)redhat.com> > wrote: > > Hi Infra, > > > > I used to authenticate on gerrit using FAS provider > > (https://admin.fedoraproject.org/accounts) > > and my FAS account. > > > > In the recent days it became too shaky, so I decided to try out > > the Google OAuth2 (gerrit-oauth-provider plugin) method, linking > > my @redhat.com account and the related gmail account. > > > > Apparently this caused split brain on gerrit, so now I have duplicated > > entry and I cannot be added to reviews. > > Plus: > > 1. if I log through fedora accounts (old method) I can review as usual > > 2. if I log through google/redhat, I only have +/-1 score and no special > > powers > > > > I'd like to switch to google oauth2 entirely or, if not possible, to solve > > the split brain issue. > > > > Can anybody help? :) > > > > Bests and thanks, > > > > -- > > Francesco Romani > > Red Hat Engineering Virtualization R & D > > Phone: 8261328 > > IRC: fromani > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-860) Re: gerrit login troubles
by Gil Shinar (oVirt JIRA) 22 Nov '16

22 Nov '16

Gil Shinar created OVIRT-860: -------------------------------- Summary: Re: gerrit login troubles Key: OVIRT-860 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-860 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Gil Shinar Assignee: infra Adding infra support On Tue, Nov 22, 2016 at 9:26 AM, Francesco Romani <fromani(a)redhat.com> wrote: > Hi Infra, > > I used to authenticate on gerrit using FAS provider > (https://admin.fedoraproject.org/accounts) > and my FAS account. > > In the recent days it became too shaky, so I decided to try out > the Google OAuth2 (gerrit-oauth-provider plugin) method, linking > my @redhat.com account and the related gmail account. > > Apparently this caused split brain on gerrit, so now I have duplicated > entry and I cannot be added to reviews. > Plus: > 1. if I log through fedora accounts (old method) I can review as usual > 2. if I log through google/redhat, I only have +/-1 score and no special > powers > > I'd like to switch to google oauth2 entirely or, if not possible, to solve > the split brain issue. > > Can anybody help? :) > > Bests and thanks, > > -- > Francesco Romani > Red Hat Engineering Virtualization R & D > Phone: 8261328 > IRC: fromani > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

gerrit login troubles
by Francesco Romani 22 Nov '16

22 Nov '16

Hi Infra, I used to authenticate on gerrit using FAS provider (https://admin.fedoraproject.org/accounts) and my FAS account. In the recent days it became too shaky, so I decided to try out the Google OAuth2 (gerrit-oauth-provider plugin) method, linking my @redhat.com account and the related gmail account. Apparently this caused split brain on gerrit, so now I have duplicated entry and I cannot be added to reviews. Plus: 1. if I log through fedora accounts (old method) I can review as usual 2. if I log through google/redhat, I only have +/-1 score and no special powers I'd like to switch to google oauth2 entirely or, if not possible, to solve the split brain issue. Can anybody help? :) Bests and thanks, -- Francesco Romani Red Hat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

2 1

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by Barak Korren (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-858: ------------------------------------ Looking at comments so far, its clear this is not yet ripe for attaching to the system tests flow. But it should get there one day. So I'm thinking this should probably go into a 'ui-perf-suit-master' directory (I'm assuming this is just testing master for now) in 'ovirt-system-tests'. Over time I hope we'll get around to building a Lago environment around it and a suit runner script. > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by eyal edri [Administrator] (oVirt JIRA) 22 Nov '16

22 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-858: ------------------------------------------------- I think 'performance-suite-master' would be a good start under the ovitr-system-tests repo. we can include there tests for UI and other parts .. if you have something for 4.0, then you also add performance-suite-4.0 ( you can soft link if its the same code for starts ). > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

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

22 Nov '16

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

1 2

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

22 Nov '16

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

1 0

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

22 Nov '16

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

1 1

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

22 Nov '16

------=_Part_734_1380540673.1479769209687 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/145//artifact/exported-a… Cheers, Jenkins ------=_Part_734_1380540673.1479769209687 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 - 21/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-appliance_master_build-artifacts-el7-x86…">ovirt-appliance_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-appliance_ovirt-4.0-pre_build-artifacts-…">ovirt-appliance_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-appliance_ovirt-4.0-snapshot_build-artif…">ovirt-appliance_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-engine-api-model_4.0_build-artifacts-fc2…">ovirt-engine-api-model_4.0_build-artifacts-fc24-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-model_master_build-artifacts-…">ovirt-engine-api-model_master_build-artifacts-fc24-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_build-artifacts-fc24-x86_6…">ovirt-engine_master_build-artifacts-fc24-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-engine_master_upgrade-from-4.0_el7_merge…">ovirt-engine_master_upgrade-from-4.0_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_4.0-create-iso/">ovirt-live_4.0-create-iso</a> </td><td> <h3>This job generates a nightly iso of ovirt-live 4.0</h3> Need to move to std-ci or yamlize </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_build-artifacts-fc24…">ovirt-provider-ovn_master_build-artifacts-fc24-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/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repoman_master_check-merged-el7-x86_64/">repoman_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/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/scan_security_and_license_ovirt-engine_master/">scan_security_and_license_ovirt-engine_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system_update_puppet/">system_update_puppet</a> </td><td> No Description </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_734_1380540673.1479769209687--

1 0

Build failed in Jenkins: ovirt_4.0_he-system-tests #545
by jenkins＠jenkins.phx.ovirt.org 21 Nov '16

21 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/545/changes> Changes: [Your Name] basic networking: added vlan attach/detach tests ------------------------------------------ [...truncated 1405 lines...] ## Mon Nov 21 16:13:26 UTC 2016 Finished env: el7:epel-7-x86_64 ## took 2282 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_4.0_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 2125 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=4.0 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_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson7120295683064234860.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=4.0 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> + OVIRT_SUITE=4.0 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/545/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/545/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/545/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_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson2332721095585244872.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_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_4.0_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_4.0_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_4.0_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_4.0_he-system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_4.0_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_4.0_he-system-tests/ws/ovirt-system-test…> + mock_root=epel-7-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + [[ -n epel-7-x86_64-0c362156a2fa4a935ea8b988eb73b2ad ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/epel-7-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> ++ virsh list --all --uuid POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 1

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by Greg Sheremeta (oVirt JIRA) 21 Nov '16

21 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-858: -------------------------------------- "I don't have many future plans" I meant "I don't have any near future plans" > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by Greg Sheremeta (oVirt JIRA) 21 Nov '16

21 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-858: -------------------------------------- [~eedri] I looked at your calendar -- haha, you don't need another meeting :) Are you sure? For this specific script, I don't have many future plans. It's doing what I need to for the moment. In the future, we'd like to performance test each commit. I believe that is far into the future, and thus shouldn't dictate where this tiny script lives. So what directory would you suggest so I can commit it? > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by eyal edri [Administrator] (oVirt JIRA) 21 Nov '16

21 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-858: ------------------------------------------------- So it's not really Up testing right? It's performance testing, which in this case is running on the US itself, but as you said, more performance tests might be coming soon... I would say it might be actually good candidate for a performance suit on oVirt system tests. But I think it's best if we'll do a short meeting over it and hear your plans for future tests so we can decide on the best solution, I guess Roy should be there as well, and he knows about system tests, so it will be easier. On Nov 21, 2016 8:30 PM, "Greg Sheremeta (oVirt JIRA)" < > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by Greg Sheremeta (oVirt JIRA) 21 Nov '16

21 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-858: -------------------------------------- Exactly. It's a selenium loop that does the exact same flow through oVirt say 400 times, and then makes sure performance doesn't degrade over time. See http://imgur.com/a/XcGib for an example result. In that case, I compared a new rpc patch to master. But sometimes I want to compare two patches. Perhaps a better phrasing is "stability and performance" or "memory leak testing" or "long time browser open performance" I dunno > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by eyal edri [Administrator] (oVirt JIRA) 21 Nov '16

21 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-858: ------------------------------------------------- can you elaborate on "running copy of oVirt"? It means that you built engine + webadmin from a patch and installed it + run it? so you now have a running oVirt instance which then you run the tests on? (selenium style sort of thing?) > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0

[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests
by Greg Sheremeta (oVirt JIRA) 21 Nov '16

21 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-858: -------------------------------------- I check out the code, run the script manually against a patched running copy of oVirt, and then I make a graph with those results. It's not automated at all, as you can see. > new gerrit repo: ovirt-ui-tests > ------------------------------- > > Key: OVIRT-858 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > Please create a new gerrit repo called ovirt-ui-tests. > Description: functional tests for oVirt UI, focused around performance > testing > +2 rights for me, awels, vszocs, oourfali > Please mirror it to github. > Let me know if you need more information. > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.552.6#100018)

1 0