- Infra - oVirt List Archives

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

07 Nov '16

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

1 1

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

07 Nov '16

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

1 6

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

07 Nov '16

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

1 1

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

07 Nov '16

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

1 1

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

07 Nov '16

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

1 112

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

07 Nov '16

------=_Part_974_1109143668.1478473205978 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/130//artifact/exported-a… Cheers, Jenkins ------=_Part_974_1109143668.1478473205978 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 - 06/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_4.0_build-artifacts-el7-x86_64/">ovirt-engine_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_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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/">ovirt_3.6_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_image-ng-system-tests/">ovirt_4.0_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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_3.6_check-closure_el6_merged/">repos_3.6_check-closure_el6_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_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_vdsm_jsonrpc_java_ma…">scan_security_and_license_vdsm_jsonrpc_java_master_whitesource</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_974_1109143668.1478473205978--

1 0

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

06 Nov '16

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

1 1

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

06 Nov '16

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

1 1

Build failed in Jenkins: ovirt_4.0_system-tests #629
by jenkins＠jenkins.phx.ovirt.org 06 Nov '16

06 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/629/changes> Changes: [Gal Ben Haim] Switched the mock automation scripts to symlinks [Gil Shinar] Create source mount point ------------------------------------------ [...truncated 820 lines...] ## took 1549 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-fedora-23-x86_64.fc23.basic_suite_4.0.sh/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_system-tests/ws/ovirt-system-tests/d…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/d…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 1388 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_system-tests] $ /bin/bash -xe /tmp/hudson9156453899063302634.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_system-tests/ws/> + OVIRT_SUITE=4.0 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/629/artifact/exported-a…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/629/artifact/exported-a…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/629/artifact/exported-a…> 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 tar cvzf exported-artifacts/logs.tgz "${logs[@]}" rm -rf "${logs[@]}" 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" [ovirt_4.0_system-tests] $ /bin/bash -xe /tmp/hudson1105985712999322223.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs ./ovirt-system-tests/logs/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/build.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/root.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/state.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/build.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/root.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/state.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.basic_suite_4.0.sh/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.basic_suite_4.0.sh/basic_suite_4.0.sh.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/stdout_stderr.log + rm -rf ./ovirt-system-tests/logs + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/m…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-fedora-23-x86_64.fc23.cfg + mock_root=mocker-fedora-23-x86_64.fc23 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-fedora-23-x86_64.fc23' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_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_system-tests/ws/ovirt-system-tests> --root=mocker-fedora-23-x86_64.fc23 --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/l….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.4.3)... 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_system-tests/ws/ovirt-system-tests/m…> + mock_root=fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + [[ -n fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 1

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

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-416: ------------------------------------------------- Any patches sent on this? Also, wanted to mention #OVIRT-751 is handling similar purpose with enabling better maven caching, so it might suffice as a starting point in optimizing ovirt-engine runtime for builds. > [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: infra > > 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.499.4#100018)

1 0

[JIRA] (OVIRT-375) add gamification to oVirt infra
by eyal edri [Administrator] (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-375?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-375: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > add gamification to oVirt infra > ------------------------------- > > Key: OVIRT-375 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-375 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: General > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > > Think on options to add gamification options to oVirt and which services can be augmented. > The following site might be interesting to use to get a working service: > - https://ovirt.getbadges.io/manager/project/677/app/new -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-763) [ost][rfe] ability to use custom repos
by eyal edri [Administrator] (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-763: ------------------------------------------------- Getting into specific digits of versions sounds like very complicated solution which might break often. We will add a job for it as mentioned before, and it will allow giving any 'custom refspec' as all CI jobs are allowing today. (e.g refs/heads/master for merged refs/changes/12/65912/4 for an open patch) > [ost][rfe] ability to use custom repos > --------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-810) Cache issues
by Piotr Kliczewski (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-810?page=com.atlassian.jira.p… ] Piotr Kliczewski commented on OVIRT-810: ---------------------------------------- Sandro, can you give more details? 6 lis 2016 09:07 "eyal edri [Administrator] (oVirt JIRA)" < > Cache issues > ------------ > > Key: OVIRT-810 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-810 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > We saw artififactory cache refresh issues which zapping cache was not able > to solve. Once that was overcame we saw issues with engine upgrade jobs due > to local cache which is used by those jobs. -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-763) [ost][rfe] ability to use custom repos
by Piotr Kliczewski (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] Piotr Kliczewski commented on OVIRT-763: ---------------------------------------- I think that 3.6, 4.0 and master is not enough. I was thinking about four digit versions but i like Dan's idea of using hashes. This would be perfect for devs. 6 lis 2016 10:05 "eyal edri [Administrator] (oVirt JIRA)" < jira(a)ovirt-jira.atlassian.net> napisał(a): eyal edri [Administrator] <https://ovirt-jira.atlassian.net/secure/ViewProfile.jspa?name=eedri> *commented* on [image: By-EMAIL] OVIRT-763 <https://ovirt-jira.atlassian.net/browse/OVIRT-763> Re: [ost][rfe] ability to use custom repos <https://ovirt-jira.atlassian.net/browse/OVIRT-763> I renamed the task, since you can choose version today by choosing to run the relevant suite (3.6,4.0,master), the requirement should be to allow running with custom repos. So one option will be to use the '-s' param and another one will be add a jenkins job to support it as mentioned in this ticket. [image: Add Comment] <https://ovirt-jira.atlassian.net/browse/OVIRT-763#add-comment> Add Comment <https://ovirt-jira.atlassian.net/browse/OVIRT-763#add-comment> This message was sent by Atlassian JIRA (v1000.499.4#100018-sha1:b6a952e) [image: Atlassian logo] > [ost][rfe] ability to use custom repos > --------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-763) [ost][rfe] ability to use custom repos
by eyal edri [Administrator] (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-763: ------------------------------------------------- I renamed the task, since you can choose version today by choosing to run the relevant suite (3.6,4.0,master), the requirement should be to allow running with custom repos. So one option will be to use the '-s' param and another one will be add a jenkins job to support it as mentioned in this ticket. > [ost][rfe] ability to use custom repos > --------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-763) [ost][rfe] ability to choose version to be installed
by eyal edri [Administrator] (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-763: -------------------------------------------- Summary: [ost][rfe] ability to choose version to be installed (was: [Lago][rfe] ability to choose version to be installed) > [ost][rfe] ability to choose version to be installed > ---------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-763) [ost][rfe] ability to use custom repos
by eyal edri [Administrator] (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-763: -------------------------------------------- Summary: [ost][rfe] ability to use custom repos (was: [ost][rfe] ability to choose version to be installed ) > [ost][rfe] ability to use custom repos > --------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-763) [ost][rfe] ability to choose version to be installed
by eyal edri [Administrator] (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-763: -------------------------------------------- Summary: [ost][rfe] ability to choose version to be installed (was: [ost][rfe] ability to choose version to be installed) > [ost][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-810) Cache issues
by eyal edri [Administrator] (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-810?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-810: ------------------------------------------------- can you be more specific? is it only on the engine-upgrade jobs? These jobs are the only ones who doesn't run on mock, so maybe we need to improve the clean script there, and we're also planning to move this job to Lago, so hopefully it won't happen anymore. > Cache issues > ------------ > > Key: OVIRT-810 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-810 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > We saw artififactory cache refresh issues which zapping cache was not able > to solve. Once that was overcame we saw issues with engine upgrade jobs due > to local cache which is used by those jobs. -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-810) Cache issues
by Piotr Kliczewski (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-810?page=com.atlassian.jira.p… ] Piotr Kliczewski commented on OVIRT-810: ---------------------------------------- It seems to not to be only about timeouts. Sandro mentioned local cache which had to be manually refreshed. 6 lis 2016 08:41 "eyal edri [Administrator] (oVirt JIRA)" < > Cache issues > ------------ > > Key: OVIRT-810 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-810 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > We saw artififactory cache refresh issues which zapping cache was not able > to solve. Once that was overcame we saw issues with engine upgrade jobs due > to local cache which is used by those jobs. -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

[JIRA] (OVIRT-810) Cache issues
by eyal edri [Administrator] (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-810?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-810: ------------------------------------------------- Isn't there already a ticket on this? [~ederevea], talking on changing the defaults ? > Cache issues > ------------ > > Key: OVIRT-810 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-810 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > We saw artififactory cache refresh issues which zapping cache was not able > to solve. Once that was overcame we saw issues with engine upgrade jobs due > to local cache which is used by those jobs. -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

OST 3.6 branch failing due to mismatch vdsm-jsonrpc-java version
by Nadav Goldin 06 Nov '16

06 Nov '16

Hi Piotr, OST on 3.6 branch is failing due to[1]: 03:50:01 Error: Package: ovirt-engine-backend-3.6.10-0.0.master.20161104223702.git9d234e8.el6.noarch (alocalsync) 03:50:01 Requires: vdsm-jsonrpc-java >= 1.1.14 03:50:01 Available: vdsm-jsonrpc-java-1.1.13-1.el6.noarch (alocalsync) 03:50:01 vdsm-jsonrpc-java = 1.1.13-1.el6 Has there been any package changes? maybe a caching issue? Thanks, Nadav. [1] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3297/

3 2

[JIRA] (OVIRT-811) upgrade jobs failing trying to make engine RPM
by eyal edri [Administrator] (oVirt JIRA) 06 Nov '16

06 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-811?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-811: ------------------------------------------------- I know there were some failures on the weekend due to network issues, have you tried to rebase and re-run again? The errors from rpmbuild looks like it couldn't connect to artifactory: [ERROR] Failed to execute goal on project common-dependencies: Could not resolve dependencies for project org.ovirt.engine.core.manager:common-dependencies:jar:4.1.0-SNAPSHOT: Failure to find org.ovirt.vdsm-jsonrpc-java:vdsm-jsonrpc-java-client:jar:1.3.3 in http://artifactory.ovirt.org/artifactory/ovirt-mirror was cached in the local repository, resolution will not be reattempted until the update interval of ovirt-maven-repository has elapsed or updates are forced -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the > upgrade jobs failing trying to make engine RPM > ---------------------------------------------- > > Key: OVIRT-811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hey, not sure if this is related to the one I reported earlier this week. > https://gerrit.ovirt.org/#/c/66095/2 > I also noticed it on one of Juan's patches, > https://gerrit.ovirt.org/#/c/66032/ > Logs: > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_creat… > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_cr… > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_creat… > All 3 appear to die trying to make the RPM. SRPM was successful. > BUILDING ENGINE RPM > + create_rpms > /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161104192441.el7.centos.src.rpm > /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo > .git4fe2734 > + local > src_rpm=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161104192441.el7.centos.src.rpm > + local > dst_dir=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo > + local release=.git4fe2734 > + local > workspace=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created > + local 'BUILD_JAVA_OPTS_MAVEN= -XX:MaxPermSize=1G > -Dgwt.compiler.localWorkers=1 ' > + local 'BUILD_JAVA_OPTS_GWT= -XX:PermSize=512M -XX:MaxPermSize=1G > -Xms1G -Xmx6G ' > + env 'BUILD_JAVA_OPTS_MAVEN= -XX:MaxPermSize=1G > -Dgwt.compiler.localWorkers=1 ' 'BUILD_JAVA_OPTS_GWT= -XX:PermSize=512M > -XX:MaxPermSize=1G -Xms1G -Xmx6G ' rpmbuild -D > 'ovirt_build_minimal 1' -D 'release_suffix .git4fe2734' -D > 'ovirt_build_extra_flags -gs > /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/artifactory-ovirt-org-settings.xml' > -D '_srcrpmdir > /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' > -D '_specdir > /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' > -D '_sourcedir > /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' > -D '_rpmdir > /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' > -D '_builddir > /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' > --rebuild > /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161104192441.el7.centos.src.rpm > + return 1 > Build step 'Execute shell' marked build as failure > Performing Post build task... > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

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

06 Nov '16

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

1 1

[JIRA] (OVIRT-812) 41339 infra-support
by m.kos＠lycos.com (oVirt JIRA) 06 Nov '16

06 Nov '16

m.kos(a)lycos.com created OVIRT-812: ------------------------------------- Summary: 41339 infra-support Key: OVIRT-812 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-812 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: m.kos(a)lycos.com Assignee: infra Attachments: EMAIL_7632934025_infra-support.zip -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

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

06 Nov '16

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

1 1

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

06 Nov '16

------=_Part_865_210930791.1478386805814 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/129//artifact/exported-a… Cheers, Jenkins ------=_Part_865_210930791.1478386805814 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 - 05/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/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/">ovirt-engine_4.0_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_4.0_upgrade-from-4.0_el7_merged/">ovirt-engine_4.0_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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/">ovirt_3.6_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_image-ng-system-tests/">ovirt_4.0_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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_3.6_check-closure_el6_merged/">repos_3.6_check-closure_el6_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_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_vdsm_jsonrpc_java_ma…">scan_security_and_license_vdsm_jsonrpc_java_master_whitesource</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.6_build-artifacts-el6-x86_…">vdsm-jsonrpc-java_3.6_build-artifacts-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/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_865_210930791.1478386805814--

1 0

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

05 Nov '16

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

1 1

[JIRA] (OVIRT-811) upgrade jobs failing trying to make engine RPM
by Greg Sheremeta (oVirt JIRA) 05 Nov '16

05 Nov '16

Greg Sheremeta created OVIRT-811: ------------------------------------ Summary: upgrade jobs failing trying to make engine RPM Key: OVIRT-811 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-811 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Hey, not sure if this is related to the one I reported earlier this week. https://gerrit.ovirt.org/#/c/66095/2 I also noticed it on one of Juan's patches, https://gerrit.ovirt.org/#/c/66032/ Logs: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_creat… http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_cr… http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_creat… All 3 appear to die trying to make the RPM. SRPM was successful. BUILDING ENGINE RPM + create_rpms /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161104192441.el7.centos.src.rpm /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo .git4fe2734 + local src_rpm=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161104192441.el7.centos.src.rpm + local dst_dir=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo + local release=.git4fe2734 + local workspace=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created + local 'BUILD_JAVA_OPTS_MAVEN= -XX:MaxPermSize=1G -Dgwt.compiler.localWorkers=1 ' + local 'BUILD_JAVA_OPTS_GWT= -XX:PermSize=512M -XX:MaxPermSize=1G -Xms1G -Xmx6G ' + env 'BUILD_JAVA_OPTS_MAVEN= -XX:MaxPermSize=1G -Dgwt.compiler.localWorkers=1 ' 'BUILD_JAVA_OPTS_GWT= -XX:PermSize=512M -XX:MaxPermSize=1G -Xms1G -Xmx6G ' rpmbuild -D 'ovirt_build_minimal 1' -D 'release_suffix .git4fe2734' -D 'ovirt_build_extra_flags -gs /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/artifactory-ovirt-org-settings.xml' -D '_srcrpmdir /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' -D '_specdir /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' -D '_sourcedir /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' -D '_rpmdir /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' -D '_builddir /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo' --rebuild /home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_created/tmp_repo/ovirt-engine-4.1.0-0.0.master.20161104192441.el7.centos.src.rpm + return 1 Build step 'Execute shell' marked build as failure Performing Post build task... -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

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

05 Nov '16

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

1 1

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

05 Nov '16

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

1 1

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

05 Nov '16

------=_Part_765_1307759257.1478300406500 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/128//artifact/exported-a… Cheers, Jenkins ------=_Part_765_1307759257.1478300406500 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 - 04/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/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/">ovirt-engine_4.0_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_4.0_upgrade-from-4.0_el7_merged/">ovirt-engine_4.0_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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/">ovirt_3.6_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_image-ng-system-tests/">ovirt_4.0_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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_3.6_check-closure_el6_merged/">repos_3.6_check-closure_el6_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_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_vdsm_jsonrpc_java_ma…">scan_security_and_license_vdsm_jsonrpc_java_master_whitesource</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.6_build-artifacts-el6-x86_…">vdsm-jsonrpc-java_3.6_build-artifacts-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/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_765_1307759257.1478300406500--

1 0

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

04 Nov '16

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

1 1

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

04 Nov '16

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

1 1

[JIRA] (OVIRT-810) Cache issues
by Piotr Kliczewski (oVirt JIRA) 04 Nov '16

04 Nov '16

Piotr Kliczewski created OVIRT-810: -------------------------------------- Summary: Cache issues Key: OVIRT-810 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-810 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Piotr Kliczewski Assignee: infra We saw artififactory cache refresh issues which zapping cache was not able to solve. Once that was overcame we saw issues with engine upgrade jobs due to local cache which is used by those jobs. -- This message was sent by Atlassian JIRA (v1000.499.4#100018)

1 0

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

04 Nov '16

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

1 1

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

04 Nov '16

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #2596 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 04 Nov '16

04 Nov '16

------=_Part_673_1164469081.1478230320096 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/2596/, Build Number: 2596, Build Status: FAILURE ------=_Part_673_1164469081.1478230320096--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #2594 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 04 Nov '16

04 Nov '16

------=_Part_659_1425138792.1478215464652 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/2594/, Build Number: 2594, Build Status: FAILURE ------=_Part_659_1425138792.1478215464652--

1 1

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

04 Nov '16

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

1 2

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

04 Nov '16

------=_Part_655_2008732856.1478214006302 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/127//artifact/exported-a… Cheers, Jenkins ------=_Part_655_2008732856.1478214006302 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 - 03/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/ovirt-engine_3.6_build-artifacts-el6-x86_64/">ovirt-engine_3.6_build-artifacts-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/ovirt-engine_3.6_build-artifacts-fc23-x86_64/">ovirt-engine_3.6_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_4.0_build-artifacts-fc23-x86_64/">ovirt-engine_4.0_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/">ovirt-engine_4.0_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_4.0_upgrade-from-4.0_el7_merged/">ovirt-engine_4.0_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-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-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_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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_image-ng-system-tests/">ovirt_4.0_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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_vdsm_jsonrpc_java_ma…">scan_security_and_license_vdsm_jsonrpc_java_master_whitesource</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_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-jsonrpc-java_3.6_build-artifacts-el6-x86_…">vdsm-jsonrpc-java_3.6_build-artifacts-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> ------=_Part_655_2008732856.1478214006302--

1 0

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

03 Nov '16

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

1 1

[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-763: ------------------------------------------------- [~pkliczew(a)redhat.com] can you show [~gbenhaim(a)redhat.com] or [~ngoldin(a)redhat.com] what is not working for you? maybe we can help > [Lago][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

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

03 Nov '16

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

1 1

[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed
by Piotr Kliczewski (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] Piotr Kliczewski commented on OVIRT-763: ---------------------------------------- I will check this approach on my machine but it would not solve the issue with system tests described earlier. If it works it partially solves the issue. > [Lago][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed
by Nadav Goldin (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-763: ------------------------------------ In order to run it directly with {code} run_suite.sh {code} use: {code} ./run_suite.sh -s http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64… basic-suite-master {code} This will prefer the RPMs found in the ovirt-engine_master_build, also, if you would like to use different resources(i.e. vdsm and engine), create a configuration file, assuming it is 'extra-sources': {code} $ cat extra-sources http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64… http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/1071/ {code} and run: {code} ./run_suite.sh -s \"conf:/home/ngoldin/ovirt-system-tests/basic-suite-master/extra-sources\" basic-suite-master {code} the "-s" parameter can accept any parameter that repoman accepts, it is quite flexible, have a look at: http://repoman.readthedocs.io, [~pkliczew(a)redhat.com] - tell me how it works for you. [~danken(a)redhat.com] - we have an open ticket for that https://ovirt-jira.atlassian.net/browse/OST-9 , though until it is completed - it should be fairly easy to run it locally by triggering the build_artifacts from the Jenkins job and passing the URL/or locally built RPMs to ./run_suite.sh. > [Lago][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-763: ------------------------------------------------- we would value it also, but currently we don't have available resources to do it, its in the queue. Until then, anyone should be able to run Lago + OST if needed on his machine without too much effort, and if documentation is missing or something isn't working please report it and we'll do our best to help. > [Lago][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed
by danken (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] danken commented on OVIRT-763: ------------------------------ I would value a jenkins job running ovirt-system-test with specific engine and vdsm hashes. Applications whose hashes are not specified should be taken from the default repository. > [Lago][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed
by Nadav Goldin (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-763: ------------------------------------ Hi [~pkliczew(a)redhat.com] sorry for missing them, I'm closing the GitHub issue as this is the right place for it(OST). You can run it with a custom repo in the following manner, in Lago directly: {code} lago ovirt reposetup --reposync-yum-config basic_suite_master/reposync-config.repo --custom-source http://jenkins.ovirt.org/job/ovirt-engine_3.6_build-artifacts-el7-x86_64/13… {code} the custom-source will be used first. About passing it from run_suite.sh, I'll test and update. > [Lago][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-809) [gerrit hooks] recreate set_modified hook
by Shlomo Ben David (oVirt JIRA) 03 Nov '16

03 Nov '16

Shlomo Ben David created OVIRT-809: -------------------------------------- Summary: [gerrit hooks] recreate set_modified hook Key: OVIRT-809 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-809 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Shlomo Ben David Assignee: infra -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0