- Infra - oVirt List Archives

[CQ]: 104815, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104815,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104815/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17189/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-7.6-el7-x86_64 #85
by jenkins＠jenkins.phx.ovirt.org 20 Nov '19

20 Nov '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-7.6-el7-x86…> Changes: ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-7.6-el7-x86…> 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 --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 9c6683c529b31a0f471a5690de84fe7bf590a5d8 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9c6683c529b31a0f471a5690de84fe7bf590a5d8 Commit message: "usrc.py: allow manual updates of upstream sources" > git rev-list --no-walk 9c6683c529b31a0f471a5690de84fe7bf590a5d8 # timeout=10 [system-sync_mirrors-centos-updates-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins8916253860117318350.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-7.6-el7 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 centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-updates-7.6-el7 + 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 centos-updates-7.6-el7 yum + local repo_name=centos-updates-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-updates-7.6-el7 /var/www/html/repos/yum/centos-updates-7.6-el7/base + check_yum_sync_needed centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-updates-7.6-el7 + 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/centos-updates-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-updates-7.6-el7 ++ 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=centos-updates-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-updates-7.6-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[CQ]: 104221, 9 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104221,9 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 104699,3 (ovirt-system-tests) 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 104699,3 (ovirt-system-tests) 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/104221/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104699/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17186/

1 0

[CQ]: 104826, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104826,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104826/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17182/

1 0

[CQ]: 104822, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104822,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104822/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17178/

1 0

[CQ]: 104823, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104823,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104823/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17174/

1 0

[CQ]: 104835,2 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 20 Nov '19

20 Nov '19

Change 104835,2 (jenkins) is probably the reason behind recent system test failures in the "dummy-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/104835/2 For failed test results see: http://jenkins.ovirt.org/job/dummy-master_change-queue-tester/183/

1 0

[CQ]: 102615, 4 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 102615,4 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 104699,3 (ovirt-system-tests) 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 104699,3 (ovirt-system-tests) 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/102615/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104699/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17170/

1 0

[CQ]: 104768, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104768,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104768/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17165/

1 0

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

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104335,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (ovirt-engine) 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 103437,35 (ovirt-engine) 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/104335/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17162/

1 0

[CQ]: 104221, 9 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-4.3" change queue including change 104221,9 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 104699,3 (ovirt-system-tests) 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 104699,3 (ovirt-system-tests) 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/104221/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104699/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2522/

1 0

[CQ]: 104699, 3 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 20 Nov '19

20 Nov '19

Change 104699,3 (ovirt-system-tests) 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/104699/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17158/

1 0

[CQ]: 104795, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104795,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104795/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17154/

1 0

[JIRA] (OVIRT-2839) CI jobs failing global_setup - docker service fails.
by Barak Korren (oVirt JIRA) 20 Nov '19

20 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2839?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2839: ----------------------------------- Assignee: Barak Korren (was: infra) > CI jobs failing global_setup - docker service fails. > ---------------------------------------------------- > > Key: OVIRT-2839 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2839 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Bell Levin > Assignee: Barak Korren > > Hey, > I have had a few consecutive jobs failing on global_setup. > Here are a few jobs that failed on global_setup: > https://jenkins.ovirt.org/job/standard-manual-runner/885 > https://jenkins.ovirt.org/job/standard-manual-runner/884 > https://jenkins.ovirt.org/job/standard-manual-runner/883 > https://jenkins.ovirt.org/job/standard-manual-runner/882 > https://jenkins.ovirt.org/job/standard-manual-runner/879 > https://jenkins.ovirt.org/job/standard-manual-runner/878 > Here are a few jobs that succeeded: > https://jenkins.ovirt.org/job/standard-manual-runner/881 > https://jenkins.ovirt.org/job/standard-manual-runner/880 > https://jenkins.ovirt.org/job/standard-manual-runner/877 > this is currently blocking me as I am trying to push a new job to run the > network functional tests in a container. > Please let me know if you need any additional information. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 7ec39a9 (ovirt-ansible-manageiq) failed "ovirt-4.3" system tests
by oVirt Jenkins 20 Nov '19

20 Nov '19

Change 7ec39a9 (ovirt-ansible-manageiq) 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://github.com/oVirt/ovirt-ansible-manageiq/commit/7ec39a99a2a8fb006e03… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2520/

1 0

[CQ]: 104796, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104796,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104796/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17150/

1 0

[JIRA] (OVIRT-2839) CI jobs failing global_setup - docker service fails.
by Bell Levin (oVirt JIRA) 20 Nov '19

20 Nov '19

Bell Levin created OVIRT-2839: --------------------------------- Summary: CI jobs failing global_setup - docker service fails. Key: OVIRT-2839 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2839 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Bell Levin Assignee: infra Hey, I have had a few consecutive jobs failing on global_setup. Here are a few jobs that failed on global_setup: https://jenkins.ovirt.org/job/standard-manual-runner/885 https://jenkins.ovirt.org/job/standard-manual-runner/884 https://jenkins.ovirt.org/job/standard-manual-runner/883 https://jenkins.ovirt.org/job/standard-manual-runner/882 https://jenkins.ovirt.org/job/standard-manual-runner/879 https://jenkins.ovirt.org/job/standard-manual-runner/878 Here are a few jobs that succeeded: https://jenkins.ovirt.org/job/standard-manual-runner/881 https://jenkins.ovirt.org/job/standard-manual-runner/880 https://jenkins.ovirt.org/job/standard-manual-runner/877 this is currently blocking me as I am trying to push a new job to run the network functional tests in a container. Please let me know if you need any additional information. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2838) Fwd: manual system test runner broken
by Sandro Bonazzola (oVirt JIRA) 20 Nov '19

20 Nov '19

Sandro Bonazzola created OVIRT-2838: --------------------------------------- Summary: Fwd: manual system test runner broken Key: OVIRT-2838 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2838 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Sandro Bonazzola Assignee: infra Opening a ticket ---------- Forwarded message --------- Da: Barak Korren <bkorren(a)redhat.com> Date: mar 19 nov 2019 alle ore 11:36 Subject: Re: manual system test runner broken To: Sandro Bonazzola <sbonazzo(a)redhat.com> Cc: oVirt development list <devel(a)ovirt.org>, infra <infra(a)ovirt.org> On Tue, 19 Nov 2019 at 12:31, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > Il giorno mar 19 nov 2019 alle ore 11:02 Barak Korren <bkorren(a)redhat.com> > ha scritto: > >> The fallback is defined in the reposync file of the suit - the option in >> the job that talks about this does nothing AFAIK. If the non-default value >> is selected it tries to add the non existent `experimental` repo to >> extra_sources. We should probably just drop that option from the Job GUI. >> > > > So we need a way to rewrite the fallback in the reposync from the manual > runner job or it won't really be that useful. > Open a ticket... I can't think of a way to do this that will not be very fragile though, maybe it's best if it would just be passed as an env var to the suit and have it decide what and how to do it. > > >> >> On Tue, 19 Nov 2019 at 11:49, Sandro Bonazzola <sbonazzo(a)redhat.com> >> wrote: >> >>> Hi, >>> just executed basic suite for testing 4.3.7 rc4 and instead of falling >>> back on latest released it was falling back on latest tested which is newer >>> than 4.3.7 rc4 so made the test useless. >>> Job execution is here: >>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6071/ >>> who's maintaining manual ost runner? I have the feeling it's not a suite >>> bug, but a job bug. >>> >>> -- >>> >>> Sandro Bonazzola >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> >>> sbonazzo(a)redhat.com >>> <https://www.redhat.com/>*Red Hat respects your work life balance. >>> Therefore there is no need to answer this email out of your office hours.* >>> _______________________________________________ >>> Infra mailing list -- infra(a)ovirt.org >>> To unsubscribe send an email to infra-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/4EBDHNB24R7GT… >>> >> >> >> -- >> Barak Korren >> RHV DevOps team , RHCE, RHCi >> Red Hat EMEA >> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted >> > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours. > <https://mojo.redhat.com/docs/DOC-1199578>* > -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 102615, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-4.3" change queue including change 102615,4 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 104699,3 (ovirt-system-tests) 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 104699,3 (ovirt-system-tests) 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/102615/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104699/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2518/

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-master - Build #32 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Nov '19

20 Nov '19

Build: http://jenkins.ovirt.org/job/deploy-to-gated-ovirt-master/32/ Build Name: #32 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

[CQ]: 104195, 22 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104195,22 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (ovirt-engine) 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 103437,35 (ovirt-engine) 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/104195/22 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17145/

1 0

upgrade-suite in manual system test is broken
by Sandro Bonazzola 20 Nov '19

20 Nov '19

Hi Just executed manual system test on https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6072/ for testing upgrade from latest released to 4.3.7 rc4 and instead of using latest released it used latest rpms passing CI so the test was not useful at all. Who's maintaining the upgrade suite? -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1

[CQ]: 104751, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104751,6 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104751/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17140/

1 0

[CQ]: 104746, 10 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '19

20 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104746,10 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104746/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17137/

1 0

[CQ]: 104436, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104436,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (ovirt-engine) 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 103437,35 (ovirt-engine) 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/104436/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17133/

1 0

[CQ]: 104750, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104750,6 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104750/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17129/

1 0

[CQ]: 104427, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104427,17 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104427/17 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17125/

1 0

[CQ]: 104291, 7 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 19 Nov '19

19 Nov '19

Change 104291,7 (ovirt-provider-ovn) 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/104291/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17120/

1 0

[CQ]: 104767,4 (ovirt-dwh) failed "ovirt-master" system tests
by oVirt Jenkins 19 Nov '19

19 Nov '19

Change 104767,4 (ovirt-dwh) 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/104767/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17115/

1 0

oVirt infra daily report - unstable production jobs - 1014
by jenkins＠jenkins.phx.ovirt.org 19 Nov '19

19 Nov '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/1014//artifact/exported-… Cheers, Jenkins

1 0

[CQ]: 103437,35 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 19 Nov '19

19 Nov '19

Change 103437,35 (ovirt-engine) 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/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17110/

1 0

[CQ]: 104546, 2 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 19 Nov '19

19 Nov '19

Change 104546,2 (ovirt-engine-api-model) 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/104546/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17105/

1 0

[CQ]: 104688, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104688,8 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104688/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17100/

1 0

[CQ]: 104699,3 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 19 Nov '19

19 Nov '19

Change 104699,3 (ovirt-system-tests) 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/104699/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2514/

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #35 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 19 Nov '19

19 Nov '19

Build: http://jenkins.ovirt.org/job/deploy-to-gated-ovirt-4.3/35/ Build Name: #35 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

[CQ]: 104733, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104733,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104733/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17095/

1 0

[CQ]: 104732, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104732,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104732/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17090/

1 0

[CQ]: 104703, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104703,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104703/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17085/

1 0

[JIRA] (OVIRT-2827) Building vdsm with standard-manual-runner fails to clone the repo
by Anton Marchukov (oVirt JIRA) 19 Nov '19

19 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2827?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2827: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Building vdsm with standard-manual-runner fails to clone the repo > ----------------------------------------------------------------- > > Key: OVIRT-2827 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2827 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > Building vdsm using standard-manual-runner fails now with: > ERROR: Error cloning remote repo 'origin' > hudson.plugins.git.GitException: Command "git fetch --tags --progress > https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/*" > returned status code 128: > stdout: > stderr: error: RPC failed; result=22, HTTP code = 503 > fatal: The remote end hung up unexpectedly > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Can someone look into this? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2828) Re: [ovirt-devel] Re: Check patch failure in vdsm
by Anton Marchukov (oVirt JIRA) 19 Nov '19

19 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2828?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2828: -------------------------------------- Assignee: Nir Soffer (was: infra) > Re: [ovirt-devel] Re: Check patch failure in vdsm > ------------------------------------------------- > > Key: OVIRT-2828 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2828 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Nir Soffer > > On Tue, Nov 12, 2019 at 5:34 PM Miguel Duarte de Mora Barroso > <mdbarroso(a)redhat.com> wrote: > > > > On Mon, Nov 11, 2019 at 11:12 AM Eyal Shenitzky <eshenitz(a)redhat.com> wrote: > > > > > > Hi, > > > > > > I encounter the following error for py36 test in vdsm check patch: > > > > > > ... > > > ... > > > 14:03:37 File "/usr/local/lib/python3.7/site-packages/pluggy/callers.py", line 187, in _multicall > > > 14:03:37 res = hook_impl.function(*args) > > > 14:03:37 File "/usr/local/lib/python3.7/site-packages/pluggy/manager.py", line 86, in <lambda> > > > 14:03:37 firstresult=hook.spec.opts.get("firstresult") if hook.spec else False, > > > 14:03:37 File "/usr/local/lib/python3.7/site-packages/pluggy/manager.py", line 92, in _hookexec > > > 14:03:37 return self._inner_hookexec(hook, methods, kwargs) > > > 14:03:37 File "/usr/local/lib/python3.7/site-packages/pluggy/hooks.py", line 286, in __call__ > > > 14:03:37 return self._hookexec(self, self.get_hookimpls(), kwargs) > > > 14:03:37 File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py37/lib/python3.7/site-packages/_pytest/config/__init__.py", line 82, in main > > > 14:03:37 return config.hook.pytest_cmdline_main(config=config) > > > 14:03:37 File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py37/bin/pytest", line 8, in <module> > > > 14:03:37 sys.exit(main()) > > > 14:03:37 [Inferior 1 (process 22145) detached] > > > 14:03:37 ============================================================= > > > 14:03:37 = Terminating watched process = > > > 14:03:37 ============================================================= > > > 14:03:37 PROFILE {"command": ["python", "py-watch", "600", "pytest", "-m", "not (slow or stress)", "--durations=10", "--cov=vdsm.storage", "--cov-report=html:htmlcov-storage-py37", "--cov-fail-under=62", "storage"], "cpu": 39.921942808919184, "elapsed": 604.4699757099152, "idrss": 0, "inblock": 1693453, "isrss": 0, "ixrss": 0, "majflt": 2, "maxrss": 331172, "minflt": 5606489, "msgrcv": 0, "msgsnd": 0, "name": "storage-py37", "nivcsw": 139819, "nsignals": 0, "nswap": 0, "nvcsw": 187576, "oublock": 2495645, "start": 1573386812.7961884, "status": 143, "stime": 118.260961, "utime": 123.055197} > > > 14:03:37 ERROR: InvocationError for command /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py37/bin/python profile storage-py37 python py-watch 600 pytest -m 'not (slow or stress)' --durations=10 --cov=vdsm.storage --cov-report=html:htmlcov-storage-py37 --cov-fail-under=62 storage (exited with code 143) > > > > > > > > > Is there any known issue? > > > > Anyone able to pitch in ? I think something similar is happening in > > [0], also on check-patch [1]. > > > > [0] - https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > Yes it looks the same issue. > > [1] - https://gerrit.ovirt.org/#/c/104274/ > Jenkins slaves are very slow recently. I suspect we run too many jobs > concurrently or using > too many virtual cpus. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2836) nlevy@redhat.com is listed twice in gerrit and can't be selected as reviewer
by Anton Marchukov (oVirt JIRA) 19 Nov '19

19 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2836?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2836: -------------------------------------- Assignee: Shlomi Zidmi (was: infra) > nlevy(a)redhat.com is listed twice in gerrit and can't be selected as reviewer > ---------------------------------------------------------------------------- > > Key: OVIRT-2836 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2836 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: Shlomi Zidmi > > nlevy(a)redhat.com is listed twice in gerrit and can't be selected as reviewer > infra team, can you please fix? > Thanks, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2837) OST fails for collecting artifacts
by Anton Marchukov (oVirt JIRA) 19 Nov '19

19 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2837?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2837: -------------------------------------- Assignee: Marcin Sobczyk (was: infra) > OST fails for collecting artifacts > ---------------------------------- > > Key: OVIRT-2837 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2837 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Amit Bawer > Assignee: Marcin Sobczyk > > Happens for several runs, full log can be seen at > http://jenkins.ovirt.org/job/ovirt-system-tests_manual/6057/artifact/export… > 2019-11-18 12:28:12,710::log_utils.py::end_log_task::670::root::ERROR:: > - [Thread-42] lago-basic-suite-master-engine: [31mERROR [0m (in > 0:00:08) > 2019-11-18 12:28:12,731::log_utils.py::__exit__::607::lago.prefix::DEBUG:: > File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1526, in > _collect_artifacts > vm.collect_artifacts(path, ignore_nopath) > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 748, in collect_artifacts > ignore_nopath=ignore_nopath > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 468, in extract_paths > return self.provider.extract_paths(paths, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/lago/providers/libvirt/vm.py", > line 398, in extract_paths > ignore_nopath=ignore_nopath, > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 253, in extract_paths > self._extract_paths_tar_gz(paths, ignore_nopath) > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 102, in wrapper > return func(self, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 341, in _extract_paths_tar_gz > raise ExtractPathNoPathError(remote_path) > 2019-11-18 12:28:12,731::utils.py::_ret_via_queue::63::lago.utils::DEBUG::Error > while running thread Thread-42 > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in > _ret_via_queue > queue.put({'return': func()}) > File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1526, > in _collect_artifacts > vm.collect_artifacts(path, ignore_nopath) > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 748, in collect_artifacts > ignore_nopath=ignore_nopath > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 468, in extract_paths > return self.provider.extract_paths(paths, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/lago/providers/libvirt/vm.py", > line 398, in extract_paths > ignore_nopath=ignore_nopath, > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 253, in extract_paths > self._extract_paths_tar_gz(paths, ignore_nopath) > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 102, in wrapper > return func(self, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line > 341, in _extract_paths_tar_gz > raise ExtractPathNoPathError(remote_path) > ExtractPathNoPathError: Failed to extract files: /tmp/otopi* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 104520, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104520,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104520/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17080/

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_gate
by jenkins＠jenkins.phx.ovirt.org 19 Nov '19

19 Nov '19

Failed to run project_setup.sh for: #51. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-integ-tests-container-s88hg.

1 0

manual system test runner broken
by Sandro Bonazzola 19 Nov '19

19 Nov '19

Hi, just executed basic suite for testing 4.3.7 rc4 and instead of falling back on latest released it was falling back on latest tested which is newer than 4.3.7 rc4 so made the test useless. Job execution is here: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6071/ who's maintaining manual ost runner? I have the feeling it's not a suite bug, but a job bug. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 3

[CQ]: 104729, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104729,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104729/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17076/

1 0

[CQ]: 104788, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Nov '19

19 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104788,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104788/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17072/

1 0

[CQ]: 104787, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Nov '19

18 Nov '19

A system test invoked by the "ovirt-master" change queue including change 104787,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 104274,21 (vdsm) 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 104274,21 (vdsm) 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/104787/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104274/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17068/

1 0

[CQ]: 104771,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 18 Nov '19

18 Nov '19

Change 104771,3 (ovirt-engine) 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/104771/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17064/

1 0

oVirt infra daily report - unstable production jobs - 1013
by jenkins＠jenkins.phx.ovirt.org 18 Nov '19

18 Nov '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/1013//artifact/exported-… Cheers, Jenkins

1 0