- Infra - oVirt List Archives

[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

eyal edri [Administrator] created OVIRT-928: ----------------------------------------------- Summary: 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

[JIRA] (OVIRT-927) CHECK why ost failed on master snapshot merge test
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

eyal edri [Administrator] created OVIRT-927: ----------------------------------------------- Summary: CHECK why ost failed on master snapshot merge test Key: OVIRT-927 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-927 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

[JIRA] (OVIRT-927) CHECK why ost failed on master snapshot merge test
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-927?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-927: -------------------------------------------- Epic Link: OVIRT-400 > CHECK why ost failed on master snapshot merge test > -------------------------------------------------- > > Key: OVIRT-927 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-927 > 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

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

11 Dec '16

eyal edri [Administrator] created OVIRT-926: ----------------------------------------------- Summary: 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-926) check why 3.6 experimental job failed even if not error in shown on job
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-926: -------------------------------------------- Epic Link: OVIRT-400 > 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-925) OST job failed on workflow error
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-925?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-925: -------------------------------------------- Epic Link: OVIRT-400 > OST job failed on workflow error > -------------------------------- > > Key: OVIRT-925 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-925 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… > Need to find root cause. > Started by timer > org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: > WorkflowScript: 305: expecting '}', found '' @ line 305, column 1. > 1 error > at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:302) > at org.codehaus.groovy.control.ErrorCollector.addFatalError(ErrorCollector.java:149) > at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:119) > at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:131) > at org.codehaus.groovy.control.SourceUnit.addError(SourceUnit.java:359) > at org.codehaus.groovy.antlr.AntlrParserPlugin.transformCSTIntoAST(AntlrParserPlugin.java:142) > at org.codehaus.groovy.antlr.AntlrParserPlugin.parseCST(AntlrParserPlugin.java:108) > at org.codehaus.groovy.control.SourceUnit.parse(SourceUnit.java:236) > at org.codehaus.groovy.control.CompilationUnit$1.call(CompilationUnit.java:161) > at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:846) > at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:550) > at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:526) > at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:503) > at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:302) > at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:281) > at groovy.lang.GroovyShell.parseClass(GroovyShell.java:731) > at groovy.lang.GroovyShell.parse(GroovyShell.java:743) > at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:106) > at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:376) > at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:343) > at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:212) > at hudson.model.ResourceController.execute(ResourceController.java:98) > at hudson.model.Executor.run(Executor.java:410) > Finished: FAILURE -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-925) OST job failed on workflow error
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

eyal edri [Administrator] created OVIRT-925: ----------------------------------------------- Summary: OST job failed on workflow error Key: OVIRT-925 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-925 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… Need to find root cause. Started by timer org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 305: expecting '}', found '' @ line 305, column 1. 1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:302) at org.codehaus.groovy.control.ErrorCollector.addFatalError(ErrorCollector.java:149) at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:119) at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:131) at org.codehaus.groovy.control.SourceUnit.addError(SourceUnit.java:359) at org.codehaus.groovy.antlr.AntlrParserPlugin.transformCSTIntoAST(AntlrParserPlugin.java:142) at org.codehaus.groovy.antlr.AntlrParserPlugin.parseCST(AntlrParserPlugin.java:108) at org.codehaus.groovy.control.SourceUnit.parse(SourceUnit.java:236) at org.codehaus.groovy.control.CompilationUnit$1.call(CompilationUnit.java:161) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:846) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:550) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:526) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:503) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:302) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:281) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:731) at groovy.lang.GroovyShell.parse(GroovyShell.java:743) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:106) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:376) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:343) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:212) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Finished: FAILURE -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3512 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Dec '16

11 Dec '16

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

1 1

CentOS 7.3 coming on Monday
by Sandro Bonazzola 11 Dec '16

11 Dec '16

Johnny Hughes (@JohnnyCentOS) ha twittato alle 2:49 AM on Ven, Dic 09, 2016: @mundounixnet the final 7.3.1611 tree and ISOs is currently syncing to our mirrors. Release should happen in a day or two. Probably Monday (https://twitter.com/JohnnyCentOS/status/807039378929369089?s=03) Scarica l'app ufficiale di Twitter su https://twitter.com/download?s=13

1 0

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

11 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/815/changes> Changes: [Your Name] basic networking: modify ip config to dhcp ------------------------------------------ [...truncated 746 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 140 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/hudson3411026981389210617.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/815/artifact/exported-a…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/815/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/815/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/hudson1485929933292496700.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 1

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

11 Dec '16

------=_Part_93_234570683.1481410804885 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/164//artifact/exported-a… Cheers, Jenkins ------=_Part_93_234570683.1481410804885 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 - 10/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-engine_4.0_upgrade-from-4.0_el7_merged/">ovirt-engine_4.0_upgrade-from-4.0_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-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.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_3.6_system-tests/">ovirt_3.6_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_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/vdsm-jsonrpc-java_4.0_build-artifacts-fc23-x86…">vdsm-jsonrpc-java_4.0_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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_93_234570683.1481410804885--

1 0

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

10 Dec '16

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4428/, Build Number: 4428, Build Status: FAILURE

1 1

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

10 Dec '16

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

1 2

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

10 Dec '16

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

1 1

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

10 Dec '16

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

1 4

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3485 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 10 Dec '16

10 Dec '16

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

1 1

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

10 Dec '16

------=_Part_60_1652658389.1481324405925 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/163//artifact/exported-a… Cheers, Jenkins ------=_Part_60_1652658389.1481324405925 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 - 09/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-engine_4.0_upgrade-from-4.0_el7_merged/">ovirt-engine_4.0_upgrade-from-4.0_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-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.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/vdsm-jsonrpc-java_4.0_build-artifacts-fc23-x86…">vdsm-jsonrpc-java_4.0_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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_60_1652658389.1481324405925--

1 0

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

09 Dec '16

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

1 1

Re: [ovirt-devel] 4.0.x dependency failure (vdsm-jsonrpc-java)
by Martin Perina 09 Dec '16

09 Dec '16

Sandro is on PTO, so adding infra ... On Fri, Dec 9, 2016 at 6:56 PM, Martin Perina <mperina(a)redhat.com> wrote: > Adding Sandro ... > > On Fri, Dec 9, 2016 at 6:45 PM, Piotr Kliczewski <pkliczew(a)redhat.com> > wrote: > >> Here [1] is the manual build. We need to check publisher. >> >> 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 >>>>> >>>> >>>> >

1 0

planned restart of Icinga and Foreman
by Evgheni Dereveanchin 09 Dec '16

09 Dec '16

Hi everyone, Today I'll update the OS and reboot the following servers: monitoring.ovirt.org foreman.ovirt.org As this will involve rebooting the Icinga service, some false positive alerts may be triggered so sorry for any inconvenience. The Foreman interface will also be unreachable for a period of time. This will not affect any existing CI workloads. Regards, Evgheni Dereveanchin

1 1

[JIRA] (OVIRT-924) 3.6 DAO tests failing due to missing postgres
by eyal edri [Administrator] (oVirt JIRA) 09 Dec '16

09 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-924?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-924: ------------------------------------------------- we need to remove those jobs. any logic needed can be implemented in check patch and iirc already is in master and 4.0 On Dec 9, 2016 12:03, "Evgheni Dereveanchin (oVirt JIRA)" < jira(a)ovirt-jira.atlassian.net> wrote: Evgheni Dereveanchin created OVIRT-924: ------------------------------------------ Summary: 3.6 DAO tests failing due to missing postgres Key: OVIRT-924 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-924 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Postgres was removed from Jenkins slaves as part of OVIRT-593 and we expect that all jobs install packages they need at runtime. Yet, 3.6 DAO tests are still expecting postgres on slaves: http://jenkins.ovirt.org/job/ovirt-engine_3.6_dao-unit-tests_created 08:53:26 /home/jenkins/workspace/ovirt-engine_3.6_dao-unit-tests_created 08:53:26 + sudo -u postgres psql -d template1 -c 'create role engine;' 08:53:26 sudo: unknown user: postgres 08:53:26 sudo: unable to initialize policy plugin The job needs to be updated. -- This message was sent by Atlassian JIRA (v1000.620.0#100023) > 3.6 DAO tests failing due to missing postgres > --------------------------------------------- > > Key: OVIRT-924 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-924 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > Postgres was removed from Jenkins slaves as part of OVIRT-593 and we expect that all jobs install packages they need at runtime. > Yet, 3.6 DAO tests are still expecting postgres on slaves: > http://jenkins.ovirt.org/job/ovirt-engine_3.6_dao-unit-tests_created > 08:53:26 /home/jenkins/workspace/ovirt-engine_3.6_dao-unit-tests_created > 08:53:26 + sudo -u postgres psql -d template1 -c 'create role engine;' > 08:53:26 sudo: unknown user: postgres > 08:53:26 sudo: unable to initialize policy plugin > The job needs to be updated. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

Re: [JIRA] (OVIRT-924) 3.6 DAO tests failing due to missing postgres
by Eyal Edri 09 Dec '16

09 Dec '16

we need to remove those jobs. any logic needed can be implemented in check patch and iirc already is in master and 4.0 On Dec 9, 2016 12:03, "Evgheni Dereveanchin (oVirt JIRA)" < jira(a)ovirt-jira.atlassian.net> wrote: Evgheni Dereveanchin created OVIRT-924: ------------------------------------------ Summary: 3.6 DAO tests failing due to missing postgres Key: OVIRT-924 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-924 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Postgres was removed from Jenkins slaves as part of OVIRT-593 and we expect that all jobs install packages they need at runtime. Yet, 3.6 DAO tests are still expecting postgres on slaves: http://jenkins.ovirt.org/job/ovirt-engine_3.6_dao-unit-tests_created 08:53:26 /home/jenkins/workspace/ovirt-engine_3.6_dao-unit-tests_created 08:53:26 + sudo -u postgres psql -d template1 -c 'create role engine;' 08:53:26 sudo: unknown user: postgres 08:53:26 sudo: unable to initialize policy plugin The job needs to be updated. -- This message was sent by Atlassian JIRA (v1000.620.0#100023) _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra

1 0

[JIRA] (OVIRT-924) 3.6 DAO tests failing due to missing postgres
by Evgheni Dereveanchin (oVirt JIRA) 09 Dec '16

09 Dec '16

Evgheni Dereveanchin created OVIRT-924: ------------------------------------------ Summary: 3.6 DAO tests failing due to missing postgres Key: OVIRT-924 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-924 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Postgres was removed from Jenkins slaves as part of OVIRT-593 and we expect that all jobs install packages they need at runtime. Yet, 3.6 DAO tests are still expecting postgres on slaves: http://jenkins.ovirt.org/job/ovirt-engine_3.6_dao-unit-tests_created 08:53:26 /home/jenkins/workspace/ovirt-engine_3.6_dao-unit-tests_created 08:53:26 + sudo -u postgres psql -d template1 -c 'create role engine;' 08:53:26 sudo: unknown user: postgres 08:53:26 sudo: unable to initialize policy plugin The job needs to be updated. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

DAO failures for 3.6 builds
by Martin Perina 09 Dec '16

09 Dec '16

Hi, DAO tests on 3.6 branch are currently broken due to following issues: *16:11:09* + DB_NAME=ovirt_engine_3_6_dao_unit_tests_created_25*16:11:09* + pwd*16:11:09* /home/jenkins/workspace/ovirt-engine_3.6_dao-unit-tests_created*16:11:09* + sudo -u postgres psql -d template1 -c 'create role engine;'*16:11:09* sudo: unknown user: postgres*16:11:09* sudo: unable to initialize policy plugin*16:11:09* + :*16:11:09* + sudo -u postgres psql -d template1 -c 'ALTER ROLE engine WITH login'*16:11:09* sudo: unknown user: postgres*16:11:09* sudo: unable to initialize policy plugin*16:11:09* + :*16:11:09* + sudo -u postgres dropdb engine*16:11:09* sudo: unknown user: postgres*16:11:09* sudo: unable to initialize policy plugin*16:11:09* + :*16:11:09* + sudo -u postgres psql -d template1 -c 'create database ovirt_engine_3_6_dao_unit_tests_created_25 owner engine;'*16:11:09* sudo: unknown user: postgres*16:11:09* sudo: unable to initialize policy plugin*16:11:09* + PGPASSWORD=engine*16:11:09* + ./packaging/dbscripts/schema.sh -c apply -d ovirt_engine_3_6_dao_unit_tests_created_25 -u engine*16:11:09* ./packaging/dbscripts/dbfunc-base.sh: line 31: psql: command not found*16:11:09* FATAL: Cannot execute sql command: --command=select 1; More information can be found at: http://jenkins.ovirt.org/job/ovirt-engine_3.6_dao-unit-tests_created/25 Could you please fix? Thanks Martin

2 1

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

09 Dec '16

------=_Part_50_1138525590.1481238012695 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/162//artifact/exported-a… Cheers, Jenkins ------=_Part_50_1138525590.1481238012695 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 - 08/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-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-engine_4.0_upgrade-from-4.0_el7_merged/">ovirt-engine_4.0_upgrade-from-4.0_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-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_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/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-fc23-x86…">vdsm-jsonrpc-java_4.0_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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_50_1138525590.1481238012695--

1 0

Mail server migration
by Marc Dequènes (Duck) 08 Dec '16

08 Dec '16

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bkDSTXWjp3as906iobm58l8sSkQ3aVVH3 Content-Type: multipart/mixed; boundary="WFPIMUvNLhaoIhxvU1KvRiguAfcoaPUnQ"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org>, users(a)ovirt.org Message-ID: <57111df5-8497-e9de-5b62-0d955384365a(a)redhat.com> Subject: Mail server migration --WFPIMUvNLhaoIhxvU1KvRiguAfcoaPUnQ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, The old server is going to retire, so we prepared a replacement. Tomorrow, between 23:30-00:30 JST, the switch will happen. Any mails on the ovirt.org domain, including mailing-lists, are affected. We now have backup servers for imcoming mails, so they will not be lost, but the processing will not occur until the final sync is done and the switch is over. This should normally take only a few minutes at most. Fly well. \_o< --WFPIMUvNLhaoIhxvU1KvRiguAfcoaPUnQ-- --bkDSTXWjp3as906iobm58l8sSkQ3aVVH3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlhIPhcACgkQVen596wc RD9JxA/+I5YXg2xk+VPevBe75XKu0RWNZN+67mHFQqFggEAOPdXoZWIsQEcepVpt mrI8gCC56w7ofcmxX84ILL9L2l62LRN8iJKXgH9FZtwjlSdbohpP5FO++XvXhSbQ /ZX7IbMUhbl48KlnGCEHbvOVXL9brbvy5fyG3p7hh4QfnHOj57Odz0ls0S7JFloT 5FyE/8xn82Pi4KESYXNxObTEQqTK4N0XUT983kZAXvLASlGcpUwhsTIC7gFRq0Oo q4onnHmlVF6zCIXtA3qqt7hGVwpQtfCYEDfFXvryksrrsWPVANg8oWMQWr9yPEXG +WE2yUWQS8wTqndWZ3y9MjX93/sBTpNWhmrLRkVjJpLNGDgw47sqGAmolPz/ehj2 DVWC2uLUGjqZPnfpkgjyv873miCOETqMh2bYFpqNPUEDNAIqpmUewsnSfNFT8FcY bo4BjBN4zfCcySemsCw0h7IDziB28knodpx2OxsEjCuIDNIGiX6fhGK6v9ynQIWX X8p7Iu1pXvaRbLehE5QcUqf7BHJ2eOEoJ+CjyyDSepppNzNibCV7zymgBDrPCnIP tAUUyCGxbtqUnK+H1XLr9/MJJYij8XIm3W39NWGOuMGERXRfXtmi/iQEbvDjbuet CztSGoJDbV+KEBXQvCuiG/s3R0rxjTL++h/7TeFdRuEFxui+6/0= =oglK -----END PGP SIGNATURE----- --bkDSTXWjp3as906iobm58l8sSkQ3aVVH3--

1 1

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by Nadav Goldin (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-713?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-713: ------------------------------------ {quote} To resolve this issue, lago removes those rpms, and runs reposync again.{quote} The 'lago remove those rpms' part, didn't usually happen. Hopefully now on 'master' branch it should, so we'll have to wait and see if it resolves the issues, or we need to be more aggressive as [~gbenhaim(a)redhat.com] suggested and wipe out the entire cache. > Clean reposync directory after n times of sync failure > ------------------------------------------------------ > > Key: OVIRT-713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: infra > > Sometimes reposync fail to sync rpms that already been synced. > To resolve this issue, lago removes those rpms, and runs reposync again. > This resolution doesn't always work, and then we need to clean all the rpms that were synced. > We want lago to clear the cached rpms after n times of sync failure, and then try to sync again. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Gil Shinar (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-886: ---------------------------------- Danken came to us with a STD-CI failure. Bark has investigated and found that when using yum in el7 mock on a Fedora host, we do not get errors on missing packages and the yum command completes successfully > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-905) lago_master_check jobs still require fc23 slaves
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-905?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-905: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > lago_master_check jobs still require fc23 slaves > ------------------------------------------------ > > Key: OVIRT-905 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-905 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: eyal edri [Administrator] > > Lago check jobs require "nested && fc23" labels, and as Fedora 23 will be EOL in a couple of weeks we need to check if we can change this to newer Fedora versions or CentOS -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

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

08 Dec '16

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

1 1

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-713?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-713: ------------------------------------------------- [~ngoldin(a)redhat.com] anything you're doing now on reposync will solve this? > Clean reposync directory after n times of sync failure > ------------------------------------------------------ > > Key: OVIRT-713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: infra > > Sometimes reposync fail to sync rpms that already been synced. > To resolve this issue, lago removes those rpms, and runs reposync again. > This resolution doesn't always work, and then we need to clean all the rpms that were synced. > We want lago to clear the cached rpms after n times of sync failure, and then try to sync again. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-792) Jenkins job on fc23-vm05.phx.ovirt.org stuck on '... Removing the used loop devices...'
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-792?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-792: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) please check if still relevant > Jenkins job on fc23-vm05.phx.ovirt.org stuck on '... Removing the used loop devices...' > --------------------------------------------------------------------------------------- > > Key: OVIRT-792 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-792 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: Shlomo Ben David > > Not sure if this is a regression, maybe added in [1], or a temporary glitch: > http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/336/console > http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/337/console > for now going to clean it manually. > [1] https://gerrit.ovirt.org/#/c/64511/ -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-886: ------------------------------------------------- Who was the original requestor for this who can verify? > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-911) Move repo closure to run in STD-CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-911?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-911: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > Move repo closure to run in STD-CI > ---------------------------------- > > Key: OVIRT-911 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-911 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Daniel Belenky > > Repo closure jobs are currently running on VMs. > We would like to change these jobs to run inside mocks as STD-CI. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-889) Add support for building containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-889: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > Add support for building containers in standard CI > -------------------------------------------------- > > Key: OVIRT-889 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-889 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > Priority: Highest > Labels: containers, docker > > might be simple as bash command in build-containers.sh script or using a service like DockerHub of OpenShift, we need to examine both options and choose the most fit. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-890) Add support to publish containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-890?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-890: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > Add support to publish containers in standard CI > ------------------------------------------------ > > Key: OVIRT-890 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-890 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > Labels: containers, docker, standard-ci > > Mostly likely to Dockerhub or OpenShift registry. > We'll need a pet project to try out the various options. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-889) Add support for building containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-889: -------------------------------------------- Priority: Highest (was: Medium) > Add support for building containers in standard CI > -------------------------------------------------- > > Key: OVIRT-889 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-889 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > Labels: containers, docker > > might be simple as bash command in build-containers.sh script or using a service like DockerHub of OpenShift, we need to examine both options and choose the most fit. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by Greg Sheremeta (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-904: -------------------------------------- [~bkorren(a)redhat.com] > are you doing that manually Yes, completely manual > I'm not sure oVirt's own infra would be the best place, because Patternfly is not strictly an oVirt project. True. However, we've talked about renaming the rpm to 'ovirt-patternflyX' to reflect the fact that it's only used by us. In that case, it might make sense to move it to our infra. > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-854) repoman: check if repoman can keep more than 1 version for experimental repo
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-854?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-854: -------------------------------------------- Resolution: Duplicate Status: Done (was: To Do) We already have a ticket on this, on the rel eng epic > repoman: check if repoman can keep more than 1 version for experimental repo > ---------------------------------------------------------------------------- > > Key: OVIRT-854 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-854 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Today we see text experimental master jobs fails because it has different vdsm rpms versions in the same repo. > This can happen because VDSM has 2 jobs publishing the "same" noarch rpms, once from x86_64 and once from ppc64le. > Since the job only takes latest rpms, it might take a newer rpm from one arch and older rpms from another, causing add host to fail installing VDSM. > We need to check if its possible to tell repoman to keep more than 1 version (should be enough) so the tests won't wait in this period of time where one arch got a head of another one. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

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

08 Dec '16

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

1 0

[JIRA] (OVIRT-923) define process to manage and apply ansible playbooks
by Evgheni Dereveanchin (oVirt JIRA) 08 Dec '16

08 Dec '16

Evgheni Dereveanchin created OVIRT-923: ------------------------------------------ Summary: define process to manage and apply ansible playbooks Key: OVIRT-923 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-923 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low We already have a repository with ansible code, but to use it effectively we need to define a way to manage playbooks and run them effectively. As Ansible Tower is not open source we need to investigate other solutions on the market. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-913) Speed up mock with the `nosync` package
by Barak Korren (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-913?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-913: ---------------------------------- Assignee: Barak Korren (was: infra) > Speed up mock with the `nosync` package > --------------------------------------- > > Key: OVIRT-913 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-913 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Labels: mock, mock_runner.sh, standard-ci > > The {{nosync}} package can make mock faster by making it ignore all {{sync(2)}} calls. > {{mock_runner.sh}} actually already enables this setting in the chroot configuration files, but it cannot work without the package. > We need to check if this actually makes mock faster, and if so, add it to the slaves. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-226: -------------------------------------------- Priority: Lowest (was: Medium) > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: sbonazzo > Assignee: infra > Priority: Lowest > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-449) Add junit report to ovirt-engine standard ci
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-449?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-449: -------------------------------------------- Priority: Low (was: Medium) > Add junit report to ovirt-engine standard ci > -------------------------------------------- > > Key: OVIRT-449 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-449 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > Priority: Low > > Currently there are to ways of doing it: > * Using a special job template for ovirt-engine (easy to do now, hard to maintain/reuse) > * Using jenkins pipeline plugin to dynamically add it to any job that generates a report (hard to do right now, easy to maintain/reuse) -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-900: ------------------------------------------------- [~ybronhei(a)redhat.com] can you check if it works for you now? > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-705) Upgrade to puppet 4.0
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-705?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-705: -------------------------------------------- Priority: Lowest (was: Medium) > Upgrade to puppet 4.0 > --------------------- > > Key: OVIRT-705 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-705 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Lowest > > Related to the migration of foreman + puppet master to PHX, and worth its own ticket. > Will be addressed once we have a new foreman 1.12 up & running. > Also, nice blog on the migration might be useful: > http://hggh.github.io/puppet/debian/2016/08/19/puppet-4.x.html -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-729) Jenkins leaves behind connections in ESTABLISHED state
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-729?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-729: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) see if this is still relevant. > Jenkins leaves behind connections in ESTABLISHED state > ------------------------------------------------------ > > Key: OVIRT-729 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-729 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Low > > Throughout the last days I noticed several times when a slave got non-responsive and after rebooting it never recovered until being removed/re-added to Jenkins. > Further investigation on el7-vm06.phx.ovirt.org revealed that on Jenkins the connection is still marked as "ESTABLISHED" hours after the slave crashed and rebooted: > {quote} > tcp6 0 0 66.187.230.92:33374 66.187.230.77:22 ESTABLISHED 14625/java > {quote} > Due to this new SSH connections are not opened and Jenkins can't reconnect to the slave. > I didn't see this behavior before, maybe it is related to the latest security upgrade of jenkins. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-453) Gerrit: Issue 3885: Failed to index change
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-453?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-453: -------------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) Havn't seen this another time since the upgrade. We'll do a periodic upgrade to 2.13/2.14 which will anyway include a fix for this. the upgrade will be monitored on another ticket. > Gerrit: Issue 3885: Failed to index change > ------------------------------------------ > > Key: OVIRT-453 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-453 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > Its an open issue [1] in Gerrit, but still no fix available. > We'll track it and see if there is a pending fix, cc'ing infra-support to > open a ticket to track this. > [1] > https://code.google.com/p/gerrit/issues/detail?can=2&start=0&num=100&q=&col… > On Sun, Mar 27, 2016 at 7:03 AM, Nadav Goldin <ngoldin(a)redhat.com> wrote: > > Hi, > > gerrit started throwing weird errors this morning, such as: > > > >> internal server error: com.google.gerrit.server.git.UpdateException: > >> java.io.IOException: java.util.concurrent.ExecutionException: > >> org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed) > >> > > > > restarting it now. > > > > > > Nadav. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHEV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-296) [jenkins] take offline faulty bad slaves
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-296?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-296: -------------------------------------------- Priority: Medium (was: Highest) > [jenkins] take offline faulty bad slaves > ---------------------------------------- > > Key: OVIRT-296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-296 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: jenkins, monitoring, > > it seems that quite often we hit an issue with a specific slave on phx, due to various reasons (out of space/git/network/etc..). > which leads to multiple jobs trying to run on it and failing. > we need an automated way of finding this. > proposal: > add post groovy build to jobs that will take a slave offline if it's misbehaves using: > manager.build.getBuiltOn().toComputer.setTemporarilyOffline(true) > the trick is to find such a slave and to be able to know if it failed consistently in the past X hours to justify it's disable. > we need some sort of counter or service to track slaves and thier error state and according to it take offline a specific slave. > for example: > if a slave was failing x jobs in Y time and runtime was < Z min , it might indicate such a problem. > (e.g 10 jobs were failing on the same slave in a timeframe of 5 min and job runtime was less than a 1 min.. ) > the post script should email infra(a)ovirt.org that it disabled a slave and we should look into it. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-837) artifactory /opt dir isn't monitored for space
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-837?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-837: -------------------------------------------- Priority: Highest (was: High) > artifactory /opt dir isn't monitored for space > ---------------------------------------------- > > Key: OVIRT-837 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-837 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > Artifactory application is running on /opt and if the disk is full the application is failing to provide jars and gets very slow ( but errors on out of space are seen in the logs ). -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0