- Infra - oVirt List Archives

[JIRA] (OVIRT-687) spike in process number on resources.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 15 Aug '16

15 Aug '16

Evgheni Dereveanchin created OVIRT-687: ------------------------------------------ Summary: spike in process number on resources.ovirt.org Key: OVIRT-687 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-687 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low Attachments: image.png The number of processes on resources.ovirt.org jumped from 300 to 500 today. Need to check why that happened and if it's normal - reconfigure nagios accordingly -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eyal edri [Administrator] (oVirt JIRA) 15 Aug '16

15 Aug '16

eyal edri [Administrator] created OVIRT-686: ----------------------------------------------- Summary: Find a better way to show unstable status in CI Key: OVIRT-686 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri [Administrator] Assignee: infra Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eyal edri [Administrator] (oVirt JIRA) 15 Aug '16

15 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-686: -------------------------------------------- Epic Link: OVIRT-400 > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

Build failed in Jenkins: ovirt_4.0_system-tests #287
by jenkins＠jenkins.phx.ovirt.org 15 Aug '16

15 Aug '16

See <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/287/changes> Changes: [Gal Ben Haim] Removed the hard coded path of the template repo. The template repo file ------------------------------------------ [...truncated 659 lines...] ## took 814 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log enties: logs/mocker-fedora-23-x86_64.fc23.basic_suite_4.0.sh/basic_suite_4.0.sh.log ##! + true + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/d…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/d…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 Took 631 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=4.0 SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_4.0_system-tests] $ /bin/bash -xe /tmp/hudson3554245375878471530.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=4.0 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/> + OVIRT_SUITE=4.0 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/287/artifact/exported-a…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/287/artifact/exported-a…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/287/artifact/exported-a…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then tar cvzf exported-artifacts/logs.tgz "${logs[@]}" rm -rf "${logs[@]}" fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" [ovirt_4.0_system-tests] $ /bin/bash -xe /tmp/hudson7620342481452401506.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs ./ovirt-system-tests/logs/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/state.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/build.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/root.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/state.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/build.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/root.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.basic_suite_4.0.sh/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.basic_suite_4.0.sh/basic_suite_4.0.sh.log + rm -rf ./ovirt-system-tests/logs + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/m…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-fedora-23-x86_64.fc23.cfg + mock_root=mocker-fedora-23-x86_64.fc23 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-fedora-23-x86_64.fc23' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests> --root=mocker-fedora-23-x86_64.fc23 --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/l….> Using default... INFO: mock.py version 1.2.18 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests/m…> + mock_root=fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + [[ -n fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 8

[JIRA] (OVIRT-675) ci-tools repo does not support RHEL7
by Evgheni Dereveanchin (oVirt JIRA) 15 Aug '16

15 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-675?page=com.atlassian.jira.p… ] Evgheni Dereveanchin updated OVIRT-675: --------------------------------------- Resolution: Fixed Status: Done (was: To Do) closing since the error is gone with the new symlink > ci-tools repo does not support RHEL7 > ------------------------------------ > > Key: OVIRT-675 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-675 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Evgheni Dereveanchin > Assignee: infra > > The ci-tools repo does not work with RHEL7. > Our puppet manifests set it up the following way: > baseurl=http://resources.ovirt.org/repos/ci-tools/EL/$releasever > On RHEL7 this results in: > http://resources.ovirt.org/repos/ci-tools/EL/7Server/ > which does not exist. > Can we create a symlink 7Server -> 7 to make it work? It looks like a similar config ins in place for RHEL6. > The current ci-tools puppet manifest is here: > https://gerrit.ovirt.org/gitweb?p=infra-puppet.git;a=blob;f=site/ovirt_base… -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

Gerrit/ManualTrigger permission
by Ravi Nori 15 Aug '16

15 Aug '16

Hi, I need dev permissions for "rnori" to be able to trigger manually. "rnori is missing the Gerrit/ManualTrigger permission" Thanks, Ravi

2 6

oVirt infra daily report - unstable production jobs - 46
by jenkins＠jenkins.phx.ovirt.org 15 Aug '16

15 Aug '16

------=_Part_142_2045070902.1471215604345 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/46//artifact/exported-ar… Cheers, Jenkins ------=_Part_142_2045070902.1471215604345 Content-Type: application/octet-stream; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 14/08/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/lago_master_check-merged-trigger/">lago_master_check-merged-trigger</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?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-engine_master_upgrade-from-4.0_el7_merge…">ovirt-engine_master_upgrade-from-4.0_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-fc22-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_4.0_he-system-tests/">ovirt_4.0_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_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/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> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/">vdsm_master_build-artifacts-el7-ppc64le</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?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_master_build-artifacts-el7-x86_64/">vdsm_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/vdsm_master_check-merged-fc24-x86_64/">vdsm_master_check-merged-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> ------=_Part_142_2045070902.1471215604345--

1 0

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

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-416: ------------------------------------------------- OK, looking at the code it seems check-merged is running a draft build: # create the rpms rpmbuild \ -D "_rpmdir $PWD/output" \ -D "_topmdir $PWD/rpmbuild" \ -D "release_suffix ${SUFFIX}" \ -D "ovirt_build_ut $BUILD_UT" \ -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \ -D "ovirt_build_draft 1" \ --rebuild output/*.src.rpm while build artifacts is running full blown matrix: # create the rpms rpmbuild \ -D "_rpmdir $PWD/output" \ -D "_topmdir $PWD/rpmbuild" \ -D "release_suffix ${SUFFIX}" \ -D "ovirt_build_ut $BUILD_UT" \ -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \ --rebuild output/*.src.rpm and currently running 27(!) permutations. So the question is, can we reduce this to 1-2 permutations? if this is just going to nightly / hourly repo then we don't need all these permutations and we'll enjoy a much faster verification on the experimental flow which collects artifacts from build-artifacts jobs. We are now adding the 'build official manual' option to standard CI, so we can keep the 27 permutations there for official builds. I believe this will reduce dramatically the CI flow runtime and will give us much faster feedback on failures. Also, it will simplify the move to running experimental flow per patch as the full run-time will be significantly lower. > [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any > ------------------------------------------------------------------------------------- > > Key: OVIRT-416 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > > Right now most projects just rebuild twice the artifacts, what for some means a big waste of resources, if we could just reuse what was built previously there would be no rebuilding. > Something to take into account is that the distributions that check-merged and build-artifacts run for might not match, so you can be running check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an example), maybe we should not allow different distros on each stage?| -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-562) find a way not to fail CI jobs if git clone fails
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-562?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-562: -------------------------------------------- Priority: Low (was: Medium) lowering priority since we don't hit this issue anymore upgrade gerrit upgrade. > find a way not to fail CI jobs if git clone fails > ------------------------------------------------- > > Key: OVIRT-562 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-562 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Low > > We need to find away to tell gerrit trigger plugin not to put -1 if git clone fails (obviously an infra issue) -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-685) Add Ubunto slaves to CI
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-685?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-685: -------------------------------------------- Epic Link: OVIRT-400 > Add Ubunto slaves to CI > ----------------------- > > Key: OVIRT-685 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-685 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > We are looking into building Lago on Ubunto, so we'll need some slaves to do it. > not sure yet about puppet classes, we might need to do some changes to support it. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-685) Add Ubunto slaves to CI
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

eyal edri [Administrator] created OVIRT-685: ----------------------------------------------- Summary: Add Ubunto slaves to CI Key: OVIRT-685 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-685 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra We are looking into building Lago on Ubunto, so we'll need some slaves to do it. not sure yet about puppet classes, we might need to do some changes to support it. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-678) vdsm check-merge jobs doesn't work for el7
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-678?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-678: ------------------------------------------------- I understand you want to remove the el7 job for master, the question is why? If we want to fix it, I suggest to keep it or at least disable it, otherwise we'll just forget about it. if its only check-merged then it doesn't give -1 on patches and its not blocking patches. also, if there is something the infra team can do to help with fixing el7 please let us know > vdsm check-merge jobs doesn't work for el7 > ------------------------------------------ > > Key: OVIRT-678 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-678 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > On Wed, Aug 10, 2016 at 3:41 PM, Irit Goihman <igoihman(a)redhat.com> wrote: > > Hi, > > jobs vdsm_master_build-artifacts-el7-ppc64le and vdsm_master_check-merged-el7-x86_64 > > keep failing. They were created recently and should be removed. > > > The ppc64le should be fixed, not removed. > We want ppc64le builds now that we have ppc64le slaves. > The check-merged for el7 is your call, fine for me if you want to remove. > Just weird since el7 is our main target. > > > > Thanks > > > > -- > > Irit Goihman > > Software Engineer > > Red Hat Israel Ltd. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-678) vdsm check-merge jobs doesn't work for el7
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-678?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-678: -------------------------------------------- Summary: vdsm check-merge jobs doesn't work for el7 (was: Re: please remove the following jenkins jobs) > vdsm check-merge jobs doesn't work for el7 > ------------------------------------------ > > Key: OVIRT-678 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-678 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > On Wed, Aug 10, 2016 at 3:41 PM, Irit Goihman <igoihman(a)redhat.com> wrote: > > Hi, > > jobs vdsm_master_build-artifacts-el7-ppc64le and vdsm_master_check-merged-el7-x86_64 > > keep failing. They were created recently and should be removed. > > > The ppc64le should be fixed, not removed. > We want ppc64le builds now that we have ppc64le slaves. > The check-merged for el7 is your call, fine for me if you want to remove. > Just weird since el7 is our main target. > > > > Thanks > > > > -- > > Irit Goihman > > Software Engineer > > Red Hat Israel Ltd. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-684) dev permissions
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-684?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-684: -------------------------------------------- Resolution: Fixed Status: Done (was: Blocked) please open if you still require more permissions > dev permissions > --------------- > > Key: OVIRT-684 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-684 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Liron Aravot > Assignee: infra > > Hi, > I need dev permissions for "laravot" to be able to trigger manually. > "laravot is missing the Gerrit/ManualTrigger permission" > thanks. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

Build failed in Jenkins: ovirt_master_system-tests #388
by jenkins＠jenkins.phx.ovirt.org 14 Aug '16

14 Aug '16

See <http://jenkins.ovirt.org/job/ovirt_master_system-tests/388/changes> Changes: [Gal Ben Haim] Removed the hard coded path of the template repo. The template repo file ------------------------------------------ [...truncated 649 lines...] ## took 807 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log enties: logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log ##! + true + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 Took 629 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=master SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson5606048360884548341.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=master + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> + OVIRT_SUITE=master + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_master_system-tests/388/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_master_system-tests/388/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/388/artifact/exporte…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then tar cvzf exported-artifacts/logs.tgz "${logs[@]}" rm -rf "${logs[@]}" fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" [ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson5680342711917502147.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs ./ovirt-system-tests/logs/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/state.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/build.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/root.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/state.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/build.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/root.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.clean_rpmdb/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log + rm -rf ./ovirt-system-tests/logs + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-fedora-24-x86_64.fc24.cfg + mock_root=mocker-fedora-24-x86_64.fc24 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-fedora-24-x86_64.fc24' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-tests> --root=mocker-fedora-24-x86_64.fc24 --resultdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test….> Using default... INFO: mock.py version 1.2.18 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> + mock_root=fedora-24-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + [[ -n fedora-24-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep fedora-24-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/fedora-24-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 9

[JIRA] (OVIRT-684) dev permissions
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-684?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-684: -------------------------------------------- Blocked By: pending user reply Status: Blocked (was: To Do) > dev permissions > --------------- > > Key: OVIRT-684 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-684 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Liron Aravot > Assignee: infra > > Hi, > I need dev permissions for "laravot" to be able to trigger manually. > "laravot is missing the Gerrit/ManualTrigger permission" > thanks. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-684) dev permissions
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-684?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-684: ------------------------------------------------- added you the dev role, please try now > dev permissions > --------------- > > Key: OVIRT-684 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-684 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Liron Aravot > Assignee: infra > > Hi, > I need dev permissions for "laravot" to be able to trigger manually. > "laravot is missing the Gerrit/ManualTrigger permission" > thanks. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-684) dev permissions
by Liron Aravot (oVirt JIRA) 14 Aug '16

14 Aug '16

Liron Aravot created OVIRT-684: ---------------------------------- Summary: dev permissions Key: OVIRT-684 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-684 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Liron Aravot Assignee: infra Hi, I need dev permissions for "laravot" to be able to trigger manually. "laravot is missing the Gerrit/ManualTrigger permission" thanks. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

Re: CI failure related to setting up PK12?
by Eyal Edri 14 Aug '16

14 Aug '16

Adding infra. But it looks like a real error, maybe Didi can help today with understanding where it comes from, we might need to do update to answer file due to recent change or something. Relevant patch which touched PKI just recently: commit f87e5c1ba7c58d342ba520422b0ec36fb01a866e Author: Yedidyah Bar David <didi(a)redhat.com> Date: Wed Aug 10 14:02:19 2016 +0300 packaging: setup: Enroll missing pki on upgrade Without this patch, imageio-proxy pki will not be generated on upgrade from 3.6, because it did not exist then. Change-Id: Ib5bbe9ddb45bfcbf6b7bf8aa7c6e2fb19fa206fe Bug-Url: https://bugzilla.redhat.com/1365451 Signed-off-by: Yedidyah Bar David <didi(a)redhat.com> On Sun, Aug 14, 2016 at 8:48 AM, Allon Mureinik <amureini(a)redhat.com> wrote: > Hi guys, > > Any recent engine patch (e.g., [1]) I look at seems to fail the CI in a > similar way: > > [ INFO ] Stage: Setup validation > [WARNING] Cannot validate host name settings, reason: resolved host does not match any of the local addresses > [WARNING] Less than 16384MB of memory is available > > --== CONFIGURATION PREVIEW ==-- > > Application mode : both > Default SAN wipe after delete : False > Firewall manager : firewalld > Update Firewall : True > Host FQDN : el7-vm31 > Require packages rollback : False > Upgrade packages : True > Engine database secured connection : False > Engine database host : localhost > Engine database user name : engine > Engine database name : engine > Engine database port : 5432 > Engine database host name validation : False > Configure local DWH database : False > Engine installation : True > NFS setup : True > PKI organization : ovirt.org > NFS export ACL : 0.0.0.0/0.0.0.0(rw) > NFS mount point : /var/lib/exports/iso > Configure local Engine database : True > Set application as default page : True > Configure Apache SSL : True > DWH installation : False > Engine Host FQDN : el7-vm31 > Configure Image I/O Proxy : False > Configure VMConsole Proxy : True > Configure WebSocket Proxy : True > [ INFO ] Stage: Transaction setup > [ INFO ] Stopping engine service > [ INFO ] Stopping ovirt-fence-kdump-listener service > [ INFO ] Stopping websocket-proxy service > [ INFO ] Stage: Misc configuration > [ INFO ] Stage: Package installation > [ INFO ] Stage: Misc configuration > [ INFO ] Upgrading CA > [ ERROR ] Failed to execute stage 'Misc configuration': Command '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to execute > > > > Can you take a look please? > > > > Thanks, > > Allon > > > [1] http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_cr… > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

3 4

[JIRA] (OVIRT-663) add ppc64le arch builds for oVirt projects
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-663?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-663: -------------------------------------------- Blocked By: centos bugs Status: Blocked (was: In Progress) Pending centos tickets to allow build vdsm ppc64le, ioprocess was already built and deployed. our patches: https://gerrit.ovirt.org/#/c/62123/5 https://gerrit.ovirt.org/#/c/61629/ centos bugs: https://bugs.centos.org/view.php?id=11304 https://bugs.centos.org/view.php?id=11222 https://bugs.centos.org/view.php?id=11279 > add ppc64le arch builds for oVirt projects > ------------------------------------------ > > Key: OVIRT-663 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-663 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > now that we have a ppc64le slaves in jenkins we can start building pkg for it and deploy it to resources.ovirt.org. > this ticket will track all pkg progress: > # qemu-kvm - currently pending gluster builds for ppc64le, ETA - next week > # vdsm > # ioprocess > [~danken][~fromani(a)redhat.com] anything else that is not noarch which we need to build? -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

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

14 Aug '16

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

1 0

[JIRA] (OVIRT-678) Re: please remove the following jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-678?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-678: -------------------------------------------- External issue ID: https://bugs.centos.org/view.php?id=11304 Blocked By: pending missing builds for ppc64 Status: Blocked (was: To Do) Once we merge https://gerrit.ovirt.org/#/c/62123/5 and https://gerrit.ovirt.org/#/c/61629/ the ppc64le jobs should work. If there are other jobs failing, please report. > Re: please remove the following jenkins jobs > -------------------------------------------- > > Key: OVIRT-678 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-678 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > On Wed, Aug 10, 2016 at 3:41 PM, Irit Goihman <igoihman(a)redhat.com> wrote: > > Hi, > > jobs vdsm_master_build-artifacts-el7-ppc64le and vdsm_master_check-merged-el7-x86_64 > > keep failing. They were created recently and should be removed. > > > The ppc64le should be fixed, not removed. > We want ppc64le builds now that we have ppc64le slaves. > The check-merged for el7 is your call, fine for me if you want to remove. > Just weird since el7 is our main target. > > > > Thanks > > > > -- > > Irit Goihman > > Software Engineer > > Red Hat Israel Ltd. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-681) [URGENT] boolean parameters not passed anymore to jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-681?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-681: ------------------------------------------------- So can we close this as duplicate? > [URGENT] boolean parameters not passed anymore to jenkins jobs > -------------------------------------------------------------- > > Key: OVIRT-681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-681 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: image.png > > > Hi, > looks like repository closure jobs are not working anymore because the > boolean parameters are not passed anymore to the job environment. > Can you please check why this happens? > See for example > http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Repo%20status/job/repo… > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-675) ci-tools repo does not support RHEL7
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-675?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-675: -------------------------------------------- Epic Link: OVIRT-411 > ci-tools repo does not support RHEL7 > ------------------------------------ > > Key: OVIRT-675 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-675 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Evgheni Dereveanchin > Assignee: infra > > The ci-tools repo does not work with RHEL7. > Our puppet manifests set it up the following way: > baseurl=http://resources.ovirt.org/repos/ci-tools/EL/$releasever > On RHEL7 this results in: > http://resources.ovirt.org/repos/ci-tools/EL/7Server/ > which does not exist. > Can we create a symlink 7Server -> 7 to make it work? It looks like a similar config ins in place for RHEL6. > The current ci-tools puppet manifest is here: > https://gerrit.ovirt.org/gitweb?p=infra-puppet.git;a=blob;f=site/ovirt_base… -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-681) [URGENT] boolean parameters not passed anymore to jenkins jobs
by snaftaly (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-681?page=com.atlassian.jira.p… ] snaftaly commented on OVIRT-681: -------------------------------- [~eedri], [~sbonazzo(a)redhat.com] I started working on moving the jobs to yaml (without matrix jobs). I hope my patch will be ready today. > [URGENT] boolean parameters not passed anymore to jenkins jobs > -------------------------------------------------------------- > > Key: OVIRT-681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-681 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: image.png > > > Hi, > looks like repository closure jobs are not working anymore because the > boolean parameters are not passed anymore to the job environment. > Can you please check why this happens? > See for example > http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Repo%20status/job/repo… > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-681) [URGENT] boolean parameters not passed anymore to jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-681?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-681: ------------------------------------------------- Can we get rid of the matrix plugin and move to use normal jobs, should be easy with YAML and don't need the complexity of matrix jobs... On Sun, Aug 14, 2016 at 10:39 AM, Gil Shinar (oVirt JIRA) < -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > [URGENT] boolean parameters not passed anymore to jenkins jobs > -------------------------------------------------------------- > > Key: OVIRT-681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-681 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: image.png > > > Hi, > looks like repository closure jobs are not working anymore because the > boolean parameters are not passed anymore to the job environment. > Can you please check why this happens? > See for example > http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Repo%20status/job/repo… > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-681) [URGENT] boolean parameters not passed anymore to jenkins jobs
by Gil Shinar (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-681?page=com.atlassian.jira.p… ] Gil Shinar updated OVIRT-681: ----------------------------- Attachment: image.png Hi Sandro, I haven't had the chance to use Matrix jobs so it was a challenge for me investigate :-) I have found the following bug: https://issues.jenkins-ci.org/browse/JENKINS-34758 Due to a security update, parameters stopped being passed to child jobs. According to changelog, matrix job plugin version 1.7 should fix that: [image: Inline image 1] I'll upgrade the plugin but restart might be needed so you'll tell us when. Gil On Sat, Aug 13, 2016 at 8:49 AM, sbonazzo (oVirt JIRA) < > [URGENT] boolean parameters not passed anymore to jenkins jobs > -------------------------------------------------------------- > > Key: OVIRT-681 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-681 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: image.png > > > Hi, > looks like repository closure jobs are not working anymore because the > boolean parameters are not passed anymore to the job environment. > Can you please check why this happens? > See for example > http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Repo%20status/job/repo… > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

2 1

[JIRA] (OVIRT-681) [URGENT] boolean parameters not passed anymore to jenkins jobs
by sbonazzo (oVirt JIRA) 14 Aug '16

14 Aug '16

sbonazzo created OVIRT-681: ------------------------------ Summary: [URGENT] boolean parameters not passed anymore to jenkins jobs Key: OVIRT-681 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-681 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, looks like repository closure jobs are not working anymore because the boolean parameters are not passed anymore to the job environment. Can you please check why this happens? See for example http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Repo%20status/job/repo… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

2 1

[JIRA] (OVIRT-683) [gerrit hooks] bug status shouldn't move to MODIFIED if on master branch
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

eyal edri [Administrator] created OVIRT-683: ----------------------------------------------- Summary: [gerrit hooks] bug status shouldn't move to MODIFIED if on master branch Key: OVIRT-683 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-683 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra consider master branch also in the logic for moving to MODIFIED state, suggested patch: https://gerrit.ovirt.org/#/c/61073/ -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

[JIRA] (OVIRT-683) [gerrit hooks] bug status shouldn't move to MODIFIED if on master branch
by eyal edri [Administrator] (oVirt JIRA) 14 Aug '16

14 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-683?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-683: -------------------------------------------- Epic Link: OVIRT-411 > [gerrit hooks] bug status shouldn't move to MODIFIED if on master branch > ------------------------------------------------------------------------ > > Key: OVIRT-683 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-683 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > consider master branch also in the logic for moving to MODIFIED state, > suggested patch: https://gerrit.ovirt.org/#/c/61073/ -- This message was sent by Atlassian JIRA (v1000.245.0#100009)

1 0

oVirt Bot and oVirt Meetings
by Sandro Bonazzola 14 Aug '16

14 Aug '16

Hi, is the oVirt Bot meant to be down? The oVIrt website still mention it: http://www.ovirt.org/community/about/meetings/ http://www.ovirt.org/develop/infra/ovirtbot/ http://www.ovirt.org/develop/infra/running-ovirtbot/ http://www.ovirt.org/develop/infra/infrastructure-team-meetings/ Are listed meetings still valid? I don't think so. http://www.ovirt.org/community/about/meetings/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

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

14 Aug '16

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

1 0

Improve CI logging - check if its possible to include mock errors in console output
by Eyal Edri 14 Aug '16

14 Aug '16

On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > Hi all, > > Lately vdsm builds are failing in the install packages stage with > this unhelpful error: > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > 13:59:53 ERROR: Command failed. See logs for output. > > I downloaded the logs.tgz file from > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > x86_64/1154/artifact/exported-artifacts/logs.tgz > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > root.log > I found found this error: > > DEBUG util.py:421: Error: Package: > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > (ovirt-snapshot) > DEBUG util.py:421: Requires: ioprocess = > 0.17.0-1.201608111609.gitbd272f2.fc24 > DEBUG util.py:421: Available: > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > DEBUG util.py:421: Available: > ioprocess-0.16.1-1.fc24.x86_64 (updates) > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > DEBUG util.py:421: Available: > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > (ovirt-snapshot) > DEBUG util.py:421: ioprocess = > 0.17.0-1.201607121058.gitbd272f2.fc24 > DEBUG util.py:421: Available: > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > (ovirt-snapshot) > DEBUG util.py:421: ioprocess = > 0.17.0-1.201608111129.gitbd272f2.fc24 > > So we have 2 issues here: > > 1. We need *all* errors in the console > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > x86_64/1154/console Not sure its possible or easy to do, these errors usually come from mock and are not relevant to the code running on the console. I've cc'd infra-support and updated topic to track it and check our options. Going foward, we might want to install a log collector like logstash and then searching errors there should be much easier. > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > the missing ioprocess > package. > Maybe the project xml is not correct? > > Nir > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

oVirt infra daily report - unstable production jobs - 45
by jenkins＠jenkins.phx.ovirt.org 14 Aug '16

14 Aug '16

------=_Part_130_1001960909.1471129204561 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/45//artifact/exported-ar… Cheers, Jenkins ------=_Part_130_1001960909.1471129204561 Content-Type: application/octet-stream; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 13/08/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/lago_master_check-merged-trigger/">lago_master_check-merged-trigger</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?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-engine_master_upgrade-from-master_el7_me…">ovirt-engine_master_upgrade-from-master_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_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/ovirt_master_system-tests/">ovirt_master_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/">test-repo_ovirt_experimental_4.0</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <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> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/">vdsm_master_build-artifacts-el7-ppc64le</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?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_master_build-artifacts-el7-x86_64/">vdsm_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> ------=_Part_130_1001960909.1471129204561--

1 0

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

13 Aug '16

------=_Part_119_420693543.1471042802451 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/44//artifact/exported-ar… Cheers, Jenkins ------=_Part_119_420693543.1471042802451 Content-Type: application/octet-stream; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 12/08/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/lago_master_check-merged-trigger/">lago_master_check-merged-trigger</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me…">ovirt-engine_master_upgrade-from-master_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_create-iso-el7-x86_64/">ovirt-live_master_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live </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_master_build-artifacts-fc22-x86_…">ovirt-node-ng_master_build-artifacts-fc22-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests/">ovirt_master_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/">test-repo_ovirt_experimental_4.0</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <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> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/">vdsm_master_build-artifacts-el7-ppc64le</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?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_master_build-artifacts-el7-x86_64/">vdsm_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> ------=_Part_119_420693543.1471042802451--

1 0

Jenkins build became unstable: ovirt_3.6_he-system-tests #296
by jenkins＠jenkins.phx.ovirt.org 12 Aug '16

12 Aug '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/296/changes>

1 1

Jenkins build became unstable: ovirt_4.0_he-system-tests #134
by jenkins＠jenkins.phx.ovirt.org 12 Aug '16

12 Aug '16

See <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/134/changes>

1 1

Install sanlock-python on jenkins slaves
by Adam Litke 12 Aug '16

12 Aug '16

Hi, I would like to remove an old hack in the test code that was put in place at a time when sanlock was not widely available on everyone's development machines. Since it is now installable on all supported platforms I would like to make it a BuildRequires and remove the hack. See the patch [1] here. In order for this patch to pass CI, I need those machines updated with the new BuildRequires: sanlock-python. Could you please install it? Thanks! Note that we do NOT need sanlock (the daemon). We just need the python module in order to satisfy imports. Thanks! -- Adam Litke

2 4

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

12 Aug '16

------=_Part_109_1050803310.1470956404180 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/43//artifact/exported-ar… Cheers, Jenkins ------=_Part_109_1050803310.1470956404180 Content-Type: application/octet-stream; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 11/08/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/lago_master_check-merged-trigger/">lago_master_check-merged-trigger</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc22-x86_…">ovirt-node-ng_master_build-artifacts-fc22-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/">vdsm_master_build-artifacts-el7-ppc64le</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?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_master_build-artifacts-el7-x86_64/">vdsm_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> ------=_Part_109_1050803310.1470956404180--

1 0

Build failed in Jenkins: ovirt_master_system-tests #380
by jenkins＠jenkins.phx.ovirt.org 11 Aug '16

11 Aug '16

See <http://jenkins.ovirt.org/job/ovirt_master_system-tests/380/changes> Changes: [Gal Ben Haim] Install firewalld on engine vm. If firewalld is already installed, make [Eyal Edri] added missing mapping for el7 ppc64le ------------------------------------------ [...truncated 755 lines...] ## took 2032 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log enties: logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log ##! + true + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 Took 1787 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=master SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson4586452256750634987.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=master + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> + OVIRT_SUITE=master + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_master_system-tests/380/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_master_system-tests/380/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/380/artifact/exporte…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then tar cvzf exported-artifacts/logs.tgz "${logs[@]}" rm -rf "${logs[@]}" fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" [ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson3378108196872314658.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs ./ovirt-system-tests/logs/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/state.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/build.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/root.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/state.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/build.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/root.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.clean_rpmdb/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log + rm -rf ./ovirt-system-tests/logs + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-fedora-24-x86_64.fc24.cfg + mock_root=mocker-fedora-24-x86_64.fc24 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-fedora-24-x86_64.fc24' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-tests> --root=mocker-fedora-24-x86_64.fc24 --resultdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test….> Using default... INFO: mock.py version 1.2.18 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> + mock_root=fedora-24-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + [[ -n fedora-24-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep fedora-24-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/fedora-24-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 6

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project
by snaftaly (oVirt JIRA) 11 Aug '16

11 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.p… ] snaftaly edited comment on OVIRT-612 at 8/11/16 6:46 PM: --------------------------------------------------------- Hi [~pvital(a)linux.vnet.ibm.com] Regarding the first part of your 1'st question, your patch needs to be sent to the 'jenkins' project on gerrit.ovirt.org (on the master branch): git://gerrit.ovirt.org/jenkins.git. [~eedri], does he need special permissions for that? Also I'm not sure about the second part of the question. Regarding your 2'nd question, all you need is to add a key named 'trigger-times' in the project yaml, and put the desired value. For example: - project: name: kimchi_project project: kimchi stage: build-artifacts trigger-times: 'H H/6 * * *' ... Regarding question 3, afaik we only support CentOS and Fedora, [~eedri(a)redaht.com] can you confirm that? was (Author: snaftaly(a)redhat.com) Hi [~pvital(a)linux.vnet.ibm.com] Regarding the first part of your 1'st question, your patch needs to be sent to the 'jenkins' project on gerrit.ovirt.org (on the master branch). [~eedri], does he need special permissions for that? Also I'm not sure about the second part of the question. Regarding your 2'nd question, all you need is to add a key named 'trigger-times' in the project yaml, and put the desired value. For example: - project: name: kimchi_project project: kimchi stage: build-artifacts trigger-times: 'H H/6 * * *' ... Regarding question 3, afaik we only support CentOS and Fedora, [~eedri(a)redaht.com] can you confirm that? > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.217.2#100008)

1 0

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project
by snaftaly (oVirt JIRA) 11 Aug '16

11 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.p… ] snaftaly commented on OVIRT-612: -------------------------------- Hi [~pvital(a)linux.vnet.ibm.com] Regarding the first part of your 1'st question, your patch needs to be sent to the 'jenkins' project on gerrit.ovirt.org (on the master branch). [~eedri], does he need special permissions for that? Also I'm not sure about the second part of the question. Regarding your 2'nd question, all you need is to add a key named 'trigger-times' in the project yaml, and put the desired value. For example: - project: name: kimchi_project project: kimchi stage: build-artifacts trigger-times: 'H H/6 * * *' ... Regarding question 3, afaik we only support CentOS and Fedora, [~eedri(a)redaht.com] can you confirm that? > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.217.2#100008)

1 0

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

11 Aug '16

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

1 0

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project
by Paulo Ricardo Paz Vital (oVirt JIRA) 11 Aug '16

11 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.p… ] Paulo Ricardo Paz Vital commented on OVIRT-612: ----------------------------------------------- Hi [~eedri]. Nice documentation, but I still have some questions: 1- I created the project yaml and the scm yaml files in my local repository. How can I submit them to review? I planning to configure only one of our 4 projects to test in a first moment and, in addition, using a specific branch in my fork in github that will include the necessary files to CI Standard. If this first test works well, is it possible to submit updates (point to projects github repository) and improvements in project's files? 2- One of the fields for the project yaml file is the trigger, that can be on-change or timed. In case of timed (that is what I want to use) how can I set the periodicity to run the job? 3 - Reading the documentation, I could see only references to build artifacts to CentOS (EL) and Fedora. We provide artifacts to Ubuntu (Debian) and OpenSUSE, also. Is it possible to build for these distros? > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.217.2#100008)

1 0

[JIRA] (OVIRT-678) Re: please remove the following jenkins jobs
by ybronhei (oVirt JIRA) 11 Aug '16

11 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-678?page=com.atlassian.jira.p… ] ybronhei commented on OVIRT-678: -------------------------------- On Wed, Aug 10, 2016 at 8:06 PM, eyal edri [Administrator] (oVirt JIRA) < This is related to check-patch, check-path and build-artifacts should run over all platforms. as many as possible.. Check-merged is a script to test our functional flows - we run lago, and fedora vm inside that runs vdsmd and some functional test. currently lago vm is fedora based, so vdsm rpms to be installed should be built over *fedora*, therefore the jenkins vm is fedora as well. We don't run the functional tests over centos\el7 vm currently, so running it on jenkins el7 vm is redundant and won't work (the rpms won't fit for the lago vm inside, and it will only test lago run over el7). That's why we ask to run check-merged CI only over f24 (as it used to be not so long ago) -- *Yaniv Bronhaim.* > Re: please remove the following jenkins jobs > -------------------------------------------- > > Key: OVIRT-678 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-678 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > On Wed, Aug 10, 2016 at 3:41 PM, Irit Goihman <igoihman(a)redhat.com> wrote: > > Hi, > > jobs vdsm_master_build-artifacts-el7-ppc64le and vdsm_master_check-merged-el7-x86_64 > > keep failing. They were created recently and should be removed. > > > The ppc64le should be fixed, not removed. > We want ppc64le builds now that we have ppc64le slaves. > The check-merged for el7 is your call, fine for me if you want to remove. > Just weird since el7 is our main target. > > > > Thanks > > > > -- > > Irit Goihman > > Software Engineer > > Red Hat Israel Ltd. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.217.2#100008)

1 0

[JIRA] (OVIRT-680) Move GlusterFS repos to version 3.8 for master jobs
by sbonazzo (oVirt JIRA) 11 Aug '16

11 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-680?page=com.atlassian.jira.p… ] sbonazzo reassigned OVIRT-680: ------------------------------ Assignee: sbonazzo (was: infra) > Move GlusterFS repos to version 3.8 for master jobs > --------------------------------------------------- > > Key: OVIRT-680 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-680 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Reporter: sbonazzo > Assignee: sbonazzo > > Move GlusterFS repos to version 3.8 already available within CentOS Storage SIG for master jobs. -- This message was sent by Atlassian JIRA (v1000.217.2#100008)

1 0

[JIRA] (OVIRT-680) Move GlusterFS repos to version 3.8 for master jobs
by sbonazzo (oVirt JIRA) 11 Aug '16

11 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-680?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-680: --------------------------- Epic Link: OVIRT-400 > Move GlusterFS repos to version 3.8 for master jobs > --------------------------------------------------- > > Key: OVIRT-680 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-680 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Reporter: sbonazzo > Assignee: infra > > Move GlusterFS repos to version 3.8 already available within CentOS Storage SIG for master jobs. -- This message was sent by Atlassian JIRA (v1000.217.2#100008)

1 0

[JIRA] (OVIRT-680) Move GlusterFS repos to version 3.8 for master jobs
by sbonazzo (oVirt JIRA) 11 Aug '16

11 Aug '16

sbonazzo created OVIRT-680: ------------------------------ Summary: Move GlusterFS repos to version 3.8 for master jobs Key: OVIRT-680 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-680 Project: oVirt - virtualization made easy Issue Type: Task Components: Jenkins Reporter: sbonazzo Assignee: infra Move GlusterFS repos to version 3.8 already available within CentOS Storage SIG for master jobs. -- This message was sent by Atlassian JIRA (v1000.217.2#100008)

1 0

[JIRA] (OVIRT-678) Re: please remove the following jenkins jobs
by Irit Goihman (oVirt JIRA) 11 Aug '16

11 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-678?page=com.atlassian.jira.p… ] Irit Goihman commented on OVIRT-678: ------------------------------------ Until recently el7 check merged job didn't exist and we had a job only for fc23 that moved to fc24. check-merged job is using a lago setup with fc24 vm and checks only fc24 packages. We are planning to add el7 vm that will run tests on el7 packages as well. > Re: please remove the following jenkins jobs > -------------------------------------------- > > Key: OVIRT-678 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-678 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > On Wed, Aug 10, 2016 at 3:41 PM, Irit Goihman <igoihman(a)redhat.com> wrote: > > Hi, > > jobs vdsm_master_build-artifacts-el7-ppc64le and vdsm_master_check-merged-el7-x86_64 > > keep failing. They were created recently and should be removed. > > > The ppc64le should be fixed, not removed. > We want ppc64le builds now that we have ppc64le slaves. > The check-merged for el7 is your call, fine for me if you want to remove. > Just weird since el7 is our main target. > > > > Thanks > > > > -- > > Irit Goihman > > Software Engineer > > Red Hat Israel Ltd. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.217.2#100008)

1 0

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

11 Aug '16

------=_Part_104_1469277730.1470870004063 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/42//artifact/exported-ar… Cheers, Jenkins ------=_Part_104_1469277730.1470870004063 Content-Type: application/octet-stream; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 10/08/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/imgbased_master_check-merged-el7-x86_64/">imgbased_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/lago_master_check-merged-trigger/">lago_master_check-merged-trigger</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_coverity-analysis/">ovirt-engine_master_coverity-analysis</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc22-x86_…">ovirt-node-ng_master_build-artifacts-fc22-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-fc22-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_master_system-tests/">ovirt_master_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/">vdsm_master_build-artifacts-el7-ppc64le</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?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_master_check-merged-el7-x86_64/">vdsm_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/vdsm_master_check-merged-fc24-x86_64/">vdsm_master_check-merged-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> ------=_Part_104_1469277730.1470870004063--

1 0