October 2019 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2811) s390x tests failing on missing tty

by Sandro Bonazzola (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jir... ] Sandro Bonazzola updated OVIRT-2811: ------------------------------------ Flagged: Impediment > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standa... > -- > 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.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

4 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty

by Sandro Bonazzola (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jir... ] Sandro Bonazzola updated OVIRT-2811: ------------------------------------ Priority: High (was: Medium) > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standa... > -- > 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.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

4 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty

by Sandro Bonazzola (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jir... ] Sandro Bonazzola commented on OVIRT-2811: ----------------------------------------- Il giorno lun 7 ott 2019 alle ore 14:56 Eyal Edri <eedri(a)redhat.com> ha scritto: > I don't think you need use sudo, since you're already root on the mock. > Did you try running without sudo? > I'm not using sudo in check patch script, it's used by CI underlying scripts. > > If you want to use sudo, you'll need to edit the /etc/suders files before > and enable tty. > > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standa... > -- > 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.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

4 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty

by Sandro Bonazzola (oVirt JIRA)

Sandro Bonazzola created OVIRT-2811: --------------------------------------- Summary: s390x tests failing on missing tty Key: OVIRT-2811 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Sandro Bonazzola Assignee: infra Jenkins is failing on s390x with: [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standa... -- 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.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

4 years, 7 months

3
2
0 / 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2811: ---------------------------------- I don't think you need use sudo, since you're already root on the mock. Did you try running without sudo? If you want to use sudo, you'll need to edit the /etc/suders files before and enable tty. > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standa... > -- > 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.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

4 years, 7 months

1
0
0 / 0

[CQ]: 103894, 3 (ovirt-engine) 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 103894,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 102934,5 (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 102934,5 (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/103894/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102934/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16344/

4 years, 7 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 215 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/215/ Build Number: 215 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #215 [jenkins CI] Auto create ovirt-master ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.ha_recovery_43 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:307b58b9-0d1c-4736-bfab-1425a88c82e3:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:307b58b9-0d1c-4736-bfab-1425a88c82e3:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running f2025ba8 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2 lago.ssh: DEBUG: Command f2025ba8 on lago-compat-4-3-suite-master-host-0 returned with 0 lago.ssh: DEBUG: Command f2025ba8 on lago-compat-4-3-suite-master-host-0 output: 12277 lago.ssh: DEBUG: start task:db14e219-7ae5-4dc4-95d1-0d4097ed440f:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:db14e219-7ae5-4dc4-95d1-0d4097ed440f:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running f3098e9a on lago-compat-4-3-suite-master-host-0: kill -KILL 12277 lago.ssh: DEBUG: Command f3098e9a on lago-compat-4-3-suite-master-host-0 returned with 0 --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/004_basic_sanity.py", line 725, in ha_recovery lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) 'False != True after 600 seconds\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:307b58b9-0d1c-4736-bfab-1425a88c82e3:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:307b58b9-0d1c-4736-bfab-1425a88c82e3:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running f2025ba8 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2\nlago.ssh: DEBUG: Command f2025ba8 on lago-compat-4-3-suite-master-host-0 returned with 0\nlago.ssh: DEBUG: Command f2025ba8 on lago-compat-4-3-suite-master-host-0 output:\n 12277\n\nlago.ssh: DEBUG: start task:db14e219-7ae5-4dc4-95d1-0d4097ed440f:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:db14e219-7ae5-4dc4-95d1-0d4097ed440f:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running f3098e9a on lago-compat-4-3-suite-master-host-0: kill -KILL 12277\n\nlago.ssh: DEBUG: Command f3098e9a on lago-compat-4-3-suite-master-host-0 returned with 0\n--------------------- >> end captured logging << ---------------------'

4 years, 7 months

1
1
0 / 0

[CQ]: 103906,1 (jenkins) failed "dummy-master" system tests

by oVirt Jenkins

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

4 years, 7 months

1
0
0 / 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #50 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

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

4 years, 7 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 970

by jenkins＠jenkins.phx.ovirt.org

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/970//artifact/exported... Cheers, Jenkins

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra October 2019