- Infra - oVirt List Archives

Build failed in Jenkins: ovirt_master_system-tests #865
by jenkins＠jenkins.phx.ovirt.org 13 Dec '16

13 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_master_system-tests/865/changes> Changes: [Yaniv Kaul] - Removed some undeeded deps. [Eyal Edri] move ovirt-engine build artifacts to build on-change [Sandro Bonazzola] Revert "qemu: use 7.3 beta repo" ------------------------------------------ [...truncated 682 lines...] ## 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 196 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/hudson7888588460657683557.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/865/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_master_system-tests/865/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/865/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 -x 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 # 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" # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then for log in "${logs[@]}"; do [[ "$log" = ./exported-artifacts/* ]] && continue 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 # remove mock caches that are older then 2 days: find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 | \ xargs -0 -tr sudo rm -rf # We make no effort to leave around caches that may still be in use because # packages installed in them may go out of date, so may as well recreate them # 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 if $failed; then echo "Cleanup script failed, propegating failure to job" exit 1 fi [ovirt_master_system-tests] $ /bin/bash -x /tmp/hudson1296377301485086069.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 # # # ####################################################################### + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + for log in '"${logs[@]}"' + [[ ./ovirt-system-tests/logs = ./exported-artifacts/* ]] + 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-b8fbc97503d2f9478015768d3094ffe4 + [[ -n epel-7-x86_64-b8fbc97503d2f9478015768d3094ffe4 ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-b8fbc97503d2f9478015768d3094ffe4 + : + [[ -n '' ]] + find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 + xargs -0 -tr sudo rm -rf ++ virsh list --all --uuid + false POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Archiving artifacts

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4129 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Dec '16

13 Dec '16

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

1 22

Jenkins permissions
by Evgenia Tokar 13 Dec '16

13 Dec '16

Hi! I need permissions for retrigering jobs in Jenkins. username: jtokar email: jtokar(a)redhat.com Thanks, Jenny

2 1

Build failed in Jenkins: ovirt_3.6_system-tests #818
by jenkins＠jenkins.phx.ovirt.org 13 Dec '16

13 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/818/changes> Changes: [Yaniv Kaul] - Removed some undeeded deps. [Eyal Edri] move ovirt-engine build artifacts to build on-change [Sandro Bonazzola] Revert "qemu: use 7.3 beta repo" ------------------------------------------ [...truncated 698 lines...] ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.basic_suite_3.6.sh/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_system-tests/ws/ovirt-system-tests/d…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_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 411 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_system-tests] $ /bin/bash -xe /tmp/hudson5915342196583079703.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_system-tests/ws/> + OVIRT_SUITE=3.6 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/818/artifact/exported-a…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/818/artifact/exported-a…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/818/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 -x 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 # 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" # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then for log in "${logs[@]}"; do [[ "$log" = ./exported-artifacts/* ]] && continue 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 # remove mock caches that are older then 2 days: find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 | \ xargs -0 -tr sudo rm -rf # We make no effort to leave around caches that may still be in use because # packages installed in them may go out of date, so may as well recreate them # 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 if $failed; then echo "Cleanup script failed, propegating failure to job" exit 1 fi [ovirt_3.6_system-tests] $ /bin/bash -x /tmp/hudson3070823141335913217.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + for log in '"${logs[@]}"' + [[ ./ovirt-system-tests/logs = ./exported-artifacts/* ]] + 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_system-tests/ws/ovirt-system-tests/m…> ]] + 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_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_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_system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/l….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.5.2)... 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_system-tests/ws/ovirt-system-tests/m…> + mock_root=epel-7-x86_64-aa7d25407b9c15b3736f25fc4fcf3710 + [[ -n epel-7-x86_64-aa7d25407b9c15b3736f25fc4fcf3710 ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-aa7d25407b9c15b3736f25fc4fcf3710 + : + [[ -n '' ]] + find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 + xargs -0 -tr sudo rm -rf ++ virsh list --all --uuid + false POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Archiving artifacts

1 0

oVirt infra daily report - unstable production jobs - 166
by jenkins＠jenkins.phx.ovirt.org 13 Dec '16

13 Dec '16

------=_Part_176_119464755.1481583609483 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/166//artifact/exported-a… Cheers, Jenkins ------=_Part_176_119464755.1481583609483 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 12/12/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/deploy-to-ovirt_experimental_master/">deploy-to-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/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/lago_master_build-artifacts-fc25-x86_64/">lago_master_build-artifacts-fc25-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-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-el6-x…">ovirt-guest-agent_master_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-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-hosted-engine-ha_3.6_create-rpms-el7-x86…">ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_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-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_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-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_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-4.1-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.1-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-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-optimizer_4.0_build-artifacts-el6-x86_64/">ovirt-optimizer_4.0_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_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/qemu_3.6_create-rpms-el7-ppc64le_merged/">qemu_3.6_create-rpms-el7-ppc64le_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/qemu_3.6_create-rpms-el7-x86_64_merged/">qemu_3.6_create-rpms-el7-x86_64_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/qemu_4.0_create-rpms-el7-ppc64le_merged/">qemu_4.0_create-rpms-el7-ppc64le_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/qemu_4.0_create-rpms-el7-x86_64_merged/">qemu_4.0_create-rpms-el7-x86_64_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/qemu_master_create-rpms-el7-ppc64le_merged/">qemu_master_create-rpms-el7-ppc64le_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/qemu_master_create-rpms-el7-x86_64_merged/">qemu_master_create-rpms-el7-x86_64_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/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/test-repo_ovirt_experimental_4.0/">test-repo_ovirt_experimental_4.0</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> ------=_Part_176_119464755.1481583609483--

1 0

[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock
by Nadav Goldin (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.p… ] Nadav Goldin updated OVIRT-935: ------------------------------- Epic Link: OVIRT-400 > Unable to build fc25 chroots with mock > -------------------------------------- > > Key: OVIRT-935 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-935 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Nadav Goldin > Assignee: infra > > Mock fails when trying to build the chroot for fedora25, on installing '@buildsys-build' group(with dnf) stage. > Open bug: https://bugzilla.redhat.com/show_bug.cgi?id=1360781 > Temporarily workaround: add the 'libcrypt' package to '.packages.fc25' file. > Possible solution: patch mock-*fc25*.cfg file in Jenkins repository to always install 'libcrypt' first. > Until fixed this will block us from building anything with mock on fc25(hit it when trying to build fc25 RPMs for lago). > Error logs: > {code} > DEBUG util.py:502: Executing command: ['/usr/bin/yum-deprecated', '--installroot', '/var/lib/mock/fedora-25-x86_64-2474d86945a1de9c6d14549ec2401b9c-8291/root/', '--releasever', '25', 'install', '@buildsys-build', 'git', 'python', 'python-dulwich', 'python-setuptools', 'yum', 'yum-utils', '--setopt=tsflags=nocontexts'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', > .... > DEBUG util.py:421: Yum command has been deprecated, use dnf instead. > DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information. > DEBUG util.py:421: Error: libcrypt conflicts with libcrypt-nss-2.24-3.fc25.x86_64 > DEBUG util.py:421: Error: libcrypt-nss conflicts with libcrypt-2.24-3.fc25.x86_64 > DEBUG util.py:421: You could try using --skip-broken to work around the problem > DEBUG util.py:421: You could try running: rpm -Va --nofiles --nodigest > DEBUG util.py:557: Child return code was: 1 > DEBUG util.py:180: kill orphans > {code} -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock
by Nadav Goldin (oVirt JIRA) 12 Dec '16

12 Dec '16

Nadav Goldin created OVIRT-935: ---------------------------------- Summary: Unable to build fc25 chroots with mock Key: OVIRT-935 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-935 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Nadav Goldin Assignee: infra Mock fails when trying to build the chroot for fedora25, on installing '@buildsys-build' group(with dnf) stage. Open bug: https://bugzilla.redhat.com/show_bug.cgi?id=1360781 Temporarily workaround: add the 'libcrypt' package to '.packages.fc25' file. Possible solution: patch mock-*fc25*.cfg file in Jenkins repository to always install 'libcrypt' first. Until fixed this will block us from building anything with mock on fc25(hit it when trying to build fc25 RPMs for lago). Error logs: {code} DEBUG util.py:502: Executing command: ['/usr/bin/yum-deprecated', '--installroot', '/var/lib/mock/fedora-25-x86_64-2474d86945a1de9c6d14549ec2401b9c-8291/root/', '--releasever', '25', 'install', '@buildsys-build', 'git', 'python', 'python-dulwich', 'python-setuptools', 'yum', 'yum-utils', '--setopt=tsflags=nocontexts'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', .... DEBUG util.py:421: Yum command has been deprecated, use dnf instead. DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information. DEBUG util.py:421: Error: libcrypt conflicts with libcrypt-nss-2.24-3.fc25.x86_64 DEBUG util.py:421: Error: libcrypt-nss conflicts with libcrypt-2.24-3.fc25.x86_64 DEBUG util.py:421: You could try using --skip-broken to work around the problem DEBUG util.py:421: You could try running: rpm -Va --nofiles --nodigest DEBUG util.py:557: Child return code was: 1 DEBUG util.py:180: kill orphans {code} -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

Re: http://lists.ovirt.org/pipermail/announce/ is not reachable
by Eyal Edri 12 Dec '16

12 Dec '16

I'm not sure who gets emails sent to infra-owner list. best to send it to infra or infra support. Adding Evgheni and Duck who are working on migration of the mm server. On Dec 12, 2016 2:58 PM, "Sandro Bonazzola" <sbonazzo(a)redhat.com> wrote: > The lists server is not reachable anymore. Looks like a dns issue: > > $ traceroute lists.ovirt.org > lists.ovirt.org: Name or service not known > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com >

4 3

mirrors errors
by Eyal Edri 12 Dec '16

12 Dec '16

Doesn't seem to be we're over the unavailable mirrors issue with the new repos added to STD CI: Lets start working on mirroring the relevant repos to mirrors.phx.ovirt.org and get control over the update process. http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc24-x86_64/16/arti… DEBUG util.py:421: https://mirrors.cat.pdx.edu/fedora/linux/updates/24/x86_64/repodata/repomd.…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: https://dl.fedoraproject.org/pub/fedora/linux/updates/24/x86_64/repodata/re…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: http://fedora.bhs.mirrors.ovh.net/linux/updates/24/x86_64/repodata/repomd.x…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: http://mirror.its.dal.ca/pub/fedora/linux/updates/24/x86_64/repodata/repomd…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: https://mirror.csclub.uwaterloo.ca/fedora/linux/updates/24/x86_64/repodata/…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: One of the configured repositories failed (updates), DEBUG util.py:421: and yum doesn't have enough cached data to continue. At this point the only DEBUG util.py:421: safe thing yum can do is fail. There are a few ways to work "fix" this: DEBUG util.py:421: 1. Contact the upstream for the repository and get them to fix the problem. DEBUG util.py:421: 2. Reconfigure the baseurl/etc. for the repository, to point to a working DEBUG util.py:421: upstream. This is most often useful if you are using a newer DEBUG util.py:421: distribution release than is supported by the repository (and the DEBUG util.py:421: packages for the previous distribution release still work). DEBUG util.py:421: 3. Disable the repository, so yum won't use it by default. Yum will then DEBUG util.py:421: just ignore the repository until you permanently enable it again or use DEBUG util.py:421: --enablerepo for temporary usage: DEBUG util.py:421: yum-config-manager --disable updates DEBUG util.py:421: 4. Configure the failing repository to be skipped, if it is unavailable. DEBUG util.py:421: Note that yum will try to contact the repo. when it runs most commands, DEBUG util.py:421: so will have to try and fail each time (and thus. yum will be be much DEBUG util.py:421: slower). If it is a very temporary problem though, this is often a nice DEBUG util.py:421: compromise: DEBUG util.py:421: yum-config-manager --save --setopt=updates.skip_if_unavailable=true DEBUG util.py:421: failure: repodata/repomd.xml from updates: [Errno 256] No more mirrors to try. DEBUG util.py:421: http://mirror.math.princeton.edu/pub/fedora/linux/updates/24/x86_64/repodat…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://linux.mirrors.es.net/fedora/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.cs.pitt.edu/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirrors.mit.edu/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://ftp.uci.edu/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: https://mirror.chpc.utah.edu/pub/fedora/linux/updates/24/x86_64/repodata/re…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://repo.atlantic.net/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.cs.princeton.edu/pub/mirrors/fedora/linux/updates/24/x86_64/r…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.uoregon.edu/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.cc.vt.edu/pub/fedora/linux/updates/24/x86_64/repodata/repomd.…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: https://mirrors.kernel.org/fedora/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: https://pubmirror2.math.uh.edu/fedora-buffet/fedora/linux/updates/24/x86_64…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.nexcess.net/fedora/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.sjc02.svwh.net/fedora/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.symnds.com/distributions/fedora/linux/updates/24/x86_64/repod…: [Errno -1] repomd.xml does not -- 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)

4 6

[JIRA] (OVIRT-934) improve ovirt.org -> www.ovirt.org redirect
by Evgheni Dereveanchin (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-934?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-934: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > improve ovirt.org -> www.ovirt.org redirect > ------------------------------------------- > > Key: OVIRT-934 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-934 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Low > > Currently http://ovirt.org points at a server that redirects users to https://www.ovirt.org > Trying to point the DNS directly at the OpenShift instance hosting the website does not work. > We need to fix this in order to avoid the intermediary redirect server. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-934) improve ovirt.org -> www.ovirt.org redirect
by Marc Dequènes (Duck) (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-934?page=com.atlassian.jira.p… ] Marc Dequènes (Duck) commented on OVIRT-934: -------------------------------------------- Here is some documentation with RFC numbers: http://cr.yp.to/im/cname.html > improve ovirt.org -> www.ovirt.org redirect > ------------------------------------------- > > Key: OVIRT-934 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-934 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > Currently http://ovirt.org points at a server that redirects users to https://www.ovirt.org > Trying to point the DNS directly at the OpenShift instance hosting the website does not work. > We need to fix this in order to avoid the intermediary redirect server. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-934) improve ovirt.org -> www.ovirt.org redirect
by Marc Dequènes (Duck) (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-934?page=com.atlassian.jira.p… ] Marc Dequènes (Duck) commented on OVIRT-934: -------------------------------------------- My original comment by mail follows: I would rather let it like this because: www.ovirt.org is an alias for beta-ovirtweb.rhcloud.com. beta-ovirtweb.rhcloud.com is an alias for ex-std-node798.prod.rhcloud.com. ex-std-node798.prod.rhcloud.com is an alias for ec2-52-23-162-8.compute-1.amazonaws.com. ec2-52-23-162-8.compute-1.amazonaws.com has address 52.23.162.8 So I don't think we can count on the node to never change, and that's the magic of the cloud in fact. We cannot have a CNAME for the domain, only a A record, so a permanent _redirect_ is fine I think. > improve ovirt.org -> www.ovirt.org redirect > ------------------------------------------- > > Key: OVIRT-934 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-934 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > Currently http://ovirt.org points at a server that redirects users to https://www.ovirt.org > Trying to point the DNS directly at the OpenShift instance hosting the website does not work. > We need to fix this in order to avoid the intermediary redirect server. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[ANN] oVirt 4.0.6 Fourth Release Candidate is now available
by Sandro Bonazzola 12 Dec '16

12 Dec '16

The oVirt Project is pleased to announce the availability of oVirt 4.0.6 fourth release candidate for testing, as of December 12th, 2016. This release is available now for: * Fedora 23 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * Fedora 23 (tech preview) * oVirt Next Generation Node 4.0 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the fourth release candidate of the sixth in a series of stabilization updates to the 4.0 series. 4.0.6 brings 4 enhancements and 61 bugfixes, including 25 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO will be available soon. [4] * A new oVirt Next Generation Node will be available soon [4] * A new oVirt Engine Appliance will be available soon for Red Hat Enterprise Linux and CentOS Linux (or similar) * Mirrors[5] might need up to one day to synchronize. Delay is due to the rolling out of CentOS 7.3 today causing several issues while building Live, Node and Appliance. They should be ready by tomorrow. Additional Resources: * Read more about the oVirt 4.0.6 release highlights: http://www.ovirt.org/release/4.0.6/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.0.6/ [4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/ [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[JIRA] (OVIRT-934) improve ovirt.org -> www.ovirt.org redirect
by Evgheni Dereveanchin (oVirt JIRA) 12 Dec '16

12 Dec '16

Evgheni Dereveanchin created OVIRT-934: ------------------------------------------ Summary: improve ovirt.org -> www.ovirt.org redirect Key: OVIRT-934 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-934 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low Currently http://ovirt.org points at a server that redirects users to https://www.ovirt.org Trying to point the DNS directly at the OpenShift instance hosting the website does not work. We need to fix this in order to avoid the intermediary redirect server. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

CentOS 7.3 is coming - and o-s-t's reposync needs updates
by Yaniv Kaul 12 Dec '16

12 Dec '16

I suspect that now that CentOS 7.3 is coming, suddenly packages that we thought are only in updates are in the base channel - which we were not fetching them from. Two examples I'm seeing (and I've fixed manually) are libxml2-python and libxml2. I'll continue chasing it down. Y.

3 6

Why experimental is failing
by Eyal Edri 12 Dec '16

12 Dec '16

Looks like the issue is in the following code: # disable any other repos to avoid downloading metadata yum install --disablerepo=\* --enablerepo=alocalsync -y yum-utils yum-config-manager --disable \* yum-config-manager --enable alocalsync in ost common/deploy-scripts/add_local_repo.sh Might be happening due to new yum available now from CentoOS 7.3... Do we really need to disable all repos when installing yum-utils? ---------- Forwarded message ---------- From: <jenkins(a)jenkins.phx.ovirt.org> Date: Mon, Dec 12, 2016 at 12:39 PM Subject: [oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3547 - FAILURE! To: infra(a)ovirt.org Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3547/, Build Number: 3547, Build Status: FAILURE _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.phx.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)

3 3

Can't run basic-suite-master in Lago
by Milan Zamazal 12 Dec '16

12 Dec '16

Hi, I tried to run basic-suite-master from current master branch of ovirt-system-tests. I run it on CentOS 7 with the following Lago packages installed: lago-0.28.0-1.el7.centos.noarch python-lago-ovirt-0.28.0-1.el7.centos.noarch python-lago-0.28.0-1.el7.centos.noarch lago-ovirt-0.28.0-1.el7.centos.noarch It doesn't work for me, I receive the following error: $ ./run_suite.sh basic-suite-master + CLI=lago + DO_CLEANUP=false + RECOMMENDED_RAM_IN_MB=8196 + EXTRA_SOURCES=() ++ getopt -o ho:e:n:b:cs:r: --long help,output:,engine:,node:,boot-iso:,cleanup --long extra-rpm-source,reposync-config: -n run_suite.sh -- basic-suite-master + options=' -- '\''basic-suite-master'\''' + [[ 0 != \0 ]] + eval set -- ' -- '\''basic-suite-master'\''' ++ set -- -- basic-suite-master + true + case $1 in + shift + break + [[ -z basic-suite-master ]] ++ realpath basic-suite-master + export SUITE=/var/lib/lago/ovirt-system-tests/basic-suite-master + SUITE=/var/lib/lago/ovirt-system-tests/basic-suite-master + '[' -z '' ']' + export PREFIX=/home/pdm/ovirt-system-tests/deployment-basic-suite-master + PREFIX=/home/pdm/ovirt-system-tests/deployment-basic-suite-master + false + [[ -d /var/lib/lago/ovirt-system-tests/basic-suite-master ]] + echo '################# lago version' ################# lago version + lago --version lago 0.28.0 + echo '#################' ################# + check_ram 8196 + local recommended=8196 ++ free -m ++ grep Mem ++ awk '{print $2}' + local cur_ram=7822 + [[ 7822 -lt 8196 ]] + echo 'It'\''s recommended to have at least 8196MB of RAM' 'installed on the system to run the system tests, if you find' 'issues while running them, consider upgrading your system.' '(only detected 7822MB installed)' It's recommended to have at least 8196MB of RAM installed on the system to run the system tests, if you find issues while running them, consider upgrading your system. (only detected 7822MB installed) + echo 'Running suite found in /var/lib/lago/ovirt-system-tests/basic-suite-master' Running suite found in /var/lib/lago/ovirt-system-tests/basic-suite-master + echo 'Environment will be deployed at /home/pdm/ovirt-system-tests/deployment-basic-suite-master' Environment will be deployed at /home/pdm/ovirt-system-tests/deployment-basic-suite-master + rm -rf /home/pdm/ovirt-system-tests/deployment-basic-suite-master + source /var/lib/lago/ovirt-system-tests/basic-suite-master/control.sh + prep_suite '' '' '' + local suite_name=basic-suite-master + suite_name=basic-suite-master + sed -r -e s,__ENGINE__,lago-basic-suite-master-engine,g -e 's,__HOST([0-9]+)__,lago-basic-suite-master-host\1,g' -e s,__LAGO_NET__,lago-basic-suite-master-lago,g -e s,__STORAGE__,lago-basic-suite-master-storage,g + run_suite + env_init '' /var/lib/lago/ovirt-system-tests/basic-suite-master/LagoInitFile + echo '#########################' ######################### + local template_repo=/var/lib/lago/ovirt-system-tests/basic-suite-master/template-repo.json + local initfile=/var/lib/lago/ovirt-system-tests/basic-suite-master/LagoInitFile + lago init /home/pdm/ovirt-system-tests/deployment-basic-suite-master /var/lib/lago/ovirt-system-tests/basic-suite-master/LagoInitFile --template-repo-path /var/lib/lago/ovirt-system-tests/basic-suite-master/template-repo.json @ Initialize and populate prefix: # Initialize prefix: * Create prefix dirs: * Create prefix dirs: Success (in 0:00:00) * Generate prefix uuid: * Generate prefix uuid: Success (in 0:00:00) * Create ssh keys: * Create ssh keys: Success (in 0:00:00) * Tag prefix as initialized: * Tag prefix as initialized: Success (in 0:00:00) # Initialize prefix: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-host0: * Create disk root: * Create disk root: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-host0: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-engine: * Create disk root: * Create disk root: Success (in 0:00:00) * Create disk nfs: * Create disk nfs: Success (in 0:00:00) * Create disk export: * Create disk export: Success (in 0:00:00) * Create disk iscsi: * Create disk iscsi: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-engine: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-host1: * Create disk root: * Create disk root: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-host1: Success (in 0:00:00) # Copying any deploy scripts: # Copying any deploy scripts: Success (in 0:00:00) # [Thread-1] Bootstrapping lago-basic-suite-master-host0: # [Thread-3] Bootstrapping lago-basic-suite-master-host1: # [Thread-2] Bootstrapping lago-basic-suite-master-engine: # [Thread-2] Bootstrapping lago-basic-suite-master-engine: Success (in 0:00:13) # [Thread-3] Bootstrapping lago-basic-suite-master-host1: Success (in 0:00:14) # [Thread-1] Bootstrapping lago-basic-suite-master-host0: Success (in 0:00:14) # Save prefix: * Save nets: * Save nets: Success (in 0:00:00) * Save VMs: * Save VMs: Success (in 0:00:00) * Save env: * Save env: Success (in 0:00:00) # Save prefix: Success (in 0:00:00) @ Initialize and populate prefix: Success (in 0:00:15) + env_repo_setup + echo '#########################' ######################### + local extrasrc + declare -a extrasrcs + cd /home/pdm/ovirt-system-tests/deployment-basic-suite-master + local reposync_conf=/var/lib/lago/ovirt-system-tests/basic-suite-master/reposync-config.repo + [[ -e '' ]] + echo 'using reposync config file: /var/lib/lago/ovirt-system-tests/basic-suite-master/reposync-config.repo' using reposync config file: /var/lib/lago/ovirt-system-tests/basic-suite-master/reposync-config.repo + lago ovirt reposetup --reposync-yum-config /var/lib/lago/ovirt-system-tests/basic-suite-master/reposync-config.repo @ Create prefix internal repo: # Syncing remote repos locally (this might take some time): * Acquiring lock for /var/lib/lago/reposync/repolock: * Acquiring lock for /var/lib/lago/reposync/repolock: Success (in 0:00:00) * Running reposync: * Running reposync: Success (in 0:00:06) # Syncing remote repos locally (this might take some time): Success (in 0:00:06) # Running repoman: # Running repoman: Success (in 0:00:05) # Save prefix: * Save nets: * Save nets: Success (in 0:00:00) * Save VMs: * Save VMs: Success (in 0:00:00) * Save env: * Save env: Success (in 0:00:00) # Save prefix: Success (in 0:00:00) @ Create prefix internal repo: Success (in 0:00:12) + cd - /home/pdm/ovirt-system-tests + env_start + echo '#########################' ######################### + cd /home/pdm/ovirt-system-tests/deployment-basic-suite-master + lago start @ Start Prefix: # Start nets: * Create network lago-basic-suite-master-lago: * Create network lago-basic-suite-master-lago: Success (in 0:00:05) # Start nets: Success (in 0:00:05) # Start vms: * Starting VM lago-basic-suite-master-host0: * Starting VM lago-basic-suite-master-host0: Success (in 0:00:00) * Starting VM lago-basic-suite-master-engine: * Starting VM lago-basic-suite-master-engine: Success (in 0:00:00) * Starting VM lago-basic-suite-master-host1: * Starting VM lago-basic-suite-master-host1: Success (in 0:00:00) # Start vms: Success (in 0:00:00) @ Start Prefix: Success (in 0:00:06) + cd - /home/pdm/ovirt-system-tests + env_deploy + echo '#########################' ######################### + cd /home/pdm/ovirt-system-tests/deployment-basic-suite-master + lago ovirt deploy @ Deploy oVirt environment: # Deploy environment: * [Thread-2] Deploy VM lago-basic-suite-master-host0: * [Thread-3] Deploy VM lago-basic-suite-master-engine: * [Thread-4] Deploy VM lago-basic-suite-master-host1: - STDERR ++ uname -r ++ sed -r 's/^.*\.([^\.]+)\.[^\.]+$/\1/' + DIST=el7 ++ ip -4 addr show scope global up ++ awk '{split($4,a,"."); print a[1] "." a[2] "." a[3] ".1"}' ++ grep -m1 inet + ADDR=192.168.200.1 + cat + sed -i 's/var\/cache/dev\/shm/g' /etc/yum.conf + echo persistdir=/dev/shm + yum install '--disablerepo=*' --enablerepo=alocalsync -y yum-utils Error: Package: yum-utils-1.1.31-40.el7.noarch (alocalsync) Requires: libxml2-python Error: Package: yum-utils-1.1.31-40.el7.noarch (alocalsync) Requires: yum >= 3.4.3-143 Installed: yum-3.4.3-132.el7.centos.0.1.noarch (installed) yum = 3.4.3-132.el7.centos.0.1 * [Thread-2] Deploy VM lago-basic-suite-master-host0: ERROR (in 0:00:35) Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1242, in _deploy_host host.name(), RuntimeError: /var/lib/lago/ovirt-system-tests/deployment-basic-suite-master/default/scripts/_var_lib_lago_ovirt-system-tests_basic-suite-master_.._common_deploy-scripts_add_local_repo.sh failed with status 1 on lago-basic-suite-master-host0 - STDERR ++ uname -r ++ sed -r 's/^.*\.([^\.]+)\.[^\.]+$/\1/' + DIST=el7 ++ ip -4 addr show scope global up ++ grep -m1 inet ++ awk '{split($4,a,"."); print a[1] "." a[2] "." a[3] ".1"}' + ADDR=192.168.200.1 + cat + sed -i 's/var\/cache/dev\/shm/g' /etc/yum.conf + echo persistdir=/dev/shm + yum install '--disablerepo=*' --enablerepo=alocalsync -y yum-utils Error: Package: yum-utils-1.1.31-40.el7.noarch (alocalsync) Requires: libxml2-python Error: Package: yum-utils-1.1.31-40.el7.noarch (alocalsync) Requires: yum >= 3.4.3-143 Installed: yum-3.4.3-132.el7.centos.0.1.noarch (installed) yum = 3.4.3-132.el7.centos.0.1 * [Thread-3] Deploy VM lago-basic-suite-master-engine: ERROR (in 0:00:37) Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1242, in _deploy_host host.name(), RuntimeError: /var/lib/lago/ovirt-system-tests/deployment-basic-suite-master/default/scripts/_var_lib_lago_ovirt-system-tests_basic-suite-master_.._common_deploy-scripts_add_local_repo.sh failed with status 1 on lago-basic-suite-master-engine - STDERR ++ uname -r ++ sed -r 's/^.*\.([^\.]+)\.[^\.]+$/\1/' + DIST=el7 ++ ip -4 addr show scope global up ++ awk '{split($4,a,"."); print a[1] "." a[2] "." a[3] ".1"}' ++ grep -m1 inet + ADDR=192.168.200.1 + cat + sed -i 's/var\/cache/dev\/shm/g' /etc/yum.conf + echo persistdir=/dev/shm + yum install '--disablerepo=*' --enablerepo=alocalsync -y yum-utils Error: Package: yum-utils-1.1.31-40.el7.noarch (alocalsync) Requires: libxml2-python Error: Package: yum-utils-1.1.31-40.el7.noarch (alocalsync) Requires: yum >= 3.4.3-143 Installed: yum-3.4.3-132.el7.centos.0.1.noarch (installed) yum = 3.4.3-132.el7.centos.0.1 * [Thread-4] Deploy VM lago-basic-suite-master-host1: ERROR (in 0:00:37) Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1242, in _deploy_host host.name(), RuntimeError: /var/lib/lago/ovirt-system-tests/deployment-basic-suite-master/default/scripts/_var_lib_lago_ovirt-system-tests_basic-suite-master_.._common_deploy-scripts_add_local_repo.sh failed with status 1 on lago-basic-suite-master-host1 # Deploy environment: ERROR (in 0:00:37) @ Deploy oVirt environment: ERROR (in 0:00:37) Error occured, aborting Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 264, in do_run self.cli_plugins[args.ovirtverb].do_run(args) File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run self._do_run(**vars(args)) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 489, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 500, in wrapper return func(*args, prefix=prefix, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 187, in do_deploy prefix.deploy() File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 621, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line 67, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 198, in deploy return super(OvirtPrefix, self).deploy() File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 621, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1249, in deploy self._deploy_host, self.virt_env.get_vms().values() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 97, in invoke_in_parallel vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1242, in _deploy_host host.name(), RuntimeError: /var/lib/lago/ovirt-system-tests/deployment-basic-suite-master/default/scripts/_var_lib_lago_ovirt-system-tests_basic-suite-master_.._common_deploy-scripts_add_local_repo.sh failed with status 1 on lago-basic-suite-master-host0 When I try to rerun the suite, I receive a different error: $ cd deployment-basic-suite-master/ $ lagocli cleanup @ Cleanup prefix: # Stop prefix: # Stop prefix: * Stop vms: * Stop vms: Success (in 0:00:00) * Stop nets: * Stop nets: Success (in 0:00:00) # Stop prefix: Success (in 0:00:00) # Tag prefix as uninitialized: # Tag prefix as uninitialized: Success (in 0:00:00) @ Cleanup prefix: Success (in 0:00:00) $ cd .. $ ./run_suite.sh basic-suite-master + CLI=lago + DO_CLEANUP=false + RECOMMENDED_RAM_IN_MB=8196 + EXTRA_SOURCES=() ++ getopt -o ho:e:n:b:cs:r: --long help,output:,engine:,node:,boot-iso:,cleanup --long extra-rpm-source,reposync-config: -n run_suite.sh -- basic-suite-master + options=' -- '\''basic-suite-master'\''' + [[ 0 != \0 ]] + eval set -- ' -- '\''basic-suite-master'\''' ++ set -- -- basic-suite-master + true + case $1 in + shift + break + [[ -z basic-suite-master ]] ++ realpath basic-suite-master + export SUITE=/var/lib/lago/ovirt-system-tests/basic-suite-master + SUITE=/var/lib/lago/ovirt-system-tests/basic-suite-master + '[' -z '' ']' + export PREFIX=/home/pdm/ovirt-system-tests/deployment-basic-suite-master + PREFIX=/home/pdm/ovirt-system-tests/deployment-basic-suite-master + false + [[ -d /var/lib/lago/ovirt-system-tests/basic-suite-master ]] + echo '################# lago version' ################# lago version + lago --version lago 0.28.0 + echo '#################' ################# + check_ram 8196 + local recommended=8196 ++ free -m ++ grep Mem ++ awk '{print $2}' + local cur_ram=7822 + [[ 7822 -lt 8196 ]] + echo 'It'\''s recommended to have at least 8196MB of RAM' 'installed on the system to run the system tests, if you find' 'issues while running them, consider upgrading your system.' '(only detected 7822MB installed)' It's recommended to have at least 8196MB of RAM installed on the system to run the system tests, if you find issues while running them, consider upgrading your system. (only detected 7822MB installed) + echo 'Running suite found in /var/lib/lago/ovirt-system-tests/basic-suite-master' Running suite found in /var/lib/lago/ovirt-system-tests/basic-suite-master + echo 'Environment will be deployed at /home/pdm/ovirt-system-tests/deployment-basic-suite-master' Environment will be deployed at /home/pdm/ovirt-system-tests/deployment-basic-suite-master + rm -rf /home/pdm/ovirt-system-tests/deployment-basic-suite-master + source /var/lib/lago/ovirt-system-tests/basic-suite-master/control.sh + prep_suite '' '' '' + local suite_name=basic-suite-master + suite_name=basic-suite-master + sed -r -e s,__ENGINE__,lago-basic-suite-master-engine,g -e 's,__HOST([0-9]+)__,lago-basic-suite-master-host\1,g' -e s,__LAGO_NET__,lago-basic-suite-master-lago,g -e s,__STORAGE__,lago-basic-suite-master-storage,g + run_suite + env_init '' /var/lib/lago/ovirt-system-tests/basic-suite-master/LagoInitFile + echo '#########################' ######################### + local template_repo=/var/lib/lago/ovirt-system-tests/basic-suite-master/template-repo.json + local initfile=/var/lib/lago/ovirt-system-tests/basic-suite-master/LagoInitFile + lago init /home/pdm/ovirt-system-tests/deployment-basic-suite-master /var/lib/lago/ovirt-system-tests/basic-suite-master/LagoInitFile --template-repo-path /var/lib/lago/ovirt-system-tests/basic-suite-master/template-repo.json @ Initialize and populate prefix: # Initialize prefix: * Create prefix dirs: * Create prefix dirs: Success (in 0:00:00) * Generate prefix uuid: * Generate prefix uuid: Success (in 0:00:00) * Create ssh keys: * Create ssh keys: Success (in 0:00:00) * Tag prefix as initialized: * Tag prefix as initialized: Success (in 0:00:00) # Initialize prefix: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-host0: * Create disk root: * Create disk root: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-host0: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-engine: * Create disk root: * Create disk root: Success (in 0:00:00) * Create disk nfs: * Create disk nfs: Success (in 0:00:00) * Create disk export: * Create disk export: Success (in 0:00:00) * Create disk iscsi: * Create disk iscsi: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-engine: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-host1: * Create disk root: * Create disk root: Success (in 0:00:00) # Create disks for VM lago-basic-suite-master-host1: Success (in 0:00:00) # Copying any deploy scripts: # Copying any deploy scripts: Success (in 0:00:00) # [Thread-1] Bootstrapping lago-basic-suite-master-host0: # [Thread-2] Bootstrapping lago-basic-suite-master-engine: # [Thread-3] Bootstrapping lago-basic-suite-master-host1: # [Thread-1] Bootstrapping lago-basic-suite-master-host0: Success (in 0:00:16) # [Thread-3] Bootstrapping lago-basic-suite-master-host1: Success (in 0:00:17) # [Thread-2] Bootstrapping lago-basic-suite-master-engine: Success (in 0:00:17) # Save prefix: * Save nets: * Save nets: Success (in 0:00:00) * Save VMs: * Save VMs: Success (in 0:00:00) * Save env: * Save env: Success (in 0:00:00) # Save prefix: Success (in 0:00:00) @ Initialize and populate prefix: Success (in 0:00:18) + env_repo_setup + echo '#########################' ######################### + local extrasrc + declare -a extrasrcs + cd /home/pdm/ovirt-system-tests/deployment-basic-suite-master + local reposync_conf=/var/lib/lago/ovirt-system-tests/basic-suite-master/reposync-config.repo + [[ -e '' ]] + echo 'using reposync config file: /var/lib/lago/ovirt-system-tests/basic-suite-master/reposync-config.repo' using reposync config file: /var/lib/lago/ovirt-system-tests/basic-suite-master/reposync-config.repo + lago ovirt reposetup --reposync-yum-config /var/lib/lago/ovirt-system-tests/basic-suite-master/reposync-config.repo @ Create prefix internal repo: # Syncing remote repos locally (this might take some time): * Acquiring lock for /var/lib/lago/reposync/repolock: * Acquiring lock for /var/lib/lago/reposync/repolock: Success (in 0:00:00) * Running reposync: * Running reposync: Success (in 0:00:06) # Syncing remote repos locally (this might take some time): Success (in 0:00:06) # Running repoman: # Running repoman: Success (in 0:00:05) # Save prefix: * Save nets: * Save nets: Success (in 0:00:00) * Save VMs: * Save VMs: Success (in 0:00:00) * Save env: * Save env: Success (in 0:00:00) # Save prefix: Success (in 0:00:00) @ Create prefix internal repo: Success (in 0:00:12) + cd - /home/pdm/ovirt-system-tests + env_start + echo '#########################' ######################### + cd /home/pdm/ovirt-system-tests/deployment-basic-suite-master + lago start @ Start Prefix: # Start nets: * Create network lago-basic-suite-master-lago: libvirt: error : internal error: Network is already in use by interface 2584-2e38ffa * Create network lago-basic-suite-master-lago: ERROR (in 0:00:00) # Start nets: ERROR (in 0:00:00) @ Start Prefix: ERROR (in 0:00:00) Error occured, aborting Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 822, in main cli_plugins[args.verb].do_run(args) File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run self._do_run(**vars(args)) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 489, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 500, in wrapper return func(*args, prefix=prefix, **kwargs) File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 258, in do_start prefix.start(vm_names=vm_names) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 949, in start self.virt_env.start(vm_names=vm_names) File "/usr/lib/python2.7/site-packages/lago/virt.py", line 186, in start net.start() File "/usr/lib/python2.7/site-packages/lago/virt.py", line 358, in start self.libvirt_con.networkCreateXML(self._libvirt_xml()) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4262, in networkCreateXML if ret is None:raise libvirtError('virNetworkCreateXML() failed', conn=self) libvirtError: internal error: Network is already in use by interface 2584-2e38ffa

2 1

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job
by Barak Korren (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-926: ------------------------------------ My thesis was wrong, this is the end of the cleanup code: {code} if $failed; then echo "Cleanup script failed, propegating failure to job" exit 1 fi {code} The following simple test shows that this kind of code indeed results in what we're seeing in the log, and also does not result in a non-zero return value: {code} $ (set -x ; failed=false; if $failed; then echo FAILED; fi); echo $? + failed=false + false 0 {code} So we need to keep looking... > check why 3.6 experimental job failed even if not error in shown on job > ----------------------------------------------------------------------- > > Key: OVIRT-926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/ > [~gbenhaim@redhat.com][~ngoldin@redhat.com][~ederevea][~bkorren@redhat.com] any ideas? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

Can't resolve maven-checkstyle-plugin el7 for vdsm-jsonrpc
by Roy Golan 12 Dec '16

12 Dec '16

This patch [1] adds maven-checkstyle plugin for project vdsm-jsonrpc but it keep complaining [2] it can't resolve it . The plugin is the same version, 2.9.1 as ovirt engine uses. The F24 build is passing. What am I missing here? [1] https://gerrit.ovirt.org/67990 [2] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_check-patch-el7-x86_6…

4 6

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job
by Barak Korren (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-926: ------------------------------------ I'm seeing this in the end of the cleanup script: {quote} 18:35:39 + false {quote} So maybe its returning a false value that gets returned up the groovy stack (the groovy code seems to imply that 'sh' will throw an exception on script failure, but maybe that is not the case) Will need to write some simple Groovy jobs to understand this. > check why 3.6 experimental job failed even if not error in shown on job > ----------------------------------------------------------------------- > > Key: OVIRT-926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/ > [~gbenhaim@redhat.com][~ngoldin@redhat.com][~ederevea][~bkorren@redhat.com] any ideas? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-933) Fix repoproxy service and logging mess
by Evgheni Dereveanchin (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-933: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Fix repoproxy service and logging mess > -------------------------------------- > > Key: OVIRT-933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > > There are a couple of issues with the way repoproxy runs right now, these issues probably cause it to be less stable then it can: > # repoproxy is can currently be invoked only from puppet, because a lot of the data on how to run it is stored right now in puppet and nowhere else. We should make puppet create a systemd unit file to run repoproxy instead of running it itself. This way we can get rid of the cron job that runs puppet every 2 minutes on the proxy. > # repoproxy is configured to run as the '{{squid}}' user and log to '{{/var/log/repoproxy.log}}'. That file is pre-created with the right permissions bu Puppet so repoproxy can write to it. However, the Python logger in repoproxy is configured to try and rotate the log when it becomes too big. That, in turn, will cause it to crash because the '{{squid}}' user cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere else. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-933) Fix repoproxy service and logging mess
by eyal edri [Administrator] (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-933: ------------------------------------------------- [~ederevea] didn't we disable or stopped using the repo proxy? I remember another ticket on it. > Fix repoproxy service and logging mess > -------------------------------------- > > Key: OVIRT-933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: High > > There are a couple of issues with the way repoproxy runs right now, these issues probably cause it to be less stable then it can: > # repoproxy is can currently be invoked only from puppet, because a lot of the data on how to run it is stored right now in puppet and nowhere else. We should make puppet create a systemd unit file to run repoproxy instead of running it itself. This way we can get rid of the cron job that runs puppet every 2 minutes on the proxy. > # repoproxy is configured to run as the '{{squid}}' user and log to '{{/var/log/repoproxy.log}}'. That file is pre-created with the right permissions bu Puppet so repoproxy can write to it. However, the Python logger in repoproxy is configured to try and rotate the log when it becomes too big. That, in turn, will cause it to crash because the '{{squid}}' user cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere else. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-933) Fix repoproxy service and logging mess
by Yaniv Kaul (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.p… ] Yaniv Kaul updated OVIRT-933: ----------------------------- Priority: High (was: Medium) > Fix repoproxy service and logging mess > -------------------------------------- > > Key: OVIRT-933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: High > > There are a couple of issues with the way repoproxy runs right now, these issues probably cause it to be less stable then it can: > # repoproxy is can currently be invoked only from puppet, because a lot of the data on how to run it is stored right now in puppet and nowhere else. We should make puppet create a systemd unit file to run repoproxy instead of running it itself. This way we can get rid of the cron job that runs puppet every 2 minutes on the proxy. > # repoproxy is configured to run as the '{{squid}}' user and log to '{{/var/log/repoproxy.log}}'. That file is pre-created with the right permissions bu Puppet so repoproxy can write to it. However, the Python logger in repoproxy is configured to try and rotate the log when it becomes too big. That, in turn, will cause it to crash because the '{{squid}}' user cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere else. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-933) Fix repoproxy service and logging mess
by Yaniv Kaul (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.p… ] Yaniv Kaul commented on OVIRT-933: ---------------------------------- Moving priority to High, based on 'will cause it to crash' statement above. > Fix repoproxy service and logging mess > -------------------------------------- > > Key: OVIRT-933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: High > > There are a couple of issues with the way repoproxy runs right now, these issues probably cause it to be less stable then it can: > # repoproxy is can currently be invoked only from puppet, because a lot of the data on how to run it is stored right now in puppet and nowhere else. We should make puppet create a systemd unit file to run repoproxy instead of running it itself. This way we can get rid of the cron job that runs puppet every 2 minutes on the proxy. > # repoproxy is configured to run as the '{{squid}}' user and log to '{{/var/log/repoproxy.log}}'. That file is pre-created with the right permissions bu Puppet so repoproxy can write to it. However, the Python logger in repoproxy is configured to try and rotate the log when it becomes too big. That, in turn, will cause it to crash because the '{{squid}}' user cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere else. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-933) Fix repoproxy service and logging mess
by Barak Korren (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-933: ------------------------------- Summary: Fix repoproxy service and logging mess (was: Fixe repoproxy service and logging mess) > Fix repoproxy service and logging mess > -------------------------------------- > > Key: OVIRT-933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > > There are a couple of issues with the way repoproxy runs right now, these issues probably cause it to be less stable then it can: > # repoproxy is can currently be invoked only from puppet, because a lot of the data on how to run it is stored right now in puppet and nowhere else. We should make puppet create a systemd unit file to run repoproxy instead of running it itself. This way we can get rid of the cron job that runs puppet every 2 minutes on the proxy. > # repoproxy is configured to run as the '{{squid}}' user and log to '{{/var/log/repoproxy.log}}'. That file is pre-created with the right permissions bu Puppet so repoproxy can write to it. However, the Python logger in repoproxy is configured to try and rotate the log when it becomes too big. That, in turn, will cause it to crash because the '{{squid}}' user cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere else. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by Evgheni Dereveanchin (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-931: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > profile why ovirt-engine check-patch takes between 10-50 min > ------------------------------------------------------------- > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-933) Fixe repoproxy service and logging mess
by Barak Korren (oVirt JIRA) 12 Dec '16

12 Dec '16

Barak Korren created OVIRT-933: ---------------------------------- Summary: Fixe repoproxy service and logging mess Key: OVIRT-933 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Barak Korren Assignee: infra There are a couple of issues with the way repoproxy runs right now, these issues probably cause it to be less stable then it can: # repoproxy is can currently be invoked only from puppet, because a lot of the data on how to run it is stored right now in puppet and nowhere else. We should make puppet create a systemd unit file to run repoproxy instead of running it itself. This way we can get rid of the cron job that runs puppet every 2 minutes on the proxy. # repoproxy is configured to run as the '{{squid}}' user and log to '{{/var/log/repoproxy.log}}'. That file is pre-created with the right permissions bu Puppet so repoproxy can write to it. However, the Python logger in repoproxy is configured to try and rotate the log when it becomes too big. That, in turn, will cause it to crash because the '{{squid}}' user cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere else. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-933) Fixe repoproxy service and logging mess
by Barak Korren (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-933: ------------------------------- Epic Link: OVIRT-403 > Fixe repoproxy service and logging mess > --------------------------------------- > > Key: OVIRT-933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > > There are a couple of issues with the way repoproxy runs right now, these issues probably cause it to be less stable then it can: > # repoproxy is can currently be invoked only from puppet, because a lot of the data on how to run it is stored right now in puppet and nowhere else. We should make puppet create a systemd unit file to run repoproxy instead of running it itself. This way we can get rid of the cron job that runs puppet every 2 minutes on the proxy. > # repoproxy is configured to run as the '{{squid}}' user and log to '{{/var/log/repoproxy.log}}'. That file is pre-created with the right permissions bu Puppet so repoproxy can write to it. However, the Python logger in repoproxy is configured to try and rotate the log when it becomes too big. That, in turn, will cause it to crash because the '{{squid}}' user cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere else. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

Build failed in Jenkins: ovirt_4.0_system-tests #733
by jenkins＠jenkins.phx.ovirt.org 12 Dec '16

12 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/733/changes> Changes: [Your Name] basic networking: modify ip config to dhcp [Barak Korren] Add http_proxy env var to proxied mock envs ------------------------------------------ [...truncated 632 lines...] ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.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 230 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/hudson7138590860841628533.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/733/artifact/exported-a…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/733/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/733/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 -x 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 # 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" # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then for log in "${logs[@]}"; do [[ "$log" = ./exported-artifacts/* ]] && continue 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 # remove mock caches that are older then 2 days: find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 | \ xargs -0 -tr sudo rm -rf # We make no effort to leave around caches that may still be in use because # packages installed in them may go out of date, so may as well recreate them # 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 if $failed; then echo "Cleanup script failed, propegating failure to job" exit 1 fi [ovirt_4.0_system-tests] $ /bin/bash -x /tmp/hudson6396308667636953382.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 # # # ####################################################################### + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/> + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + for log in '"${logs[@]}"' + [[ ./ovirt-system-tests/logs = ./exported-artifacts/* ]] + 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_system-tests/ws/ovirt-system-tests/m…> ]] + 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_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_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-epel-7-x86_64.el7 --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.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_system-tests/ws/ovirt-system-tests/m…> + mock_root=epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e + [[ -n epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-ed452d1ea0f6dadf50c66d3b3f6b3a6e + : + [[ -n '' ]] + find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 + xargs -0 -tr sudo rm -rf ++ virsh list --all --uuid + false POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Archiving artifacts

2 5

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4471 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Dec '16

12 Dec '16

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

1 1

oVirt infra daily report - unstable production jobs - 165
by jenkins＠jenkins.phx.ovirt.org 12 Dec '16

12 Dec '16

------=_Part_115_940422232.1481497205899 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/165//artifact/exported-a… Cheers, Jenkins ------=_Part_115_940422232.1481497205899 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 11/12/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_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-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_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-guest-agent_master_build-artifacts-el6-x…">ovirt-guest-agent_master_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-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-hosted-engine-ha_3.6_create-rpms-el7-x86…">ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_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-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_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-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_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-4.1-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.1-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-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-node_ovirt-3.6_create-iso-el7_merged/">ovirt-node_ovirt-3.6_create-iso-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-optimizer_4.0_build-artifacts-el6-x86_64/">ovirt-optimizer_4.0_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_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_4.0_system-tests/">ovirt_4.0_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.0_check-closure_el7_merged/">repos_4.0_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_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/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_115_940422232.1481497205899--

1 0

Re: [ovirt-devel] 4.0.x dependency failure (vdsm-jsonrpc-java)
by Eyal Edri 11 Dec '16

11 Dec '16

Adding infra as well. I see a very strange thing happening on the build artifacts jobs: On [1] we see a successful build of 1.2.10 built in build-artifacts, but on the 2 patches merged after it, its back to 1.2.9 [2]. Is it possible that the 2 patches merged after the version bump weren't rebased on the version branch and were built using older code? I think what we're seeing is a race of 3 patches merged all at the same time ( jenkins shows same datetime on the builds ) and it might be that the 2 builds that show older version run before the version bump was done, even if it shows otherwise on CI. I've run manually the job again and it nows produces 1.2.10 as expected [3], so the job should work once the rpms are deployed ( 30 min ~ ) I believe this is one of the things Zuul will solve, I can't think on something we can do at the moment to prevents such issues, Barak - any ideas? The project has 'fast forward only' mode in Gerrit. [1] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_… [2] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_… [3] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_… On Sun, Dec 11, 2016 at 11:01 AM, Piotr Kliczewski <pkliczew(a)redhat.com> wrote: > Yes, version bump was merged. > > 11 gru 2016 09:57 "Eyal Edri" <eedri(a)redhat.com> napisał(a): > >> Was the version bumped pushed to the repo itself in Gerrit? >> I.e - does build-artifacts builds now the new version 1.2.10? >> >> On Fri, Dec 9, 2016 at 9:33 PM, Sandro Bonazzola <sbonazzo(a)redhat.com> >> wrote: >> >>> >>> >>> Il 09/Dic/2016 18:45, "Piotr Kliczewski" <pkliczew(a)redhat.com> ha >>> scritto: >>> >>> Here [1] is the manual build. We need to check publisher. >>> >>> >>> >>> Manual builds are not published by nightly publisher. Manual builds are >>> meant for releases or for testing. I haven't the laptop with me tonight and >>> tomorrow. Didi, Lev can you handle Sunday morning? >>> >>> >>> >>> >>> Thanks, >>> Piotr >>> >>> [1] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_any_build >>> -artifacts-manual/30/ >>> >>> 9 gru 2016 18:36 "Piotr Kliczewski" <pkliczew(a)redhat.com> napisał(a): >>> >>>> Both us and ds rpms were built. Is it possible to check why new version >>>> was not published to the repo? >>>> >>>> 9 gru 2016 18:07 "Martin Perina" <mperina(a)redhat.com> napisał(a): >>>> >>>>> Piotr, are you able to publish new vdsm-jsonrpc-java 1.2.10 into >>>>> ovirt-4.0-snapshot repo [1]? Or only someone from integration team can do >>>>> that? >>>>> >>>>> Thanks >>>>> >>>>> Martin >>>>> >>>>> [1] http://plain.resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm >>>>> >>>>> >>>>> On Fri, Dec 9, 2016 at 4:54 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: >>>>> >>>>>> See [1]: >>>>>> >>>>>> + yum install --nogpgcheck -y --downloaddir=/dev/shm ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*'*13:55:25* Error: Package: ovirt-engine-backend-4.0.7-0.0.master.20161208233116.git3dff5ce.el7.centos.noarch (alocalsync)*13:55:25* Requires: vdsm-jsonrpc-java >= 1.2.10*13:55:25* Available: vdsm-jsonrpc-java-1.2.9-1.20161208102442.gite5c0c8e.el7.centos.noarch (alocalsync)*13:55:25* vdsm-jsonrpc-java = 1.2.9-1.20161208102442.gite5c0c8e.el7.centos >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> [1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Devel mailing list >>>>>> Devel(a)ovirt.org >>>>>> http://lists.phx.ovirt.org/mailman/listinfo/devel >>>>>> >>>>> >>>>> >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.phx.ovirt.org/mailman/listinfo/devel >>> >>> >>> >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.phx.ovirt.org/mailman/listinfo/devel >>> >> >> >> >> -- >> 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) >> > -- 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)

4 7

[JIRA] (OVIRT-932) Wrong Lago version used in CI
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-932?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-932: ----------------------------------------------- Assignee: Gal Ben Haim (was: infra) According to [~bkorren(a)redhat.com] the new changed in mock cache should cause this. Any idea where else it can come from? We cleared the mock cache also on the ovirt-srv22 server, and I now rerun the job to see if it works. > Wrong Lago version used in CI > ----------------------------- > > Key: OVIRT-932 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Yaniv Kaul > Assignee: Gal Ben Haim > Priority: High > > See http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… : > Error: package lago-ovirt-0.23.0-1.fc24.noarch requires python-lago-ovirt = 0.23.0, but none of the providers can be installed > It should use v0.28. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-932) Wrong Lago version used in CI
by Yaniv Kaul (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-932?page=com.atlassian.jira.p… ] Yaniv Kaul updated OVIRT-932: ----------------------------- Epic Link: OVIRT-400 > Wrong Lago version used in CI > ----------------------------- > > Key: OVIRT-932 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Yaniv Kaul > Assignee: infra > Priority: High > > See http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… : > Error: package lago-ovirt-0.23.0-1.fc24.noarch requires python-lago-ovirt = 0.23.0, but none of the providers can be installed > It should use v0.28. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-932) Wrong Lago version used in CI
by Yaniv Kaul (oVirt JIRA) 11 Dec '16

11 Dec '16

Yaniv Kaul created OVIRT-932: -------------------------------- Summary: Wrong Lago version used in CI Key: OVIRT-932 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Yaniv Kaul Assignee: infra Priority: High See http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… : Error: package lago-ovirt-0.23.0-1.fc24.noarch requires python-lago-ovirt = 0.23.0, but none of the providers can be installed It should use v0.28. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

Bug moved to MODIFIED by hook while patches are not all in.
by Yaniv Dary 11 Dec '16

11 Dec '16

Hi, Can you have a look? https://bugzilla.redhat.com/show_bug.cgi?id=827529# This bug moved to MODIFIED by hook while patches are not all in. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary(a)redhat.com IRC : ydary

3 3

Moving NGN system tests to fc24/fc25
by Eyal Edri 11 Dec '16

11 Dec '16

Hi, We're looking to move away from fc23 before it stops working, I see that the ngn system tests still uses it, do we know if it can move to fc24/fc25? I remember el7 wasn't possible when we moved it from fc22. [1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_4.0_image-ng… -- 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)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-931: ------------------------------------------------- [~gshinar] thanks for the quick debug, [~ederevea] can we have a list of "problematic hypervisors"? we might want to move them to Lago or production DC. > profile why ovirt-engine check-patch takes between 10-50 min > ------------------------------------------------------------- > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by Gil Shinar (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-931: ---------------------------------- I have checked two different slaves. One usually takes long 50~ minutes and the other one usually takes 10~ minutes. The one that takes 10~ minutes has 16 cores CPU and the one that takes 50~ minutes has two cores CPU. On top of that, some builds run dao tests and some don't (depend on files that had been changed. > profile why ovirt-engine check-patch takes between 10-50 min > ------------------------------------------------------------- > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4457 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Dec '16

11 Dec '16

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

1 1

hot plug disk test failed on system tests
by Eyal Edri 11 Dec '16

11 Dec '16

FYI, We're seeing a single test 'add hotplug disk' failing recently on OST, the test only failed once on the jobs [1] and was fixed on its own after one run, but now I see it also on check-patch [2] jobs. Looking at the changelog, I can't find immediate suspects, and if this is a race it might make sense it got in at some point and didn't fail on the 1st time. Anyone can have a look to help debug this? it also failed once on 4.0 job. I see some exceptions on VDSM.LOG [3] [1] http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… [2] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… [3] 2016-12-11 04:51:19,055 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.getDeviceList succeeded in 0.39 seconds (__init__:515) 2016-12-11 04:51:19,106 INFO (jsonrpc/5) [dispatcher] Run and protect: getAllTasksInfo(spUUID=None, options=None) (logUtils:49) 2016-12-11 04:51:19,106 ERROR (jsonrpc/5) [storage.TaskManager.Task] (Task='ef8d6b6f-256c-4420-9998-bef8a140a20f') Unexpected error (task:870) Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 877, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 50, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2193, in getAllTasksInfo allTasksInfo = self._pool.getAllTasksInfo() File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state 2016-12-11 04:51:19,109 INFO (jsonrpc/5) [storage.TaskManager.Task] (Task='ef8d6b6f-256c-4420-9998-bef8a140a20f') aborting: Task is aborted: u'Secured object is not in safe state' - code 100 (task:1175) 2016-12-11 04:51:19,109 ERROR (jsonrpc/5) [storage.Dispatcher] Secured object is not in safe state (dispatcher:80) Traceback (most recent call last): File "/usr/share/vdsm/storage/dispatcher.py", line 72, in wrapper result = ctask.prepare(func, *args, **kwargs) File "/usr/share/vdsm/storage/task.py", line 105, in wrapper return m(self, *a, **kw) File "/usr/share/vdsm/storage/task.py", line 1183, in prepare raise self.error second error: 2016-12-11 04:55:21,837 ERROR (libvirt/events) [vds] Error running VM callback (clientIF:543) Traceback (most recent call last): File "/usr/share/vdsm/clientIF.py", line 514, in dispatchLibvirtEvents v.onLibvirtLifecycleEvent(event, detail, None) File "/usr/share/vdsm/virt/vm.py", line 4318, in onLibvirtLifecycleEvent elif detail == libvirt.VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY: AttributeError: 'module' object has no attribute 'VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY' -- 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)

2 1

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job
by Gil Shinar (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-926: ---------------------------------- [~ngoldin(a)redhat.com] These warning are coming from the emailext plugin I have used to send emails on failures/success. They have nothing to do with this issue IMO. > check why 3.6 experimental job failed even if not error in shown on job > ----------------------------------------------------------------------- > > Key: OVIRT-926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/ > [~gbenhaim@redhat.com][~ngoldin@redhat.com][~ederevea][~bkorren@redhat.com] any ideas? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

eyal edri [Administrator] created OVIRT-931: ----------------------------------------------- Summary: profile why ovirt-engine check-patch takes between 10-50 min Key: OVIRT-931 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: High Same job sometimes takes little as 10 min but sometimes high as 50 min. We need to understand why. http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-931: -------------------------------------------- Epic Link: OVIRT-400 > profile why ovirt-engine check-patch takes between 10-50 min > ------------------------------------------------------------- > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-930) check why ost 4.0 failed on vm run job even though not change was done
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

eyal edri [Administrator] created OVIRT-930: ----------------------------------------------- Summary: check why ost 4.0 failed on vm run job even though not change was done Key: OVIRT-930 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-930 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Looks like false positive or race issue, but still needs to be debug for RCA. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3389/consoleF… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-930) check why ost 4.0 failed on vm run job even though not change was done
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-930?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-930: -------------------------------------------- Epic Link: OVIRT-400 > check why ost 4.0 failed on vm run job even though not change was done > ---------------------------------------------------------------------- > > Key: OVIRT-930 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-930 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > Looks like false positive or race issue, but still needs to be debug for RCA. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3389/consoleF… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job
by Nadav Goldin (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-926: ------------------------------------ {code} [Pipeline] node { [Pipeline] emailext Job type does not allow token replacement. Job type does not allow token replacement. Job type does not allow token replacement. Job type does not allow token replacement. Sending email to: infra(a)ovirt.org {code} I think these errors are new, might be related to the Jenkins plugin upgrade. > check why 3.6 experimental job failed even if not error in shown on job > ----------------------------------------------------------------------- > > Key: OVIRT-926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/ > [~gbenhaim@redhat.com][~ngoldin@redhat.com][~ederevea][~bkorren@redhat.com] any ideas? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-929) debug why 3.6 ost job failed on vm template test
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-929?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-929: -------------------------------------------- Epic Link: OVIRT-400 > debug why 3.6 ost job failed on vm template test > ------------------------------------------------ > > Key: OVIRT-929 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-929 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4428/consoleF… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-929) debug why 3.6 ost job failed on vm template test
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

eyal edri [Administrator] created OVIRT-929: ----------------------------------------------- Summary: debug why 3.6 ost job failed on vm template test Key: OVIRT-929 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-929 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4428/consoleF… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-928) check why ost failed on hot plug test while no code got in to break it
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-928?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-928: -------------------------------------------- Epic Link: OVIRT-400 > check why ost failed on hot plug test while no code got in to break it > ---------------------------------------------------------------------- > > Key: OVIRT-928 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-928 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0