November 2018 - Infra - Ovirt List Archives

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #1503 jenkins [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 vm0041.workers-phx.ovirt.org.

6 years, 4 months

1
0
0 / 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #1503 jenkins [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 vm0203.workers-phx.ovirt.org.

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2581) ovirt-engine is failing on master due to missing packages

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2581?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2581: ----------------------------- Resolution: Fixed Status: Done (was: To Do) this issue was resolved > ovirt-engine is failing on master due to missing packages > --------------------------------------------------------- > > Key: OVIRT-2581 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2581 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_packages > > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11202/ > failure is due to missing packages: > {noformat} > 2018-11-19 13:51:51,498-0500 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:85 Yum [u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libepoxy.so.0()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libgbm.so.1()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libibumad.so.3()(64bit)'] > 2018-11-19 13:51:51,499-0500 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-I0X8XAo2i4/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-I0X8XAo2i4/otopi-plugins/otopi/packagers/yumpackager.py", line 248, in _packages > self.processTransaction() > File "/tmp/ovirt-I0X8XAo2i4/otopi-plugins/otopi/packagers/yumpackager.py", line 262, in processTransaction > if self._miniyum.buildTransaction(): > File "/tmp/ovirt-I0X8XAo2i4/pythonlib/otopi/miniyum.py", line 920, in buildTransaction > raise yum.Errors.YumBaseError(msg) > YumBaseError: [u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libepoxy.so.0()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libgbm.so.1()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libibumad.so.3()(64bit)'] > 2018-11-19 13:51:51,500-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Package installation': [u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libepoxy.so.0()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libgbm.so.1()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libibumad.so.3()(64bit)'] > 2018-11-19 13:51:51,519-0500 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: > id uid local foreign state pid exe > {noformat} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[CQ]: 95463, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 95463,5 (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/95463/5 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/11696/

6 years, 4 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 376 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/376/ Build Number: 376 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #376 [Gal Ben Haim] oc-on-ovirt: Update Orb version to 4.2.7 ----------------- Failed Tests: ----------------- No tests ran.

6 years, 4 months

1
8
0 / 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2594: ---------------------------------- Nothing on those slaves desc indicated they have an issue, so I'm not sure that was the reason they were taken offline. In any case if they are not OK, they should be reinstalled as centos 7. [~ederevea] can you reinstall all the fc27 slaves as centos7? Probably best to bring them down now ( I would but I don't have access to jenkins for some reason, I can't login ) > 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/co... > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/co... > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/co... > 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)

6 years, 4 months

1
0
0 / 0

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 - Build # 130 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-f... Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-f... Build Number: 130 Build Status: Failure Triggered By: Started by user Sandro Bonazzola ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran.

6 years, 4 months

1
1
0 / 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2594: ------------------------------------- This looks like a very old known issue - this happens when someone sets up a slave when the {{jenkins}} UID/GID are 1000. [~eedri], [~ena(a)redhat.com] - this seems to be all happenning on the fc27 slaves you brought up, I guess now we know why they were down in the 1st place... [~nsoffer(a)redhat.com] WRT your 2nd issue - we actually have fixes for that where possible - but not in STDCI V1... The code structure of STDCI V1 makes this close to impossible to do there... But for this particular issue, its not really possible to tell the difference because the failure is occurring in the innermost {{mock}} invocation that is launching your script... > 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/co... > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/co... > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/co... > 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)

6 years, 4 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 376 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/376/ Build Number: 376 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #376 [Gal Ben Haim] oc-on-ovirt: Update Orb version to 4.2.7 ----------------- Failed Tests: ----------------- No tests ran.

6 years, 4 months

1
8
0 / 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2556: ------------------------------------- We need to fix this, or at least come up with some idea as to why is this happening, because like I said, it does not make sense. Also if 1/9 tests fails because of this, you would now rerun all 9 hereby wasting quite a bit of resources.... At the very least I think we may want to add some canary script before your tests start to fail on this and properly flag this as a system error rather then a test failure. [~dbelenky(a)redhat.com] FYI, any idea why we're seeing this again now? > 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//a... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2018