- Infra - oVirt List Archives

[JIRA] (OVIRT-848) Add support for building containers in oVirt CI
by eyal edri [Administrator] (oVirt JIRA) 16 Nov '16

16 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-848?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-848: ------------------------------------------------- [~fdeutsch] feel free to add more info if I left anything > Add support for building containers in oVirt CI > ----------------------------------------------- > > Key: OVIRT-848 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-848 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > more and more projects in oVirt are starting to build containers and using Docker files in their reops. > We need to start preparing oVirt CI to know how to handle containers and support containers the same way we support rpms today. > This will be a parent task with multiple sub-tasks that will follow, the following is a draft list of what we might need to do to add this support: > # Install Registry server ( maybe use openshift.ovirt.org ) > # Add for standard CI 'build-containers.sh' support > # Add verification steps for the build before publishing to registry > # Look at 3rd party OSS projects that might help and integrate with existing solutions -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[JIRA] (OVIRT-847) Re: [Ovirt github] Please add me as project maintainer on ovirt-vdsmfake
by Pavel Zhukov (oVirt JIRA) 16 Nov '16

16 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-847?page=com.atlassian.jira.p… ] Pavel Zhukov updated OVIRT-847: ------------------------------- Resolution: Fixed Status: Done (was: To Do) Soldev as per last commend > Re: [Ovirt github] Please add me as project maintainer on ovirt-vdsmfake > ------------------------------------------------------------------------ > > Key: OVIRT-847 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-847 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > Adding infra-support to open a ticket. > On Wed, Nov 16, 2016 at 11:26 AM, Roy Golan <rgolan(a)redhat.com> wrote: > > Hi infra > > > > I want admin permission on ovirt/ovirt-vdsmfake GH project so I can manage > > issues and project there. > > Also if not already there, please add mperina as well > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[JIRA] (OVIRT-847) Re: [Ovirt github] Please add me as project maintainer on ovirt-vdsmfake
by rgolan (oVirt JIRA) 16 Nov '16

16 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-847?page=com.atlassian.jira.p… ] rgolan commented on OVIRT-847: ------------------------------ resolved already by Vincent. Thanks. On 16 November 2016 at 11:38, Eyal Edri <eedri(a)redhat.com> wrote: > Adding infra-support to open a ticket. > > On Wed, Nov 16, 2016 at 11:26 AM, Roy Golan <rgolan(a)redhat.com> wrote: > >> Hi infra >> >> I want admin permission on ovirt/ovirt-vdsmfake GH project so I can >> manage issues and project there. >> Also if not already there, please add mperina as well >> >> _______________________________________________ >> Infra mailing list >> Infra(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/infra >> >> > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > Re: [Ovirt github] Please add me as project maintainer on ovirt-vdsmfake > ------------------------------------------------------------------------ > > Key: OVIRT-847 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-847 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > Adding infra-support to open a ticket. > On Wed, Nov 16, 2016 at 11:26 AM, Roy Golan <rgolan(a)redhat.com> wrote: > > Hi infra > > > > I want admin permission on ovirt/ovirt-vdsmfake GH project so I can manage > > issues and project there. > > Also if not already there, please add mperina as well > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[Ovirt github] Please add me as project maintainer on ovirt-vdsmfake
by Roy Golan 16 Nov '16

16 Nov '16

Hi infra I want admin permission on ovirt/ovirt-vdsmfake GH project so I can manage issues and project there. Also if not already there, please add mperina as well

2 2

[JIRA] (OVIRT-846) [URGENT] all specs related jobs triggered by unrelated patches
by eyal edri [Administrator] (oVirt JIRA) 16 Nov '16

16 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-846?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-846: ----------------------------------------------- Assignee: Gil Shinar (was: infra) we found out it was caused by the patch to update created/merged rpms. The patch probably changed the template the rel-eng jobs are using, triggering multi jobs as a result. > [URGENT] all specs related jobs triggered by unrelated patches > -------------------------------------------------------------- > > Key: OVIRT-846 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-846 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: Gil Shinar > > Some recent patches now triggers all the jobs related to releng-tools even if the patch is unrelated. > See for example: https://gerrit.ovirt.org/#/c/66783/ -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[JIRA] (OVIRT-847) Re: [Ovirt github] Please add me as project maintainer on ovirt-vdsmfake
by eyal edri [Administrator] (oVirt JIRA) 16 Nov '16

16 Nov '16

eyal edri [Administrator] created OVIRT-847: ----------------------------------------------- Summary: Re: [Ovirt github] Please add me as project maintainer on ovirt-vdsmfake Key: OVIRT-847 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-847 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra Adding infra-support to open a ticket. On Wed, Nov 16, 2016 at 11:26 AM, Roy Golan <rgolan(a)redhat.com> wrote: > Hi infra > > I want admin permission on ovirt/ovirt-vdsmfake GH project so I can manage > issues and project there. > Also if not already there, please add mperina as well > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

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

16 Nov '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/748/changes> Changes: [Yaniv Kaul] Explictly use systemctl for services. [Fabian Deutsch] mock_cleanup: Drop all leftover libvirt domains [Eyal Edri] whitesource: update project name to oVirt ------------------------------------------ [...truncated 757 lines...] ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/d…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/d…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 1545 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=3.6 SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_3.6_system-tests] $ /bin/bash -xe /tmp/hudson8286416771805850752.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=3.6 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> + OVIRT_SUITE=3.6 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/748/artifact/exported-a…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/748/artifact/exported-a…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/e…> <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/748/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" # Drop all left over libvirt domains for UUID in $(virsh list --all --uuid); do virsh destroy $UUID || : sleep 2 virsh undefine --remove-all-storage --storage vda --snapshots-metadata $UUID || : done [ovirt_3.6_system-tests] $ /bin/bash -xe /tmp/hudson2419942323115778781.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + 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-epel-7-x86_64.el7.init/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/state.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/build.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.init/root.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/state.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/build.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.install_packages/root.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.clean_rpmdb/stdout_stderr.log ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.basic_suite_3.6.sh/ ./ovirt-system-tests/logs/mocker-epel-7-x86_64.el7.basic_suite_3.6.sh/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_system-tests/ws/ovirt-system-tests/m…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-epel-7-x86_64.el7.cfg + mock_root=mocker-epel-7-x86_64.el7 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-epel-7-x86_64.el7' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/l….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.5.2)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/m…> + mock_root=epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + [[ -n epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/epel-7-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/> ++ virsh list --all --uuid POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 1

[oVirt Jenkins] repos_3.6_check-closure_el6_merged - Build # 76 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 Nov '16

16 Nov '16

------=_Part_477_669384771.1479278048031 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el6_merged/ Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el6_merged/76/ Build Number: 76 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #76 [Gil Shinar] Removed build artifacts on fc24 with ppc64le [Gil Shinar] Better error message when deleting a job [Sandro Bonazzola] node: move email recipient to fabiand [Fabian Deutsch] mock_cleanup: Drop all leftover libvirt domains [Eyal Edri] whitesource: update project name to oVirt ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_477_669384771.1479278048031--

1 0

[JIRA] (OVIRT-846) [URGENT] all specs related jobs triggered by unrelated patches
by sbonazzo (oVirt JIRA) 16 Nov '16

16 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-846?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-846: --------------------------- Description: Some recent patches now triggers all the jobs related to releng-tools even if the patch is unrelated. See for example: https://gerrit.ovirt.org/#/c/66783/ was: Some recent patches now triggers qemu-lvm-ev jobs even if the patch is unrelated. See for example: https://gerrit.ovirt.org/#/c/66783/ > [URGENT] all specs related jobs triggered by unrelated patches > -------------------------------------------------------------- > > Key: OVIRT-846 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-846 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: infra > > Some recent patches now triggers all the jobs related to releng-tools even if the patch is unrelated. > See for example: https://gerrit.ovirt.org/#/c/66783/ -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[JIRA] (OVIRT-846) [URGENT] all specs related jobs triggered by unrelated patches
by sbonazzo (oVirt JIRA) 16 Nov '16

16 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-846?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-846: --------------------------- Summary: [URGENT] all specs related jobs triggered by unrelated patches (was: [URGENT] qemu-kvm-ev jobs triggered by unrelated patches) > [URGENT] all specs related jobs triggered by unrelated patches > -------------------------------------------------------------- > > Key: OVIRT-846 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-846 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: infra > > Some recent patches now triggers qemu-lvm-ev jobs even if the patch is unrelated. > See for example: https://gerrit.ovirt.org/#/c/66783/ -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[JIRA] (OVIRT-846) qemu-kvm-ev jobs triggered by unrelated patches
by sbonazzo (oVirt JIRA) 16 Nov '16

16 Nov '16

sbonazzo created OVIRT-846: ------------------------------ Summary: qemu-kvm-ev jobs triggered by unrelated patches Key: OVIRT-846 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-846 Project: oVirt - virtualization made easy Issue Type: Task Reporter: sbonazzo Assignee: infra Some recent patches now triggers qemu-lvm-ev jobs even if the patch is unrelated. See for example: https://gerrit.ovirt.org/#/c/66783/ -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[JIRA] (OVIRT-846) qemu-kvm-ev jobs triggered by unrelated patches
by sbonazzo (oVirt JIRA) 16 Nov '16

16 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-846?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-846: --------------------------- Epic Link: OVIRT-400 > qemu-kvm-ev jobs triggered by unrelated patches > ----------------------------------------------- > > Key: OVIRT-846 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-846 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: infra > > Some recent patches now triggers qemu-lvm-ev jobs even if the patch is unrelated. > See for example: https://gerrit.ovirt.org/#/c/66783/ -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[JIRA] (OVIRT-846) [URGENT] qemu-kvm-ev jobs triggered by unrelated patches
by sbonazzo (oVirt JIRA) 16 Nov '16

16 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-846?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-846: --------------------------- Summary: [URGENT] qemu-kvm-ev jobs triggered by unrelated patches (was: qemu-kvm-ev jobs triggered by unrelated patches) > [URGENT] qemu-kvm-ev jobs triggered by unrelated patches > -------------------------------------------------------- > > Key: OVIRT-846 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-846 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: infra > > Some recent patches now triggers qemu-lvm-ev jobs even if the patch is unrelated. > See for example: https://gerrit.ovirt.org/#/c/66783/ -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[JIRA] (OVIRT-845) Build oVirt 4.0.6 RC1
by sbonazzo (oVirt JIRA) 16 Nov '16

16 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-845?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-845: --------------------------- Epic Link: OVIRT-411 > Build oVirt 4.0.6 RC1 > --------------------- > > Key: OVIRT-845 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-845 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

[JIRA] (OVIRT-845) Build oVirt 4.0.6 RC1
by sbonazzo (oVirt JIRA) 16 Nov '16

16 Nov '16

sbonazzo created OVIRT-845: ------------------------------ Summary: Build oVirt 4.0.6 RC1 Key: OVIRT-845 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-845 Project: oVirt - virtualization made easy Issue Type: Task Components: Repositories Mgmt Reporter: sbonazzo Assignee: infra Priority: Highest -- This message was sent by Atlassian JIRA (v1000.550.1#100018)

1 0

Fwd: Linode Support Ticket 7156775 - Critical Xen Maintenance / Reboot Schedule
by Karsten Wade 15 Nov '16

15 Nov '16

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --g9BeT0r2PKq1TcR1b4AXeiU3UXAxwkWIQ Content-Type: multipart/mixed; boundary="XoqTt80bHUtfEg8mmbt6CVL3pSVUp5UAI"; protected-headers="v1" From: Karsten Wade <quaid(a)iquaid.org> To: infra <infra(a)ovirt.org> Message-ID: <91f74acb-36c7-f954-2362-73af9d80d626(a)iquaid.org> Subject: Fwd: Linode Support Ticket 7156775 - Critical Xen Maintenance / Reboot Schedule References: <2108364301.128572.1479261262542.JavaMail.cfusion(a)mail2.linode.com> In-Reply-To: <2108364301.128572.1479261262542.JavaMail.cfusion(a)mail2.linode.com> --XoqTt80bHUtfEg8mmbt6CVL3pSVUp5UAI Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable The irony here is palpable ... What's the plan or blocker on migrating off this Linode instance? -------- Forwarded Message -------- Subject: Linode Support Ticket 7156775 - Critical Xen Maintenance / Reboot Schedule Date: Tue, 15 Nov 2016 20:54:22 -0500 (EST) From: support(a)linode.com To: quaid(a)iquaid.org Hello, Linode has received a Xen Security Advisory (XSA) that requires us to perform updates to our legacy Xen host servers. We must complete these updates before November 22nd. For general information, please see our status page post below: https://status.linode.com/incidents/6lqznlfwlv1r Your Linodes have been assigned a maintenance window in which a reboot will occur. These times are listed within the Linode Manager[1] in the timezone set in your user's My Profile[2]. Your schedule in UTC timezone is as follows: * 2016-11-21 12:00:00 PM UTC - linodeXXXXXXXX Upgrading to KVM will allow you to avoid this maintenance entirely. You can use the =E2=80=9CUpgrade to KVM=E2=80=9D link in your Linode=E2=80=99= s dashboard to move to KVM. Please note that KVM upgrades are not available in Tokyo at this time. More KVM upgrading information can be found here: https://www.linode.com/docs/platform/kvm-reference We strongly recommend you read through our Reboot guide, which will help you prepare your Linode for these reboots. After going through that guide, we recommend you reboot your Linode at a convenient time to ensure your services come up correctly. The Reboot guide is available her= e: https://www.linode.com/docs/uptime/reboot-survival-guide During the maintenance window, your Linodes will be cleanly shut down while we perform the updates. Your Linodes will be inaccessible during this time. A two-hour window is allocated, however the actual downtime should be much less. After the maintenance, each Linode will be returned to its last state (running or powered off). Please let us know if there is anything we can do to assist. [1] <https://manager.linode.com/linodes> [2] <https://manager.linode.com/profile> --Linode --- https://manager.linode.com/support/ticket/7156775 --XoqTt80bHUtfEg8mmbt6CVL3pSVUp5UAI-- --g9BeT0r2PKq1TcR1b4AXeiU3UXAxwkWIQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlgr5TcACgkQ2ZIOBq0ODEFbdgCgiedG8EAYDuwjg7HFPOpWAC0S 5K0An3tyA9/PzAv/HPLb2dgUd/RuHP0P =rBqw -----END PGP SIGNATURE----- --g9BeT0r2PKq1TcR1b4AXeiU3UXAxwkWIQ--

1 0

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

15 Nov '16

------=_Part_475_1044194490.1479250809204 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/139//artifact/exported-a… Cheers, Jenkins ------=_Part_475_1044194490.1479250809204 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 - 15/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/opstools-ansible_master_create-rpms-el7-x86_64…">opstools-ansible_master_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/opstools-ansible_master_create-rpms-fc24-x86_6…">opstools-ansible_master_create-rpms-fc24-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86…">ovirt-appliance_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-nodejs-modules_4.0_create-rpms-el…">ovirt-engine-nodejs-modules_4.0_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-nodejs-modules_4.0_create-rpms-fc…">ovirt-engine-nodejs-modules_4.0_create-rpms-fc23-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-nodejs-modules_master_create-rpms…">ovirt-engine-nodejs-modules_master_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-nodejs-modules_master_create-rpms…">ovirt-engine-nodejs-modules_master_create-rpms-fc24-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-nodejs_4.0_create-rpms-el7-x86_64…">ovirt-engine-nodejs_4.0_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-nodejs_4.0_create-rpms-fc23-x86_6…">ovirt-engine-nodejs_4.0_create-rpms-fc23-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_create-rpms-el7-x86…">ovirt-engine-nodejs_master_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_create-rpms-fc24-x8…">ovirt-engine-nodejs_master_create-rpms-fc24-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge…">ovirt-engine_master_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_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-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-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_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/">ovirt_3.6_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/qemu_3.6_create-rpms-el7-ppc64le_merged/">qemu_3.6_create-rpms-el7-ppc64le_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/qemu_3.6_create-rpms-el7-x86_64_merged/">qemu_3.6_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/qemu_4.0_create-rpms-el7-ppc64le_merged/">qemu_4.0_create-rpms-el7-ppc64le_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/qemu_4.0_create-rpms-el7-x86_64_merged/">qemu_4.0_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/qemu_master_create-rpms-el7-ppc64le_merged/">qemu_master_create-rpms-el7-ppc64le_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/qemu_master_create-rpms-el7-x86_64_merged/">qemu_master_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repoman_master_check-merged-el7-x86_64/">repoman_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/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system_update_puppet/">system_update_puppet</a> </td><td> No Description </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/unboundid-ldapsdk_3.6_create-rpms-el6-x86_64_m…">unboundid-ldapsdk_3.6_create-rpms-el6-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/unboundid-ldapsdk_3.6_create-rpms-el7-x86_64_m…">unboundid-ldapsdk_3.6_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/unboundid-ldapsdk_4.0_create-rpms-el7-x86_64_m…">unboundid-ldapsdk_4.0_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/unboundid-ldapsdk_master_create-rpms-el7-x86_6…">unboundid-ldapsdk_master_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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_build-artifacts-fc24-x86_64/">vdsm_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/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> ------=_Part_475_1044194490.1479250809204--

1 0

Jenkins build became unstable: ovirt_3.6_he-system-tests #688
by jenkins＠jenkins.phx.ovirt.org 15 Nov '16

15 Nov '16

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

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #3638 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 15 Nov '16

15 Nov '16

------=_Part_471_479579442.1479238518266 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3638/, Build Number: 3638, Build Status: SUCCESS ------=_Part_471_479579442.1479238518266--

1 0

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

15 Nov '16

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

1 19

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3366 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 15 Nov '16

15 Nov '16

------=_Part_467_2008351848.1479232581461 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3366/, Build Number: 3366, Build Status: SUCCESS ------=_Part_467_2008351848.1479232581461--

1 0

[JIRA] (OVIRT-844) move node builds jobs to run on Lago VM
by eyal edri [Administrator] (oVirt JIRA) 15 Nov '16

15 Nov '16

eyal edri [Administrator] created OVIRT-844: ----------------------------------------------- Summary: move node builds jobs to run on Lago VM Key: OVIRT-844 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-844 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri [Administrator] Assignee: infra the node jobs keeps failing on cleanup issues which will be solved if we move the job to run on Lago. lets do it for master(4.1) as POC and see if it helps. http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… the job doesn't nessasarily needs a BM slave, so we will need to check what infra changes are needed (puppet classes to install lago?) in order to run it. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-844) move node builds jobs to run on Lago VM
by eyal edri [Administrator] (oVirt JIRA) 15 Nov '16

15 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-844?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-844: -------------------------------------------- Epic Link: OVIRT-400 > move node builds jobs to run on Lago VM > --------------------------------------- > > Key: OVIRT-844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-844 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > the node jobs keeps failing on cleanup issues which will be solved if we move the job to run on Lago. > lets do it for master(4.1) as POC and see if it helps. > http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… > the job doesn't nessasarily needs a BM slave, so we will need to check what infra changes are needed (puppet classes to install lago?) in order to run it. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

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

15 Nov '16

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

1 1

oVirt 4.0.6 RC1 merge / branch / tag / bugzilla reminder
by Rafael Martins 15 Nov '16

15 Nov '16

All stable branch maintainers, please make sure to - merge all relevant open bugs until Wednesday morning 11:00 AM TLV time. For each package that need to be built (i.e oVirt product) please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.6, tr: 4.0.6) A list of bugs that require attention is here: - https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… Rafael

1 0

Gerrit->Bugzilla update failed
by Shmuel Melamud 15 Nov '16

15 Nov '16

Hi! Seems there is a problem with gerrit-hooks as related to Bugzilla updates. With this change https://gerrit.ovirt.org/#/c/66774/ gerrit-hooks says that Bug-Url is absent, while it is present and correct. With this change: https://gerrit.ovirt.org/#/c/66723/ Bugzilla was not updated, while Bug-Url is present and correct. Shmuel

3 5

[JIRA] (OVIRT-843) Bug-Url is not recognized properly
by Shlomo Ben David (oVirt JIRA) 15 Nov '16

15 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-843?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-843: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > Bug-Url is not recognized properly > ---------------------------------- > > Key: OVIRT-843 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-843 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: Shlomo Ben David > Priority: High > > Example: > Check Bug-Url::WARN, no bug url/s found <== !!!! > Check Public Bug::#1373573::OK, public bug <== But OK here > Example changes: > https://gerrit.ovirt.org/#/c/66723/ > https://gerrit.ovirt.org/#/c/66774/ -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-843) Bug-Url is not recognized properly
by Shlomo Ben David (oVirt JIRA) 15 Nov '16

15 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-843?page=com.atlassian.jira.p… ] Shlomo Ben David commented on OVIRT-843: ---------------------------------------- Hi Pavel, It is not a bug, the user added the bug-url with wrong convention: https://bugzilla.redhat.com/*show_bug.cgi?id=*1335642 While it should be added as: https://bugzilla.redhat.com/1335642 > Bug-Url is not recognized properly > ---------------------------------- > > Key: OVIRT-843 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-843 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > Priority: High > > Example: > Check Bug-Url::WARN, no bug url/s found <== !!!! > Check Public Bug::#1373573::OK, public bug <== But OK here > Example changes: > https://gerrit.ovirt.org/#/c/66723/ > https://gerrit.ovirt.org/#/c/66774/ -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-843) Bug-Url is not recognized properly
by Pavel Zhukov (oVirt JIRA) 15 Nov '16

15 Nov '16

Pavel Zhukov created OVIRT-843: ---------------------------------- Summary: Bug-Url is not recognized properly Key: OVIRT-843 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-843 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Pavel Zhukov Assignee: infra Priority: High Example: Check Bug-Url::WARN, no bug url/s found <== !!!! Check Public Bug::#1373573::OK, public bug <== But OK here Example changes: https://gerrit.ovirt.org/#/c/66723/ https://gerrit.ovirt.org/#/c/66774/ -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

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

15 Nov '16

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

1 2

[JIRA] (OVIRT-842) Artifactory service is restart by puppet in the loop
by Pavel Zhukov (oVirt JIRA) 15 Nov '16

15 Nov '16

Pavel Zhukov created OVIRT-842: ---------------------------------- Summary: Artifactory service is restart by puppet in the loop Key: OVIRT-842 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-842 Project: oVirt - virtualization made easy Issue Type: Epic Reporter: Pavel Zhukov Assignee: infra Priority: High For some reasons systemd reports artifactory as failed state while it works normally. This cause service to be restarted in the loop and DoS as the result. As a workaround I've disabled puppet service to prevent artifactory from restarts and start it manually. Looks like PID file is not created. As far as I know we had problem with free space on this server -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

Jenkins build is back to stable : ovirt_3.6_he-system-tests #685
by jenkins＠jenkins.phx.ovirt.org 15 Nov '16

15 Nov '16

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

1 0

Re: ** PROBLEM Service Alert: ovirt-mirrorchecker/www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync is CRITICAL **
by Nadav Goldin 15 Nov '16

15 Nov '16

Hi, the oVirt mirror site stopped synchronising again few days ago, can you please check? Thanks, Nadav. On Tue, Nov 15, 2016 at 11:56 AM, icinga <icinga(a)monitoring.ovirt.org> wrote: > ***** Icinga ***** > > Notification Type: PROBLEM > > Service: www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync > Host: ovirt-mirrorchecker > Address: 66.187.230.105 > State: CRITICAL > > Date/Time: Tue Nov 15 09:56:58 UTC 2016 > > Additional Info: > > CRITICAL - 713972 seconds since last sync, which are 198.3256 hours.

1 0

vdsm_master_build-artifacts-fc24-ppc64le job keeps failing
by Irit Goihman 15 Nov '16

15 Nov '16

Hi, It seems like there's a problem with this job. All the jobs fail because of this error: Start: yum install*15:11:34* ERROR: Command failed. See logs for output. Can you please check? Thanks, -- Irit Goihman Software Engineer Red Hat Israel Ltd.

5 11

OST failing for master - might be related to change in 'remove vm guest agent ...'
by Eyal Edri 15 Nov '16

15 Nov '16

Failing after this patch was merged: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc24-x86_6… [0][1] https://gerrit.ovirt.org/#/c/65860/ [0] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3329/conso… [1] Lago log: 16-11-14 13:54:35,485::ssh.py::ssh::55::lago.ssh::DEBUG::Running e0703cf0 on lago-basic-suite-master-host0: /usr/bin/systemctl status --lines=0 qemu-guest-agent 2016-11-14 13:54:35,528::ssh.py::ssh::80::lago.ssh::DEBUG::Command e0703cf0 on lago-basic-suite-master-host0 returned with 0 2016-11-14 13:54:35,528::ssh.py::ssh::88::lago.ssh::DEBUG::Command e0703cf0 on lago-basic-suite-master-host0 output: â— qemu-guest-agent.service - QEMU Guest Agent Loaded: loaded (/usr/lib/systemd/system/qemu-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2016-11-14 08:29:16 EST; 25min ago Main PID: 476 (qemu-ga) CGroup: /system.slice/qemu-guest-agent.service â””â”€476 /usr/bin/qemu-ga --method=virtio-serial --path=/dev/virtio-ports/org.qemu.guest_agent.0 --blacklist=guest-file-open guest-file-close guest-file-read guest-file-write guest-file-seek guest-file-flush -F/etc/qemu-ga/fsfreeze-hook 2016-11-14 13:54:37,086::log_utils.py::end_log_task::649::root::ERROR:: # [Thread-2] lago-basic-suite-master-engine: [31mERROR [0m (in 0:00:02) 2016-11-14 13:54:37,087::utils.py::_ret_via_queue::57::lago.utils::ERROR::Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1117, in _collect_artifacts vm.collect_artifacts(path) File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 456, in collect_artifacts ) for guest_path in self._artifact_paths() File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 302, in extract_paths return self.provider.extract_paths(paths, *args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/vm.py", line 194, in extract_paths self._extract_paths_live(paths=paths) File "/usr/lib/python2.7/site-packages/lago/vm.py", line 409, in _extract_paths_live self._extract_paths_dead(paths=paths) File "/usr/lib/python2.7/site-packages/lago/vm.py", line 423, in _extract_paths_dead gfs_cli.launch() File "/usr/lib64/python2.7/site-packages/guestfs.py", line 4731, in launch r = libguestfsmod.launch (self._o) RuntimeError: guestfs_launch failed. This usually means the libguestfs appliance failed to start or crashed. See http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs or run 'libguestfs-test-tool' and post the *complete* output into a bug report or message to the libguestfs mailing list. Exception from test: *13:54:37* [36m # [Thread-2] lago-basic-suite-master-engine: [31mERROR [0m (in 0:00:02) [0m*13:54:37* [31mError while running thread*13:54:37* Traceback (most recent call last):*13:54:37* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue*13:54:37* queue.put({'return': func()})*13:54:37* File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1117, in _collect_artifacts*13:54:37* vm.collect_artifacts(path)*13:54:37* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 456, in collect_artifacts*13:54:37* ) for guest_path in self._artifact_paths()*13:54:37* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 302, in extract_paths*13:54:37* return self.provider.extract_paths(paths, *args, **kwargs)*13:54:37* File "/usr/lib/python2.7/site-packages/lago/vm.py", line 194, in extract_paths*13:54:37* self._extract_paths_live(paths=paths)*13:54:37* File "/usr/lib/python2.7/site-packages/lago/vm.py", line 409, in _extract_paths_live*13:54:37* self._extract_paths_dead(paths=paths)*13:54:37* File "/usr/lib/python2.7/site-packages/lago/vm.py", line 423, in _extract_paths_dead*13:54:37* gfs_cli.launch()*13:54:37* File "/usr/lib64/python2.7/site-packages/guestfs.py", line 4731, in launch*13:54:37* r = libguestfsmod.launch (self._o)*13:54:37* RuntimeError: guestfs_launch failed.*13:54:37* This usually means the libguestfs appliance failed to start or crashed.*13:54:37* See http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*13:54:37* or run 'libguestfs-test-tool' and post the *complete* output into a*13:54:37* bug report or message to the libguestfs mailing list. [0m*13:54:47* [36m # [Thread-3] lago-basic-suite-master-host1: [32mSuccess [0m (in 0:00:11) [0m*13:54:47* [36m # [Thread-1] lago-basic-suite-master-host0: [32mSuccess [0m (in 0:00:11) [0m*13:54:47* [36m@ Collect artifacts: [31mERROR [0m (in 0:00:11) [0m*13:54:47* [31mError occured, aborting*13:54:47* Traceback (most recent call last):*13:54:47* File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 259, in do_run*13:54:47* self.cli_plugins[args.ovirtverb].do_run(args)*13:54:47* File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 180, in do_run*13:54:47* self._do_run(**vars(args))*13:54:47* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 490, in wrapper*13:54:47* return func(*args, **kwargs)*13:54:47* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 501, in wrapper*13:54:47* return func(*args, prefix=prefix, **kwargs)*13:54:47* File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 228, in do_ovirt_collect*13:54:47* prefix.collect_artifacts(output)*13:54:47* File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 615, in wrapper*13:54:47* return func(*args, **kwargs)*13:54:47* File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1121, in collect_artifacts*13:54:47* self.virt_env.get_vms().values(),*13:54:47* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 97, in invoke_in_parallel*13:54:47* vt.join_all()*13:54:47* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue*13:54:47* queue.put({'return': func()})*13:54:47* File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1117, in _collect_artifacts*13:54:47* vm.collect_artifacts(path)*13:54:47* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 456, in collect_artifacts*13:54:47* ) for guest_path in self._artifact_paths()*13:54:47* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 302, in extract_paths*13:54:47* return self.provider.extract_paths(paths, *args, **kwargs)*13:54:47* File "/usr/lib/python2.7/site-packages/lago/vm.py", line 194, in extract_paths*13:54:47* self._extract_paths_live(paths=paths)*13:54:47* File "/usr/lib/python2.7/site-packages/lago/vm.py", line 409, in _extract_paths_live*13:54:47* self._extract_paths_dead(paths=paths)*13:54:47* File "/usr/lib/python2.7/site-packages/lago/vm.py", line 423, in _extract_paths_dead*13:54:47* gfs_cli.launch()*13:54:47* File "/usr/lib64/python2.7/site-packages/guestfs.py", line 4731, in launch*13:54:47* r = libguestfsmod.launch (self._o)*13:54:47* RuntimeError: guestfs_launch failed.*13:54:47* This usually means the libguestfs appliance failed to start or crashed.*13:54:47* See http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*13:54:47* or run 'libguestfs-test-tool' and post the *complete* output into a*13:54:47* bug report or message to the libguestfs mailing list. [0m On Mon, Nov 14, 2016 at 3:55 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ > master/3329/, > Build Number: 3329, > Build Status: FAILURE > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

2 1

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

14 Nov '16

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

1 5

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

14 Nov '16

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

1 2

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

14 Nov '16

------=_Part_396_285032562.1479164410400 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/138//artifact/exported-a… Cheers, Jenkins ------=_Part_396_285032562.1479164410400 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/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge…">ovirt-engine_master_upgrade-from-3.6_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-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_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_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_image-ng-system-tests/">ovirt_4.0_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/qemu_3.6_create-rpms-el7-ppc64le_merged/">qemu_3.6_create-rpms-el7-ppc64le_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/qemu_4.0_create-rpms-el7-ppc64le_merged/">qemu_4.0_create-rpms-el7-ppc64le_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/qemu_master_create-rpms-el7-ppc64le_merged/">qemu_master_create-rpms-el7-ppc64le_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repoman_master_check-merged-el7-x86_64/">repoman_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/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system_update_puppet/">system_update_puppet</a> </td><td> No Description </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc24-ppc64le/">vdsm_master_build-artifacts-fc24-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> ------=_Part_396_285032562.1479164410400--

1 0

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

14 Nov '16

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

1 1

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

14 Nov '16

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

1 1

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

14 Nov '16

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

1 1

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

14 Nov '16

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

1 1

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

14 Nov '16

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

1 2

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

14 Nov '16

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

1 2

[JIRA] (OVIRT-841) Modify check_merged jobs to run as merge gates instead of post merge
by Barak Korren (oVirt JIRA) 14 Nov '16

14 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-841?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-841: ------------------------------- Epic Link: OVIRT-400 > Modify check_merged jobs to run as merge gates instead of post merge > -------------------------------------------------------------------- > > Key: OVIRT-841 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-841 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > This can be done with Zuul - as tracked by OVIRT-734, but can also be done with just Jenkins in the short term. > This ticket is to track short-term gate implementation without Zuul, it is separate from the Zuul ticket, because if we do end up deploying Zuul, we will probably have to let it do this too. > We need to also communicate with the developers to ask what will the prefer as the way to signal Jenkins to run the gate, there are two options we can consider: > # Use code-review+2 > # Use some new "approve" flag (Like OpenStack) -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-841) Modify check_merged jobs to run as merge gates instead of post merge
by Barak Korren (oVirt JIRA) 14 Nov '16

14 Nov '16

Barak Korren created OVIRT-841: ---------------------------------- Summary: Modify check_merged jobs to run as merge gates instead of post merge Key: OVIRT-841 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-841 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: High This can be done with Zuul - as tracked by OVIRT-734, but can also be done with just Jenkins in the short term. This ticket is to track short-term gate implementation without Zuul, it is separate from the Zuul ticket, because if we do end up deploying Zuul, we will probably have to let it do this too. We need to also communicate with the developers to ask what will the prefer as the way to signal Jenkins to run the gate, there are two options we can consider: # Use code-review+2 # Use some new "approve" flag (Like OpenStack) -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-841) Modify check_merged jobs to run as merge gates instead of post merge
by Barak Korren (oVirt JIRA) 14 Nov '16

14 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-841?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-841: ---------------------------------- Assignee: Barak Korren (was: infra) > Modify check_merged jobs to run as merge gates instead of post merge > -------------------------------------------------------------------- > > Key: OVIRT-841 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-841 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > This can be done with Zuul - as tracked by OVIRT-734, but can also be done with just Jenkins in the short term. > This ticket is to track short-term gate implementation without Zuul, it is separate from the Zuul ticket, because if we do end up deploying Zuul, we will probably have to let it do this too. > We need to also communicate with the developers to ask what will the prefer as the way to signal Jenkins to run the gate, there are two options we can consider: > # Use code-review+2 > # Use some new "approve" flag (Like OpenStack) -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

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

14 Nov '16

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

1 2

[JIRA] (OVIRT-840) oVirt Monitoring & Reporting
by eyal edri [Administrator] (oVirt JIRA) 14 Nov '16

14 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-840?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-840: -------------------------------------------- Epic Name: oVirt Monitoring & Reporting (was: Monitoring & Reporting) > oVirt Monitoring & Reporting > ---------------------------- > > Key: OVIRT-840 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-840 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-840) oVirt Monitoring & Reporting
by eyal edri [Administrator] (oVirt JIRA) 14 Nov '16

14 Nov '16

eyal edri [Administrator] created OVIRT-840: ----------------------------------------------- Summary: oVirt Monitoring & Reporting Key: OVIRT-840 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-840 Project: oVirt - virtualization made easy Issue Type: Epic Reporter: eyal edri [Administrator] Assignee: infra -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0