March 2019 - Infra - oVirt List Archives

[JIRA] (OVIRT-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
by Daniel Belenky (oVirt JIRA) 24 Mar '19

24 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2704?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2704: --------------------------------------- You need to update the throttle secion of the '{project}_manual' template in `jobs/confs/yaml/templates/system_tests_templates.yaml` > Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2704 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
by Eyal Edri (oVirt JIRA) 24 Mar '19

24 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2704?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2704: ---------------------------------- I have no objections to increase it. I've updated the job on the UI to allow 10 builds until this is updated via the YAML. Anton - please see if this can updated during the week, I belive its the yaml/templates/standard-pipeline.yaml file that needs updating. -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2704 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
by Daniel Belenky (oVirt JIRA) 24 Mar '19

24 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2704?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2704: --------------------------------------- AFAIK, this job is limited because it never meant to be used as a production job, but as a way to debug things or specifically run some scenario. Nir, can't your tool work directly with the OST manual job? it already allows some concurrency and I guess we could increase it. Otherwise, I don't have any strict objection on increasing the # of concurrent jobs in the manual runner other than that IMO, it wasn't meant to be used in this scenario and it will be hard to find jobs there. > Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2704 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

3 2

[CQ]: 98824,4 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 24 Mar '19

24 Mar '19

Change 98824,4 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/98824/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/347/

1 0

[CQ]: 98801,2 (ovirt-engine-metrics) failed "ovirt-4.3" system tests
by oVirt Jenkins 24 Mar '19

24 Mar '19

Change 98801,2 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/98801/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/346/

1 0

[CQ]: 98801, 2 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Mar '19

24 Mar '19

A system test invoked by the "ovirt-master" change queue including change 98801,2 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 98760,1 (ovirt-engine-metrics) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 98760,1 (ovirt-engine-metrics) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98801/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/98760/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13530/

1 0

[CQ]: 98802, 3 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Mar '19

24 Mar '19

A system test invoked by the "ovirt-master" change queue including change 98802,3 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 98760,1 (ovirt-engine-metrics) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 98760,1 (ovirt-engine-metrics) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98802/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/98760/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13528/

1 0

[CQ]: 98760, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 24 Mar '19

24 Mar '19

Change 98760,1 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/98760/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13526/

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #412
by jenkins＠jenkins.phx.ovirt.org 24 Mar '19

24 Mar '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/41…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 923a9132e19710fe8e84b36bdb5911f0306b24cf (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 923a9132e19710fe8e84b36bdb5911f0306b24cf # timeout=10 Commit message: "ovirt-host-deploy: move master to v2" > git rev-list --no-walk 923a9132e19710fe8e84b36bdb5911f0306b24cf # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins1983236472791656754.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet Error setting up repositories: fedora-base-fc29: Check uncompressed DB failed + reposync_out= Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 773
by jenkins＠jenkins.phx.ovirt.org 24 Mar '19

24 Mar '19

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/773//artifact/exported-a… Cheers, Jenkins

1 0