- Infra - oVirt List Archives

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Barak Korren (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Barak Korren reopened OVIRT-2556: --------------------------------- > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Roman Mohr > Assignee: infra > Priority: High > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Barak Korren (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2556: -------------------------------- Issue Type: Bug (was: By-EMAIL) Priority: High (was: Medium) > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Roman Mohr > Assignee: infra > Priority: High > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Barak Korren (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2556: ------------------------------------- Re-openning This doesn't really make sense - we now bring up a fresh docker instance each run... Maybe its some sort of a race condition with Docker not starting up fast enough.... We do have a script that checks it before starting the test so we aught to catch that too. > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #1944
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ 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-centos-kvm-common-el7-x86_…> > 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 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision b75848a829f6096faa2982c7f1f65a28970d2a8b (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f b75848a829f6096faa2982c7f1f65a28970d2a8b Commit message: "container: shutdown if jnlp agent failed 3 times" > git rev-list --no-walk b75848a829f6096faa2982c7f1f65a28970d2a8b # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins4350288772434599557.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-kvm-common-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 95613, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '18

27 Nov '18

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

1 0

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

27 Nov '18

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

1 0

[CQ]: 95383, 2 (ovirt-lldp-labeler) failed "ovirt-master" system tests
by oVirt Jenkins 27 Nov '18

27 Nov '18

Change 95383,2 (ovirt-lldp-labeler) 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/95383/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11683/

1 0

[CQ]: 95699, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '18

27 Nov '18

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

1 0

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 - Build # 126 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build Number: 126 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #126 [Yuval Turgeman] stdci: move build-artifacts to a v1 job [Marcin Sobczyk] VDSM on stdci v2 [Milan Zamazal] Drop mzamazal from basic-suite-master compatibility testing [Sandro Bonazzola] ovirt-appliance: add builds for 4.3 branch ----------------- Failed Tests: ----------------- No tests ran.

1 3

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

27 Nov '18

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

1 0

[CQ]: 95698, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-master" system tests
by oVirt Jenkins 26 Nov '18

26 Nov '18

Change 95698,1 (ovirt-engine-extension-aaa-jdbc) 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/95698/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11673/

1 0

[CQ]: 95692, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

[CQ]: 95722,1 (cockpit-ovirt) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Nov '18

26 Nov '18

Change 95722,1 (cockpit-ovirt) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/95722/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3541/

1 0

[CQ]: 95578, 5 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

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

26 Nov '18

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

1 0

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

26 Nov '18

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

1 0

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

26 Nov '18

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

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Roman Mohr (oVirt JIRA) 26 Nov '18

26 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Roman Mohr commented on OVIRT-2556: ----------------------------------- Here is another one: https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2610//art… > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Eyal Edri (oVirt JIRA) 26 Nov '18

26 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2594: ---------------------------------- [~ederevea] can you look into it? worth marking these builds as keep forever so we can debug them later. > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[oVirt Jenkins] ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 - Build # 1 - Failure!
by jenkins＠jenkins.phx.ovirt.org 26 Nov '18

26 Nov '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x… Build Number: 1 Build Status: Failure Triggered By: Started by user Sandro Bonazzola ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran.

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Roman Mohr (oVirt JIRA) 26 Nov '18

26 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Roman Mohr updated OVIRT-2556: ------------------------------ Resolution: Fixed Status: Done (was: To Do) > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Nov '18

26 Nov '18

Failed to run project_setup.sh for: #164 vdsm [check-patch]. 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 vm0010.workers-phx.ovirt.org.

1 0

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

26 Nov '18

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

1 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Nir Soffer (oVirt JIRA) 26 Nov '18

26 Nov '18

Nir Soffer created OVIRT-2594: --------------------------------- Summary: Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run Key: OVIRT-2594 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I have seen this issue in the recent days several times. Here are some examples: - https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… There are too issues: - No test ran, so we need to retrigger manually - Gerrit report build FAILURE instead of build ERROR I reported the second issue many times in the last 5 years, no progress yet. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Nir Soffer 26 Nov '18

26 Nov '18

I have seen this issue in the recent days several times. Here are some examples: - https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… There are too issues: - No test ran, so we need to retrigger manually - Gerrit report build FAILURE instead of build ERROR I reported the second issue many times in the last 5 years, no progress yet. Nir

1 0

[JIRA] (OVIRT-2589) CI random failures on VDSM check-patch
by Eyal Edri (oVirt JIRA) 26 Nov '18

26 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2589?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2589: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > CI random failures on VDSM check-patch > -------------------------------------- > > Key: OVIRT-2589 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2589 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: Evgheni Dereveanchin > > Hello, > It seems we are experiencing random failures on the CI VDSM check-patch, > Could you please have a look? > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/108/ > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26203/ > Some have errors of improper imports, as if the slave is not "clean". > Thanks, > Edy. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 95686, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

[CQ]: 95685, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

[CQ]: 95681, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

[JIRA] (OVIRT-2593) How does stdci prevent regressions and proactively monitor the cluster?
by Roman Mohr (oVirt JIRA) 26 Nov '18

26 Nov '18

Roman Mohr created OVIRT-2593: --------------------------------- Summary: How does stdci prevent regressions and proactively monitor the cluster? Key: OVIRT-2593 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2593 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roman Mohr Assignee: infra We want to go one step further with KubeVirt and sooner or later only merge when the tests are green (automatically). Therefore we want to ensure that this CI system is the right system for us and can be properly scaled, developed and operated. Apart from requirements like, automatically re-run tests and a merge-pools stability and QoS of the CI system are interesting for us. Some examples: * Sometimes jobs break with a system error shown in the logs (is that monitored and worked on?) * Sometimes things like "out-of-disk-space" show up. Is e.g. disk utilization proactively handled? * We had one issue where the docker installation was broken in a build-slot and all jobs stopped fast. As a consequence all following builds were scheduled there too. Is something like that monitored? * We repeatedly have issues, connecting to jenkins. It is extremely slow (not just Blue-Ocean-slow, really slow). Are such things monitored and alarms raised, countermeasures taken? * That did not happen for a while, but there were repeatedly bare-metal machines whithout kvm-nesting added to the cluster. Are there measures in place which prevent such regressions where the same issues happen multiple times? * How is the flexibility of the project ensured? Is it also tested and maintained in a sane fashion to allow proper evolution in time? Automated tests? Offline-testing of changes? And so on ... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2592) Allow caching directories in the datacenter
by Roman Mohr (oVirt JIRA) 26 Nov '18

26 Nov '18

Roman Mohr created OVIRT-2592: --------------------------------- Summary: Allow caching directories in the datacenter Key: OVIRT-2592 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2592 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roman Mohr Assignee: infra What? Sometimes jobs create huge artifacts or need to download a lot in order start building. For instance Maven, glide or bazel download a lot before they can build. These tools also include their own checks to ensure that the content of a cached folder is in-sync. It is helpful if people can specify directories to cache. Normally it makes sense to have options to allow a cache-per-build-branch. When a PR is merged into this branch the cache from that branch is used. There are very rare conditions where it is needed to clear such a cache. A UI-Button to do so is helpful. Just to higlight the difference to e.g. container whitelist: This is about caching in the cluster, not in a build-slot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2591) Add a distributed docker-cache
by Roman Mohr (oVirt JIRA) 26 Nov '18

26 Nov '18

Roman Mohr created OVIRT-2591: --------------------------------- Summary: Add a distributed docker-cache Key: OVIRT-2591 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2591 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roman Mohr Assignee: infra What? If CI builds get heavy and things are running inside containers, I expect that the CI system proactively tries to optimize when it can. Since the CI system provides the docker installation, I would expect that under some conditions, it automatically puts heavy docker builds in a distributed cache in the cluster. Examples on how this can achieved are listed in [1] and [2]. Why? Dockerfiles have the advantage that we can isolate our biuld-steps in a Dockerfile. This gives reproducibility, but also means that e.g. curl downloads or RPM installs are not visible for the CI system. Therefore it is beneficial for the CI system and the user (more speed and less utilization), to put docker images with their build chain into a distributed cache and pre-fetch the cache into the docker cache of the build slot. Pre-fetching based on e.g. gibhub project probably makes sense. [1] https://runnable.com/blog/distributing-docker-cache-across-hosts [2] https://blog.codeship.com/building-a-remote-caching-system/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2590) Cache Docker images in the datacenter
by Roman Mohr (oVirt JIRA) 26 Nov '18

26 Nov '18

Roman Mohr created OVIRT-2590: --------------------------------- Summary: Cache Docker images in the datacenter Key: OVIRT-2590 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2590 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roman Mohr Assignee: infra What? As a user, I expect that I don't have to care about caching to speed up builds for the good of the CI system itself. Right now there exists a whitelist for docker images, which will not be remove from the build slot after the build. Instead of that I expect a clean build environment and that in general all images which I regularly use are cached in the cluster via e.g. a pull-through-cache [1]. Why? 1) Caching in a build slot is not very effective. CI runs do really-a-lot of almost identical things in a small time-window (e.g. days). If caching happens in the build-slot and many slots are present, then the cache utilization will be very low. 2) Whitelisting docker images extra for a slot where the registry runs in, is very error prone and since it is not cached across the cluster it is also very intransparent what the clear benefit for the user is. Especially when thinking about scaling a CI system, that seems to leak internal optimizations to the user. Fast builds are twice as important for the CI system than they are for the users (by default faster and lower utilization is always better than asking people to optimize on their side). [1] https://docs.docker.com/registry/recipes/mirror/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 95383,2 (ovirt-lldp-labeler) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Nov '18

26 Nov '18

Change 95383,2 (ovirt-lldp-labeler) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/95383/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3535/

1 0

[CQ]: 95680, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-master" system tests
by oVirt Jenkins 26 Nov '18

26 Nov '18

Change 95680,1 (ovirt-engine-extension-logger-log4j) 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/95680/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11638/

1 0

[JIRA] (OVIRT-2586) Jenkins terribly slow and unresponsive
by Evgheni Dereveanchin (oVirt JIRA) 26 Nov '18

26 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2586: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Jenkins terribly slow and unresponsive > -------------------------------------- > > Key: OVIRT-2586 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > Priority: Highest > > Hi, > jenkins is terribly slow and becoming worse every day. > I tried to gain some speed by adding 4 cores to the VM through engine-phx. > It's a bit better but the real issue doesn't seem related to CPU power. > Can anybody investigate? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 95722,1 (cockpit-ovirt) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Nov '18

26 Nov '18

Change 95722,1 (cockpit-ovirt) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/95722/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3534/

1 0

Fwd: ** PROBLEM Service Alert: ovirt-mirrorchecker/mirror.slu.cz/ovirt mirror site last sync is CRITICAL **
by Emil Natan 26 Nov '18

26 Nov '18

Hello, mirror.slu.cz has not synced with our mirror master for a few days now. Can you please investigate. Thank you very much in advance. ---------- Forwarded message --------- From: <nagios(a)monitoring.ovirt.org> Date: Sun, Nov 25, 2018 at 7:34 AM Subject: ** PROBLEM Service Alert: ovirt-mirrorchecker/mirror.slu.cz/ovirt mirror site last sync is CRITICAL ** To: <ena(a)redhat.com> ***** Nagios ***** Notification Type: PROBLEM Service: mirror.slu.cz/ovirt mirror site last sync Host: ovirt-mirrorchecker Address: web-ovirt-mirrorchecker.apps.ovirt.org State: CRITICAL Date/Time: Sun Nov 25 05:33:54 UTC 2018 Additional Info: CRITICAL - 367439 seconds since last sync, which are 102.0664 hours. -- Emil Natan RHV/CNV DevOps

2 2

[JIRA] (OVIRT-2589) CI random failures on VDSM check-patch
by Edward Haas (oVirt JIRA) 26 Nov '18

26 Nov '18

Edward Haas created OVIRT-2589: ---------------------------------- Summary: CI random failures on VDSM check-patch Key: OVIRT-2589 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2589 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: infra Hello, It seems we are experiencing random failures on the CI VDSM check-patch, Could you please have a look? https://jenkins.ovirt.org/job/vdsm_standard-check-patch/108/ https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26203/ Some have errors of improper imports, as if the slave is not "clean". Thanks, Edy. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

Jenkins – Running OST Manual
by Tomasz Barański 26 Nov '18

26 Nov '18

Hello, I'm trying to diagnose a failing build and need to run manually run the OST. I'm logged in to Jenkins, but I don't seem to have the right credentials to start a build at https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ My account: tbaransk, with my @redhat mail address. Please help. Tomo

3 3

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #46
by jenkins＠jenkins.phx.ovirt.org 26 Nov '18

26 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/46…> ------------------------------------------ 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/> > 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 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision fde1163547fa2d61d7ec308d07cee3b52bb2623e (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f fde1163547fa2d61d7ec308d07cee3b52bb2623e Commit message: "cancel build when GH PR is updated" > git rev-list --no-walk fde1163547fa2d61d7ec308d07cee3b52bb2623e # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins5579623578094511566.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/fedora-base-fc29 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/fedora-base-fc29' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 95383, 2 (ovirt-lldp-labeler) failed "ovirt-master" system tests
by oVirt Jenkins 26 Nov '18

26 Nov '18

Change 95383,2 (ovirt-lldp-labeler) 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/95383/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11633/

1 0

[CQ]: 95677, 1 (ovirt-wgt) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

[CQ]: 95676, 1 (ovirt-wgt) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

[CQ]: 95675,1 (ovirt-wgt) failed "ovirt-master" system tests
by oVirt Jenkins 26 Nov '18

26 Nov '18

Change 95675,1 (ovirt-wgt) 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/95675/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11618/

1 0

[CQ]: 95674, 1 (ovirt-engine-extension-aaa-misc) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

[CQ]: 95673, 1 (ovirt-engine-extension-aaa-misc) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

[CQ]: 95036, 3 (ovirt-engine-extension-aaa-misc) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Nov '18

26 Nov '18

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

1 0

[CQ]: 95672,2 (engine-db-query) failed "ovirt-master" system tests
by oVirt Jenkins 26 Nov '18

26 Nov '18

Change 95672,2 (engine-db-query) 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/95672/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11598/

1 0

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

26 Nov '18

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

1 0