November 2016 - Infra - oVirt List Archives

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

10 Nov '16

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

1 1

[JIRA] (OVIRT-825) re: Assistance
by Billy Boulden (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-825?page=com.atlassian.jira.p… ] Billy Boulden updated OVIRT-825: -------------------------------- Attachment: image002.png We’ve tried that. I need to speak to someone that has set this up before please From: eyal edri [Administrator] (oVirt JIRA) [mailto:jira@ovirt-jira.atlassian.net] Sent: Thursday, November 10, 2016 3:23 PM To: Billy Boulden <Billy.Boulden(a)ecs-federal.com> Subject: [JIRA] (OVIRT-825) re: Assistance [cid:image001.png@01D23B6A.66003EF0] eyal edri [Administrator]<https://ovirt-jira.atlassian.net/secure/ViewProfile.jspa?name=eedri> commented on [By-EMAIL] OVIRT-825<https://ovirt-jira.atlassian.net/browse/OVIRT-825> Re: re: Assistance<https://ovirt-jira.atlassian.net/browse/OVIRT-825> Hi! You've reached the oVirt infrastructure jira, your best place to get help with oVirt will be on the users list users(a)ovirt.org<mailto:users@ovirt.org> or on the devel list: devel(a)ovirt.org<mailto:devel@ovirt.org>. Its almost weekend for most developers, but you might get an answer as early as tomorrow, if not then on by Sunday. cc danken<https://ovirt-jira.atlassian.net/secure/ViewProfile.jspa?name=danken%40redh…> [Add Comment]<https://ovirt-jira.atlassian.net/browse/OVIRT-825#add-comment> Add Comment<https://ovirt-jira.atlassian.net/browse/OVIRT-825#add-comment> This message was sent by Atlassian JIRA (v1000.526.2#100018-sha1:d415428) [Atlassian logo] > re: Assistance > -------------- > > Key: OVIRT-825 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-825 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Billy Boulden > Assignee: infra > Attachments: image002.png > > > Hello, > Having issues installing and configuring OVIRT with the virtual switch. Need to speak with someone > Billy Boulden, C|EH, C|HFI > Systems Engineer > Information Systems Worldwide > A Wholly-Owned Subsidiary of ECS Federal. Inc. > 3865 Wilson Blvd, #600 > Arlington, VA 22203 > Phone: 571-482-4900 x6004 -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by Scott Dickerson (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] Scott Dickerson commented on OVIRT-824: --------------------------------------- Those 2 were triggered manually by [~gshereme(a)redhat.com] On that patch at 11:39AM (or equivalent in your timezone), I triggered the hooks. You can see the BZ update task run, but not the typical Jenkins CI. Patch 65925 [1], that submitted on Oct 31, shows the Jenkins CI tasks at the same time as the BZ updating one. [1] - https://gerrit.ovirt.org/#/c/65925/ > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by Greg Sheremeta (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-824: -------------------------------------- ^ what he said. "Manually triggered by user gshereme for Gerrit: https://gerrit.ovirt.org/66368" > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-825) re: Assistance
by eyal edri [Administrator] (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-825?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-825: ------------------------------------------------- Hi! You've reached the oVirt infrastructure jira, your best place to get help with oVirt will be on the users list users(a)ovirt.org or on the devel list: devel(a)ovirt.org. Its almost weekend for most developers, but you might get an answer as early as tomorrow, if not then on by Sunday. cc [~danken(a)redhat.com] > re: Assistance > -------------- > > Key: OVIRT-825 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-825 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Billy Boulden > Assignee: infra > > Hello, > Having issues installing and configuring OVIRT with the virtual switch. Need to speak with someone > Billy Boulden, C|EH, C|HFI > Systems Engineer > Information Systems Worldwide > A Wholly-Owned Subsidiary of ECS Federal. Inc. > 3865 Wilson Blvd, #600 > Arlington, VA 22203 > Phone: 571-482-4900 x6004 -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-825) re: Assistance
by Billy Boulden (oVirt JIRA) 10 Nov '16

10 Nov '16

Billy Boulden created OVIRT-825: ----------------------------------- Summary: re: Assistance Key: OVIRT-825 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-825 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Billy Boulden Assignee: infra Hello, Having issues installing and configuring OVIRT with the virtual switch. Need to speak with someone Billy Boulden, C|EH, C|HFI Systems Engineer Information Systems Worldwide A Wholly-Owned Subsidiary of ECS Federal. Inc. 3865 Wilson Blvd, #600 Arlington, VA 22203 Phone: 571-482-4900 x6004 -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by eyal edri [Administrator] (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-824: ------------------------------------------------- I see in the patch it just run the 2 jobs successfully: Jenkins CI 8:23 PM ↩ Patch Set 2: Continuous-Integration+1 Build Successful http://jenkins.ovirt.org/job/ovirt-engine-dashboard_master_check-patch-fc24… : SUCCESS http://jenkins.ovirt.org/job/ovirt-engine-dashboard_master_check-patch-el7-… : SUCCESS > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by Scott Dickerson (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] Scott Dickerson commented on OVIRT-824: --------------------------------------- Eyal - Thanks for the add! The repo does have the automation dir with both check-merged.sh and check-patch.sh. Everything worked last week with my last patch. Nothing has changed in the repo since then. I'll take a look at the docs, but I don't see any changes in the repo that would make it stop working now. Other ideas? > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

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

10 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_master_system-tests/773/changes> Changes: [ngoldin] Add fall back to 'extra_sources' file in suite.sh [Ondra Machacek] Remove Fedora 23 build from aaa-misc project [Gil Shinar] Added builds discarder to test experimental [Yedidyah Bar David] nsis-simple-service-plugin: Remove 3.6 ------------------------------------------ [...truncated 754 lines...] ## took 1367 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 1207 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/hudson4808543504114178908.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/773/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_master_system-tests/773/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/773/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/hudson640997540742494374.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.basic_suite_master.sh/ ./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log ./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.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.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 + 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.21 starting (python version = 3.4.3)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_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 2

[JIRA] (OVIRT-824) Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
by eyal edri [Administrator] (oVirt JIRA) 10 Nov '16

10 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-824: ------------------------------------------------- Also, I've added you to the dev role on jenkins, so you can now trigger jobs using the manual trigger job > Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches > ------------------------------------------------------------------- > > Key: OVIRT-824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-824 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Hi, > I submitted an ovirt-engine-dashboard patch [1] last night. The > gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the > normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the > "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run > again. How can we tell if the Jenkins CI triggers on the > ovirt-engine-dashboard gerrit are still configured correctly? What can be > done to fix the problem? > To attempt to work around the issue, I tried the gerrit manual trigger page > [3]. Unfortunately my jenkins account (sdickers) does not have the > appropriate permission to the page. My teammate was able to manually > trigger the job and my patch cleared CI (thanks Greg). Who do I need to > ping to get that permission added to my account? > Regards, > Scott > [1] - https://gerrit.ovirt.org/66368 > [2] - https://bugzilla.redhat.com/1389382 > [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/ > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0