- Infra - oVirt List Archives

Build failed in Jenkins: ovirt_3.6_he-system-tests #659
by jenkins＠jenkins.phx.ovirt.org 13 Nov '16

13 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/659/changes> Changes: [Yaniv Kaul] Fixes for HE suite [Yedidyah Bar David] nsis-simple-service-plugin: Remove 3.6 ------------------------------------------ [...truncated 418 lines...] ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log ##! + export SUITE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + SUITE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + '[' -z '' ']' + export PREFIX=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + PREFIX=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + false + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + echo 'Suite <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> not found or is not a dir' Suite <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> not found or is not a dir + exit 1 + res=1 + exit 1 + cleanup + rm -rf exported-artifacts + mkdir -p exported-artifacts + [[ -d deployment-he-basic-suite-3.6/current/logs ]] + find deployment-he-basic-suite-3.6 -iname 'nose*.xml' -exec mv '{}' exported-artifacts/ ';' find: ��deployment-he-basic-suite-3.6��: No such file or directory Took 0 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=3.6 SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_3.6_he-system-tests] $ /bin/bash -xe /tmp/hudson3689120829993516547.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=3.6 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + OVIRT_SUITE=3.6 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/659/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/659/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + mv '<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…'> <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/659/artifact/exporte…> mv: cannot stat '<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…'>: No such file or directory POST BUILD TASK : FAILURE END OF POST BUILD TASK : 0 ESCALATE FAILED POST BUILD TASK TO JOB STATUS 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_3.6_he-system-tests] $ /bin/bash -xe /tmp/hudson5362433884214963789.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-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.he_basic_suite_3.6.sh/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_3.6.sh/he_basic_suite_3.6.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_3.6_he-system-tests/ws/ovirt-system-test…> ]] + 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_3.6_he-system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-fedora-23-x86_64.fc23' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-tests> --root=mocker-fedora-23-x86_64.fc23 --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + mock_root=fedora-23-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + [[ -n fedora-23-x86_64-235bec7d0621e95d1cae73d7cf9dc27c ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep fedora-23-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/fedora-23-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Archiving artifacts

1 15

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

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-824: ------------------------------------------------- [~oourfali(a)redhat.com] this was already resolved, please see previous comments. > 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 Oved Ourfali (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira.p… ] Oved Ourfali commented on OVIRT-824: ------------------------------------ Adding Eyal. Thanks, Oved On Thu, Nov 10, 2016 at 9:27 PM, Scott Dickerson <sdickers(a)redhat.com> wrote: > 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 > > 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

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

13 Nov '16

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

1 6

[JIRA] (OVIRT-831) enable spam filters for lago-devel mailing list
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

eyal edri [Administrator] created OVIRT-831: ----------------------------------------------- Summary: enable spam filters for lago-devel mailing list Key: OVIRT-831 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-831 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Can you check if its possible? I keep getting requests to approve spam mails to lago-devel. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-831) enable spam filters for lago-devel mailing list
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-831?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-831: -------------------------------------------- Epic Link: OVIRT-403 > enable spam filters for lago-devel mailing list > ----------------------------------------------- > > Key: OVIRT-831 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-831 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > Can you check if its possible? > I keep getting requests to approve spam mails to lago-devel. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-825) re: Assistance
by danken (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-825?page=com.atlassian.jira.p… ] danken commented on OVIRT-825: ------------------------------ Billy, could you point me to your attempt to discuss this on devel(a)ovirt.org? I could not find any post under your name. A link like http://lists.ovirt.org/pipermail/users/2016-November/043911.html would be most useful. The short answer is that OvS is not yet available, and that we're working hard to make it reach a tech-preview state. To understand about your specific issue, I'll need to hear more details about the failures you see. Let us continue this discussion on the mailing list, please. > 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-830) Vdsm lost its "Forge Author" permission?
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-830?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-830: ------------------------------------------------- You don't see any security implication with this? any user (even malicious) has the potential to forge the author identity? Shouldn't this be restricted to maintainers of the project? [~sbendavi(a)redhat.com] > Vdsm lost its "Forge Author" permission? > ---------------------------------------- > > Key: OVIRT-830 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-830 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Until recently, any registered user could take on somebody else's change, > and post a new patchset to it. > It's very useful when someone wants to fix a typo in someone else's > code, or when we need to take on a work of a sick/vacating developer. > Please amend this. I'm not 100% sure, but it could be fix by setting > "Forge Author" on the vdsm project. > https://gerrit-review.googlesource.com/Documentation/access-control.html#ca… -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

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

13 Nov '16

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

1 3

[JIRA] (OVIRT-830) Vdsm lost its "Forge Author" permission?
by danken (oVirt JIRA) 13 Nov '16

13 Nov '16

danken created OVIRT-830: ---------------------------- Summary: Vdsm lost its "Forge Author" permission? Key: OVIRT-830 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-830 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra Until recently, any registered user could take on somebody else's change, and post a new patchset to it. It's very useful when someone wants to fix a typo in someone else's code, or when we need to take on a work of a sick/vacating developer. Please amend this. I'm not 100% sure, but it could be fix by setting "Forge Author" on the vdsm project. https://gerrit-review.googlesource.com/Documentation/access-control.html#ca… -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0