- Infra - oVirt List Archives

[JIRA] (OVIRT-414) [standard-ci] build stage should start only after check-merged stage completes
by eyal edri [Administrator] (oVirt JIRA) 21 Aug '16

21 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-414?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-414: -------------------------------------------- Resolution: Won't Do Status: Done (was: To Do) we have enough power to handle running builds in parallel. there is another ticket that talks about optimizing build params to save time. > [standard-ci] build stage should start only after check-merged stage completes > ------------------------------------------------------------------------------ > > Key: OVIRT-414 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-414 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Affects Versions: Production > Reporter: sbonazzo > Assignee: infra > > In order to save jenkins resources, build stage should be triggered only after check-merged stage passes. -- This message was sent by Atlassian JIRA (v1000.253.3#100011)

1 0

[JIRA] (OVIRT-414) [standard-ci] build stage should start only after check-merged stage completes
by eyal edri [Administrator] (oVirt JIRA) 21 Aug '16

21 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-414?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-414: ------------------------------------------------- I think it will just prolong significantly our output from experimental flows without a major benefit. we now have enough slaves and jenkins power to handle both builds in parallel so I don't see benefit in doing this, we should invest in improving our infra and adding slaves if needed. also, there is another ticket that talks about not building ALL permutations on build_artifacts for ovirt-engine and only doing that for official builds. see https://ovirt-jira.atlassian.net/browse/OVIRT-416 for more info > [standard-ci] build stage should start only after check-merged stage completes > ------------------------------------------------------------------------------ > > Key: OVIRT-414 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-414 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Affects Versions: Production > Reporter: sbonazzo > Assignee: infra > > In order to save jenkins resources, build stage should be triggered only after check-merged stage passes. -- This message was sent by Atlassian JIRA (v1000.253.3#100011)

1 0

[JIRA] (OVIRT-244) Add RpmGrill and rpmlint validation to rpm build jobs
by eyal edri [Administrator] (oVirt JIRA) 21 Aug '16

21 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-244?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-244: -------------------------------------------- Blocked By: requester response Status: Blocked (was: To Do) Please re-assign to relevant maintainer, or close if not going to be implemented. > Add RpmGrill and rpmlint validation to rpm build jobs > ----------------------------------------------------- > > Key: OVIRT-244 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-244 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > I suggest to add rpmlint and RpmGrill (https://gist.github.com/kholia/5899572) validation to rpm build jobs. > It may help finding issues in rpm packaging earlier. -- This message was sent by Atlassian JIRA (v1000.253.3#100011)

1 0

[JIRA] (OVIRT-226) create new job to ensure no sensitive data leak in logs
by eyal edri [Administrator] (oVirt JIRA) 21 Aug '16

21 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-226: -------------------------------------------- Blocked By: pending requester response Status: Blocked (was: To Do) > create new job to ensure no sensitive data leak in logs > ------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.253.3#100011)

1 0

[JIRA] (OVIRT-226) create new job to ensure no sensitive data leak in logs
by eyal edri [Administrator] (oVirt JIRA) 21 Aug '16

21 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-226: ------------------------------------------------- any project that wants to add functionality can add it via the automation dir. We stopped adding specific jobs per project outside of standard CI, this can cause issues in gerrit reviews and required more maintenance. If this is something that can't be done via standard CI, then we need to think how to support it, but it sounds like simple regex on output. feel free to keep this open if you want to implement it for ovirt-engine or other projects, but please assign the relevant maintainer. > create new job to ensure no sensitive data leak in logs > ------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.253.3#100011)

1 0

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

21 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-663?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-663: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > add ppc64le arch builds for oVirt projects > ------------------------------------------ > > Key: OVIRT-663 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-663 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > > now that we have a ppc64le slaves in jenkins we can start building pkg for it and deploy it to resources.ovirt.org. > this ticket will track all pkg progress: > # qemu-kvm - currently pending gluster builds for ppc64le, ETA - next week > # vdsm > # ioprocess > [~danken][~fromani(a)redhat.com] anything else that is not noarch which we need to build? -- This message was sent by Atlassian JIRA (v1000.253.3#100011)

1 0

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

21 Aug '16

See <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/396/changes> Changes: [Gal Ben Haim] Verify that a template exists before trying to export it. ------------------------------------------ [...truncated 706 lines...] ## took 1733 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log enties: logs/mocker-fedora-23-x86_64.fc23.basic_suite_3.6.sh/basic_suite_3.6.sh.log ##! + true + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/d…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/d…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 Took 1561 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/hudson2133658236975941093.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/396/artifact/exported-a…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/396/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/396/artifact/exported-a…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then tar cvzf exported-artifacts/logs.tgz "${logs[@]}" rm -rf "${logs[@]}" fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" [ovirt_3.6_system-tests] $ /bin/bash -xe /tmp/hudson5979019198993670946.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-fedora-23-x86_64.fc23.init/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/state.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/build.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/root.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/state.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/build.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/root.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.basic_suite_3.6.sh/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.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-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_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_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-fedora-23-x86_64.fc23 --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.18 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/ws/ovirt-system-tests/m…> + 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_system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 1

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

21 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-663?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-663: ------------------------------------------------- VDSM EL7 PPC64LE is now built using the new patches: http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/ So the fix is pending merge from VDSM maintainers: https://gerrit.ovirt.org/#/c/62123/ > add ppc64le arch builds for oVirt projects > ------------------------------------------ > > Key: OVIRT-663 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-663 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > now that we have a ppc64le slaves in jenkins we can start building pkg for it and deploy it to resources.ovirt.org. > this ticket will track all pkg progress: > # qemu-kvm - currently pending gluster builds for ppc64le, ETA - next week > # vdsm > # ioprocess > [~danken][~fromani(a)redhat.com] anything else that is not noarch which we need to build? -- This message was sent by Atlassian JIRA (v1000.253.3#100011)

1 0

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

21 Aug '16

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

1 0

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

21 Aug '16

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

1 0