- Infra - oVirt List Archives

[JIRA] (OVIRT-2491) upgrade jenkins.ovirt.org to 2.138.1 LTS
by Evgheni Dereveanchin (oVirt JIRA) 13 Sep '18

13 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2491?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2491: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > upgrade jenkins.ovirt.org to 2.138.1 LTS > ---------------------------------------- > > Key: OVIRT-2491 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2491 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Jenkins 2.138.1 LTS is out, our instance needs to be updated. > https://jenkins.io/changelog-stable/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2491) upgrade jenkins.ovirt.org to 2.138.1 LTS
by Evgheni Dereveanchin (oVirt JIRA) 13 Sep '18

13 Sep '18

Evgheni Dereveanchin created OVIRT-2491: ------------------------------------------- Summary: upgrade jenkins.ovirt.org to 2.138.1 LTS Key: OVIRT-2491 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2491 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Jenkins 2.138.1 LTS is out, our instance needs to be updated. https://jenkins.io/changelog-stable/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2490) Add support for tag-stage
by Daniel Belenky (oVirt JIRA) 13 Sep '18

13 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2490?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2490: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Add support for tag-stage > ------------------------- > > Key: OVIRT-2490 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2490 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: Daniel Belenky > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2490) Add support for tag-stage
by Daniel Belenky (oVirt JIRA) 13 Sep '18

13 Sep '18

Daniel Belenky created OVIRT-2490: ------------------------------------- Summary: Add support for tag-stage Key: OVIRT-2490 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2490 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

Change in stdci-staging[master]: Check timeout functionality
by review＠gerrit-staging.phx.ovirt.org 13 Sep '18

13 Sep '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/213 ) Change subject: Check timeout functionality ...................................................................... Check timeout functionality Change-Id: I8264e2efd72cf4c969dd9d2a149a3fbd45f6feb7 Signed-off-by: Daniel Belenky <dbelenky(a)redhat.com> --- A automation/check-patch.do-not-timeout.sh A automation/check-patch.do-timeout.sh M stdci.yaml 3 files changed, 19 insertions(+), 3 deletions(-) Approvals: Daniel Belenky: Looks good to me, approved; Verified; Passed CI tests Objections: Jenkins CI: Failed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/213 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: merged Gerrit-Change-Id: I8264e2efd72cf4c969dd9d2a149a3fbd45f6feb7 Gerrit-Change-Number: 213 Gerrit-PatchSet: 2 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in stdci-staging[master]: Check timeout functionality
by review＠gerrit-staging.phx.ovirt.org 13 Sep '18

13 Sep '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/213 ) Change subject: Check timeout functionality ...................................................................... Patch Set 2: Verified+1 Code-Review+2 Continuous-Integration+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/213 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I8264e2efd72cf4c969dd9d2a149a3fbd45f6feb7 Gerrit-Change-Number: 213 Gerrit-PatchSet: 2 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Thu, 13 Sep 2018 08:05:55 +0000 Gerrit-HasComments: No

1 0

[CQ]: 94299, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Sep '18

13 Sep '18

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

1 0

[CQ]: 94240, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Sep '18

13 Sep '18

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

1 0

[CQ]: 93776, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Sep '18

13 Sep '18

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

1 0

[CQ]: 94298, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Sep '18

13 Sep '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 604 - Failure!
by jenkins＠jenkins.phx.ovirt.org 13 Sep '18

13 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build Number: 604 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #604 [Gal Ben Haim] Adding dr suite [Barak Korren] Remove the populate_mock function from mock_runner [Daniel Belenky] mock_runner: store shell cmd in a variable [Barak Korren] mock_runner: Added timeout param [Barak Korren] Make whitelist repo configurable via env vars [Daniel Belenky] stdci_runner: let mock_runner manage timeout [Greg Sheremeta] remove 4.1 change queue from ovirt-engine-nodejs config ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 012_local_maintenance_sdk.local_maintenance Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- root: INFO: * Waiting For System Stability... root: INFO: * Performing Deactivation... --------------------- >> 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs 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_he-basic-ansible-suite-master/ovirt-system-tests/he-basic-ansible-suite-master/test-scenarios/012_local_maintenance_sdk.py", line 65, in local_maintenance lambda: host_service.get().status == types.HostStatus.MAINTENANCE or 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 << --------------------\nroot: INFO: * Waiting For System Stability...\nroot: INFO: * Performing Deactivation...\n--------------------- >> end captured logging << ---------------------'

2 22

oVirt infra daily report - unstable production jobs - 581
by jenkins＠jenkins.phx.ovirt.org 13 Sep '18

13 Sep '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/581//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 94071, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Sep '18

12 Sep '18

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

1 0

[CQ]: 94219, 21 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Sep '18

12 Sep '18

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

1 0

[JIRA] (OVIRT-2489) Add nmstate project to STDCI
by Edward Haas (oVirt JIRA) 12 Sep '18

12 Sep '18

Edward Haas created OVIRT-2489: ---------------------------------- Summary: Add nmstate project to STDCI Key: OVIRT-2489 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2489 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: infra Hello, nmstate is a new project that is aimed to replace most of the VDSM networking implementation and hopefully used to manage k8s nodes networking. It has raised from a joint effort between the NetworkManager team and oVirt networking team. We would like to utilize STDCI to run integration tests. A PR has been opened for this: https://github.com/nmstate/nmstate/pull/76 Could you please help us add it to the CI? Thanks, Edy. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[CQ]: 93775,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 Sep '18

12 Sep '18

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

1 0

[JIRA] (OVIRT-2488) mirrors.phx running out of disk space
by Ehud Yonasi (oVirt JIRA) 12 Sep '18

12 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2488?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2488: ------------------------------------ Yea. i understand there is no retention policy in place. Let's discuss about how far we want to keep backwards because as i see your growth report it's like 10 gigs weekly.. > mirrors.phx running out of disk space > ------------------------------------- > > Key: OVIRT-2488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2488 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > mirrors.phx.ovirt.org is slowly running out of space. We should document the cleanup procedure so opening a tracker ticket. > Free disk space has dropped from 10% (61GB free) to 8.5% (52GB free) within the last week so we still have time to react. We can also modify alert thresholds or disable alerts if they're causing too much noise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2488) mirrors.phx running out of disk space
by Evgheni Dereveanchin (oVirt JIRA) 12 Sep '18

12 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2488?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2488: --------------------------------------------- AFAIR there is no retention here as well. The disk filled up several times before and [~bkorren(a)redhat.com] performed manual cleanups. Now we have monitoring in place to know this in advance before mirros sync jobs start failing and also we can see the trend from the graphs. > mirrors.phx running out of disk space > ------------------------------------- > > Key: OVIRT-2488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2488 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > mirrors.phx.ovirt.org is slowly running out of space. We should document the cleanup procedure so opening a tracker ticket. > Free disk space has dropped from 10% (61GB free) to 8.5% (52GB free) within the last week so we still have time to react. We can also modify alert thresholds or disable alerts if they're causing too much noise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[CQ]: 94204, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Sep '18

12 Sep '18

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

2 1

[CQ]: 94271, 1 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Sep '18

12 Sep '18

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

1 0

[JIRA] (OVIRT-2488) mirrors.phx running out of disk space
by Ehud Yonasi (oVirt JIRA) 12 Sep '18

12 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2488?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2488: ------------------------------------ 1st question is, how far do we keep outdated fedora rpms atm? because AFAIK we keep the supported distro. if we keep it based on daily snapshot, i can manage to create a cleanup script with a pre-defined policy. > mirrors.phx running out of disk space > ------------------------------------- > > Key: OVIRT-2488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2488 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > mirrors.phx.ovirt.org is slowly running out of space. We should document the cleanup procedure so opening a tracker ticket. > Free disk space has dropped from 10% (61GB free) to 8.5% (52GB free) within the last week so we still have time to react. We can also modify alert thresholds or disable alerts if they're causing too much noise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2488) mirrors.phx running out of disk space
by Evgheni Dereveanchin (oVirt JIRA) 12 Sep '18

12 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2488?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2488: --------------------------------------------- For reference, the FS is 600GB in size. We can grow it but likely most disk space is taken up by outdated fedora RPMs. > mirrors.phx running out of disk space > ------------------------------------- > > Key: OVIRT-2488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2488 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > mirrors.phx.ovirt.org is slowly running out of space. We should document the cleanup procedure so opening a tracker ticket. > Free disk space has dropped from 10% (61GB free) to 8.5% (52GB free) within the last week so we still have time to react. We can also modify alert thresholds or disable alerts if they're causing too much noise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2488) mirrors.phx running out of disk space
by Evgheni Dereveanchin (oVirt JIRA) 12 Sep '18

12 Sep '18

Evgheni Dereveanchin created OVIRT-2488: ------------------------------------------- Summary: mirrors.phx running out of disk space Key: OVIRT-2488 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2488 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra mirrors.phx.ovirt.org is slowly running out of space. We should document the cleanup procedure so opening a tracker ticket. Free disk space has dropped from 10% (61GB free) to 8.5% (52GB free) within the last week so we still have time to react. We can also modify alert thresholds or disable alerts if they're causing too much noise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[CQ]: 53950c3 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Sep '18

12 Sep '18

A system test invoked by the "ovirt-master" change queue including change 53950c3 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 9984774 (ovirt-ansible- hosted-engine-setup) 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 9984774 (ovirt-ansible-hosted- engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/53950c39f… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/998477419… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10233/

1 0

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

12 Sep '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 155 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Sep '18

12 Sep '18

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/155/ Build Number: 155 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #155 [Miguel Duarte Barroso] Repos: add python2-ovsdbapp to the reposync config ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.verify_suspend_resume_vm0_42 Error Message: 0 != 1 -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:e7c63432-40ff-4de9-8756-d51ce70025fe:Get ssh client for lago-compat-4-2-suite-master-host-1: lago.ssh: DEBUG: end task:e7c63432-40ff-4de9-8756-d51ce70025fe:Get ssh client for lago-compat-4-2-suite-master-host-1: lago.ssh: DEBUG: Running fcfd4cbe on lago-compat-4-2-suite-master-host-1: awk 'BEGIN { n = 0; } $1 + " " + $2 > "IOError: [Errno" && $0 ~ /START create\(.*memoryDumpVolume/ { n = n + 1; } END { print n; }' /var/log/vdsm/vdsm.log lago.ssh: DEBUG: Command fcfd4cbe on lago-compat-4-2-suite-master-host-1 returned with 0 lago.ssh: DEBUG: Command fcfd4cbe on lago-compat-4-2-suite-master-host-1 output: 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.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/004_basic_sanity.py", line 1140, in verify_suspend_resume_vm0 nt.assert_equals(log_line_count('START create\(.*' + identifier), 1) File "/usr/lib64/python2.7/unittest/case.py", line 553, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib64/python2.7/unittest/case.py", line 546, in _baseAssertEqual raise self.failureException(msg) '0 != 1\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:e7c63432-40ff-4de9-8756-d51ce70025fe:Get ssh client for lago-compat-4-2-suite-master-host-1:\nlago.ssh: DEBUG: end task:e7c63432-40ff-4de9-8756-d51ce70025fe:Get ssh client for lago-compat-4-2-suite-master-host-1:\nlago.ssh: DEBUG: Running fcfd4cbe on lago-compat-4-2-suite-master-host-1: awk \'BEGIN { n = 0; } $1 + " " + $2 > "IOError: [Errno" && $0 ~ /START create\\(.*memoryDumpVolume/ { n = n + 1; } END { print n; }\' /var/log/vdsm/vdsm.log\nlago.ssh: DEBUG: Command fcfd4cbe on lago-compat-4-2-suite-master-host-1 returned with 0\nlago.ssh: DEBUG: Command fcfd4cbe on lago-compat-4-2-suite-master-host-1 output:\n 0\n\n--------------------- >> end captured logging << ---------------------'

1 1

oVirt infra daily report - unstable production jobs - 580
by jenkins＠jenkins.phx.ovirt.org 12 Sep '18

12 Sep '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/580//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 94285, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Sep '18

11 Sep '18

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

1 0

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

11 Sep '18

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

1 0

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

11 Sep '18

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

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-ansible-manageiq) ] [ 11-09-2018 ] [ metrics_bootstrap.metrics_and_log_collector ]
by Dafna Ron 11 Sep '18

11 Sep '18

Hi, we have a failure in basic suite for test metrics_bootstrap.metrics_and_log_collector. We failed to configure the hosts for metrics collection which causes failure in the test. The change that is reported as cause of failure is: https://github.com/oVirt/ovirt-ansible-manageiq/commit/ 6697fc98f934beb9fece6d0224c0b013411b84e6 You can see the full logs here: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3078/artifact/b… error: PLAY RECAP ********************************************************************* lago-basic-suite-4-2-host-0 : ok=1 changed=0 unreachable=0 failed=1 lago-basic-suite-4-2-host-1 : ok=1 changed=0 unreachable=0 failed=1 localhost : ok=53 changed=24 unreachable=0 failed=0 2018-09-11 09:06:18,713::ssh.py::ssh::96::lago.ssh::DEBUG::Command d69e71be on lago-basic-suite-4-2-engine errors: [WARNING]: Could not match supplied host pattern, ignoring: metrics_store 2018-09-11 09:06:18,713::utils.py::_ret_via_queue::60::lago.utils::ERROR::Error while running thread 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 "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/003_00_metrics_bootstrap.py", line 54, in configure_metrics ' Exit code is %s' % result.code File "/usr/lib/python2.7/site-packages/nose/tools/trivial.py", line 29, in eq_ raise AssertionError(msg or "%r != %r" % (a, b)) AssertionError: Configuring ovirt machines for metrics failed. Exit code is 2 2018-09-11 09:06:38,897::ssh.py::ssh::81::lago.ssh::DEBUG::Command d648c70a on lago-basic-suite-4-2-engine returned with 0 2018-09-11 09:06:38,897::ssh.py::ssh::89::lago.ssh::DEBUG::Command d648c70a on lago-basic-suite-4-2-engine output: This command will collect system configuration and diagnostic information from this system.

2 1

[CQ]: 94271, 1 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Sep '18

11 Sep '18

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

1 0

Change in barak-test[master]: jenkins integ test
by review＠gerrit-staging.phx.ovirt.org 11 Sep '18

11 Sep '18

From Evgheni Dereveanchin <ederevea(a)redhat.com>: Evgheni Dereveanchin has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/17 ) Change subject: jenkins integ test ...................................................................... Patch Set 1: gerrit el7 migration test -- To view, visit https://gerrit-staging.phx.ovirt.org/17 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: barak-test Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I50acc69c8c5b6b3e03f3ced23d72c883ac4db2c2 Gerrit-Change-Number: 17 Gerrit-PatchSet: 1 Gerrit-Owner: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Tue, 11 Sep 2018 12:37:22 +0000 Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-2487) Re: [ovirt-users] Re: Managing multiple oVirt installs?
by sbonazzo (oVirt JIRA) 11 Sep '18

11 Sep '18

sbonazzo created OVIRT-2487: ------------------------------- Summary: Re: [ovirt-users] Re: Managing multiple oVirt installs? Key: OVIRT-2487 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2487 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra 2018-09-04 14:06 GMT+02:00 femi adegoke <ovirt(a)fateknollogee.com>: > Just an FYI: > The Glance registry does not have the latest current stable release which > is Gaprindashvili-4 > Thanks for reporting, opening a ticket. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/users@ovirt.org/ > message/V4C73LOMHDJR3MPA4E4CXTBNVQXHGNP4/ > -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

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

11 Sep '18

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

2 1

issue in vdsm monitoring
by Dafna Ron 11 Sep '18

11 Sep '18

Hi, I have been seeing random failures of tests in different projects caused by vdsm monitoring. I need someone from vdsm to please help debug this issue. From what I can see, the test suspend/resume vm failed because we could not query the status of the vm on the host. you can see full log from failed tests here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10208/artifa… Here are the errors that I can see in the vdsm which seem to suggest that there is an issue getting stats on the vm which was suspended and caused the failure of the test: 2018-09-11 00:40:05,896-0400 INFO (monitor/c1fe6e6) [storage.StorageDomain] Removing remnants of deleted images [] (fileSD:734) 2018-09-11 00:40:07,957-0400 DEBUG (qgapoller/1) [vds] Not sending QEMU-GA command 'guest-get-users' to vm_id='8214433a-f233-4aaa-aeda-2ce1d31c78dc', command is not supported (qemuguestagent:192) 2018-09-11 00:40:08,068-0400 DEBUG (periodic/3) [virt.sampling.VMBulkstatsMonitor] sampled timestamp 4296118.49 elapsed 0.010 acquired True domains all (sampling:443) 2018-09-11 00:40:08,271-0400 DEBUG (jsonrpc/1) [jsonrpc.JsonRpcServer] Calling 'Image.prepare' in bridge with {u'allowIllegal': True, u'storagepoolID': u'e80a56d9-74da-498a-b010-4a9df287f11d', u'imageID': u'd4c831e6-02d2-4d89-b516-0ec4597 5e024', u'volumeID': u'15b07af1-625b-42e3-b62a-8e7c7a120a56', u'storagedomainID': u'f1744940-41b6-4d35-b7bf-870c4e07d995'} (__init__:329) 2018-09-11 00:40:10,846-0400 DEBUG (vmchannels) [virt.vm] (vmId='8214433a-f233-4aaa-aeda-2ce1d31c78dc') Guest connection timed out (guestagent:556) 2018-09-11 00:40:11,637-0400 DEBUG (jsonrpc/5) [jsonrpc.JsonRpcServer] Calling 'Host.getStats' in bridge with {} (__init__:329) 2018-09-11 00:40:11,637-0400 INFO (jsonrpc/5) [api.host] START getStats() from=::ffff:192.168.201.4,49184 (api:47) 2018-09-11 00:40:11,643-0400 DEBUG (jsonrpc/5) [root] cannot read eth0 speed (nic:42) 2018-09-11 00:40:11,645-0400 DEBUG (jsonrpc/5) [root] cannot read eth1 speed (nic:42) 2018-09-11 00:40:11,647-0400 DEBUG (jsonrpc/5) [root] cannot read eth2 speed (nic:42) 2018-09-11 00:40:11,649-0400 DEBUG (jsonrpc/5) [root] cannot read eth3 speed (nic:42) 2018-09-11 00:40:11,667-0400 INFO (jsonrpc/5) [api.host] FINISH getStats error=[Errno 22] Invalid argument from=::ffff:192.168.201.4,49184 (api:51) 2018-09-11 00:40:11,667-0400 ERROR (jsonrpc/5) [jsonrpc.JsonRpcServer] Internal server error (__init__:350) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request res = method(**params) File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 202, in _dynamicMethod result = fn(*methodArgs) File "<string>", line 2, in getStats File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 49, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1407, in getStats multipath=True)} File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 49, in get_stats decStats = stats.produce(first_sample, last_sample) File "/usr/lib/python2.7/site-packages/vdsm/host/stats.py", line 71, in produce stats.update(get_interfaces_stats()) File "/usr/lib/python2.7/site-packages/vdsm/host/stats.py", line 153, in get_interfaces_stats return net_api.network_stats() File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 63, in network_stats return netstats.report() File "/usr/lib/python2.7/site-packages/vdsm/network/netstats.py", line 31, in report stats = link_stats.report() File "/usr/lib/python2.7/site-packages/vdsm/network/link/stats.py", line 41, in report speed = vlan.speed(i.device) File "/usr/lib/python2.7/site-packages/vdsm/network/link/vlan.py", line 36, in speed dev_speed = nic.read_speed_using_sysfs(dev_name) File "/usr/lib/python2.7/site-packages/vdsm/network/link/nic.py", line 48, in read_speed_using_sysfs s = int(f.read()) IOError: [Errno 22] Invalid argument 2018-09-11 00:40:11,669-0400 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.getStats failed (error -32603) in 0.03 seconds (__init__:312) 2018-09-11 00:40:14,656-0400 DEBUG (jsonrpc/2) [jsonrpc.JsonRpcServer] Calling 'Host.getAllVmStats' in bridge with {} (__init__:329) 2018-09-11 00:40:14,657-0400 INFO (jsonrpc/2) [api.host] START getAllVmStats() from=::1,46772 (api:47) 2018-09-11 00:40:14,659-0400 INFO (jsonrpc/2) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::1,46772 (api:53) 2018-09-11 00:40:14,660-0400 DEBUG (jsonrpc/2) [jsonrpc.JsonRpcServer] Return 'Host.getAllVmStats' in bridge with (suppressed) (__init__:356) 2018-09-11 00:40:14,661-0400 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) 2018-09-11 00:40:14,674-0400 DEBUG (jsonrpc/1) [jsonrpc.JsonRpcServer] Calling 'Host.getAllVmIoTunePolicies' in bridge with {} (__init__:329) 2018-09-11 00:40:14,675-0400 INFO (jsonrpc/1) [api.host] START getAllVmIoTunePolicies() from=::1,46772 (api:47) 2018-09-11 00:40:14,675-0400 INFO (jsonrpc/1) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'message': 'Done', 'code': 0}, 'io_tune_policies_dict': {'8214433a-f233-4aaa-aeda-2ce1d31c78dc': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/blockSD/f1744940-41b6-4d35-b7bf-870c4e07d995/images/9a3659dc-339e-4b3f-a1d1-6ee3debb6168/e2570635-a798-4e9e-a0ea-88436d5b296f', 'name': 'vda'}]}}} from=::1,46772 (api:53) 2018-09-11 00:40:14,675-0400 DEBUG (jsonrpc/1) [jsonrpc.JsonRpcServer] Return 'Host.getAllVmIoTunePolicies' in bridge with {'8214433a-f233-4aaa-aeda-2ce1d31c78dc': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/blockSD/f1744940-41b6-4d35-b7bf-870c4e07d995/images/9a3659dc-339e-4b3f-a1d1-6ee3debb6168/e2570635-a798-4e9e-a0ea-88436d5b296f', 'name': 'vda'}]}} (__init__:356) 2018-09-11 00:40:14,675-0400 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmIoTunePolicies succeeded in 0.00 seconds (__init__:312) 2018-09-11 00:40:16,118-0400 DEBUG (jsonrpc/7) [jsonrpc.JsonRpcServer] Calling 'Host.getAllVmStats' in bridge with {} (__init__:329) 2018-09-11 00:40:16,119-0400 INFO (jsonrpc/7) [api.host] START getAllVmStats() from=::ffff:192.168.201.4,49184 (api:47) 2018-09-11 00:40:16,121-0400 INFO (jsonrpc/7) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:192.168.201.4,49184 (api:53) 2018-09-11 00:40:16,122-0400 DEBUG (jsonrpc/7) [jsonrpc.JsonRpcServer] Return 'Host.getAllVmStats' in bridge with (suppressed) (__init__:356) 2018-09-11 00:40:16,122-0400 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.01 seconds (__init__:312) 2018-09-11 00:40:17,956-0400 DEBUG (qgapoller/2) [vds] Not sending QEMU-GA command 'guest-get-users' to vm_id='8214433a-f233-4aaa-aeda-2ce1d31c78dc', command is not supported (qemuguestagent:192) 2018-09-11 00:40:18,025-0400 DEBUG (periodic/3) [virt.periodic] Looking for stale paused VMs (periodic:388) I can also see this in Super vdsm which may be related but I an not 100% sure its related to current issue: MainProcess|jsonrpc/2::DEBUG::2018-09-11 00:33:20,012::cmdutils::159::root::(exec_cmd) SUCCESS: <err> = ''; <rc> = 0 ifup/on039d2d88d8ee4::DEBUG::2018-09-11 00:33:20,238::cmdutils::159::root::(exec_cmd) FAILED: <err> = 'Running scope as unit 2f1f417d-85b9-46c0-b7d7-6082836daaae.scope.\n/etc/sysconfig/network-scripts/ifup-eth: line 321: 20715 Terminated /sbin/dhclient ${DHCLIENTARGS} ${DEVICE}\nDevice "on039d2d88d8ee4" does not exist.\nCannot find device "on039d2d88d8ee4"\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d 8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevic e "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d 8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevic e "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d 8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevic e "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\nDevice "on039d2d88d8ee4" does not exist.\n'; <rc> = 1 ifup/on039d2d88d8ee4::ERROR::2018-09-11 00:33:20,238::concurrent::202::root::(run) FINISH thread <Thread(ifup/on039d2d88d8ee4, stopped daemon 140281550731008)> failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 195, in run ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 948, in _exec_ifup _exec_ifup_by_name(iface.name, cgroup) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 934, in _exec_ifup_by_name raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '') ConfigNetworkError: (29, '\n') thanks, Dafna

1 0

[CQ]: 6697fc9 (ovirt-ansible-manageiq) failed "ovirt-4.2" system tests
by oVirt Jenkins 11 Sep '18

11 Sep '18

Change 6697fc9 (ovirt-ansible-manageiq) 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://github.com/oVirt/ovirt-ansible-manageiq/commit/6697fc98f934beb9fece… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3078/

1 0

[CQ]: 93345, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Sep '18

11 Sep '18

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

2 1

[JIRA] (OVIRT-2486) master ovirt-engine is failing for both basic and upgrade suites on test 002_bootstrap.add_cluster
by Dafna Ron (oVirt JIRA) 11 Sep '18

11 Sep '18

Dafna Ron created OVIRT-2486: -------------------------------- Summary: master ovirt-engine is failing for both basic and upgrade suites on test 002_bootstrap.add_cluster Key: OVIRT-2486 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2486 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest the failure is due to a regression, change reported for this failure: https://gerrit.ovirt.org/#/c/93345/ it seems correct. error: https://pastebin.com/7x0TanJr full logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10187/artifa… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[CQ]: 93487, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Sep '18

11 Sep '18

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

2 1

[CQ]: 93399, 17 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 11 Sep '18

11 Sep '18

Change 93399,17 (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/93399/17 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10181/

2 1

failure in ost test - Invalid argument - help in debugging issue
by Dafna Ron 11 Sep '18

11 Sep '18

Hi, can someone please have a look at this ost failure? it is not related to the change that failed and I think its probably a race. you can find the logs here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10175/artifa… The error I can see is this: https://pastebin.com/pm6x0W62 Thanks, Dafna

3 2

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 10-09-2018 ] [ 002_bootstrap.add_hosts, bootstrap.verify_add_hosts ]
by Dafna Ron 11 Sep '18

11 Sep '18

Hi, we had a failure to deploy hosts for change; https://gerrit.ovirt.org/#/c/ 94228/1 I don't think its related directly to the change but anything between packaging: use system provided nimbus-jose-jwt also on el7 patch and current patch could have caused the failure. https://gerrit.ovirt.org/#/q/project:ovirt-engine+status:Merged+branch:mast… Sandro, Ondra, can you please have a look? (Relevant) error snippet from the log: <error> 018-09-10 04:05:33,850-04 INFO [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] Installation of lago-upgrade-from-release-suite-master-host-0. Executing command via SSH umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar -b1 --warning=no-timestamp -C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True < /var/cache/ovirt-engine/ovirt-host-deploy.tar 2018-09-10 04:05:33,850-04 INFO [org.ovirt.engine.core.utils.archivers.tar.CachedTar] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] Tarball '/var/cache/ovirt-engine/ovirt-host-deploy.tar' refresh 2018-09-10 04:05:33,915-04 INFO [org.ovirt.engine.core.uutils.ssh.SSHDialog] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] SSH execute 'root@lago-upgrade-from-release-suite-master-host-0' 'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar -b1 --warning=no-timestamp -C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True' 2018-09-10 04:05:34,694-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [33bb53b] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-upgrade-from-release-suite-master-host-0. Stage: Initializing. 2018-09-10 04:05:34,710-04 INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (VdsDeploy) [33bb53b] transaction rolled back 2018-09-10 04:05:34,719-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [33bb53b] Error during deploy dialog 2018-09-10 04:05:34,723-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] Error during host lago-upgrade-from-release-suite-master-host-0 install 2018-09-10 04:05:34,736-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host lago-upgrade-from-release-suite-master-host-0: CallableStatementCallback; SQL [{call insertauditlog(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}ERROR: invalid byte sequence for encoding "UTF8": 0x00; nested exception is org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00. 2018-09-10 04:05:34,737-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] Error during host lago-upgrade-from-release-suite-master-host-0 install, preferring first exception: CallableStatementCallback; SQL [{call insertauditlog(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}ERROR: invalid byte sequence for encoding "UTF8": 0x00; nested exception is org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 2018-09-10 04:05:34,737-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] Host installation failed for host 'febee66d-fa4b-4321-9c99-cb053ddd4817', 'lago-upgrade-from-release-suite-master-host-0': CallableStatementCallback; SQL [{call insertauditlog(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}ERROR: invalid byte sequence for encoding "UTF8": 0x00; nested exception is org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 2018-09-10 04:05:34,760-04 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] START, SetVdsStatusVDSCommand(HostName = lago-upgrade-from-release-suite-master-host-0, SetVdsStatusVDSCommandParameters:{hostId='febee66d-fa4b-4321-9c99-cb053ddd4817', status='InstallFailed', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 793ad1ed 2018-09-10 04:05:34,769-04 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] FINISH, SetVdsStatusVDSCommand, return: , log id: 793ad1ed 2018-09-10 04:05:34,781-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] EVENT_ID: VDS_INSTALL_FAILED(505), Host lago-upgrade-from-release-suite-master-host-0 installation failed. CallableStatementCallback; SQL [{call insertauditlog(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}ERROR: invalid byte sequence for encoding "UTF8": 0x00; nested exception is org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00. 2018-09-10 04:05:34,794-04 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33bb53b] Lock freed to object 'EngineLock:{exclusiveLocks='[febee66d-fa4b-4321-9c99-cb053ddd4817=VDS]', sharedLocks=''}' 2018-09-10 04:06:10,003-04 INFO [org.ovirt.engine.core.bll.quota.QuotaManager] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [] Quota Cache updated. (20 msec) (END) </error>

3 4

[CQ]: 94215, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Sep '18

11 Sep '18

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

1 0

[JIRA] (OVIRT-2485) shift.ovirt.org tls verification does not seem to work
by Roman Mohr (oVirt JIRA) 11 Sep '18

11 Sep '18

Roman Mohr created OVIRT-2485: --------------------------------- Summary: shift.ovirt.org tls verification does not seem to work Key: OVIRT-2485 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2485 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roman Mohr Assignee: infra Hi, If I expose an app on shift.ovirt.org via a tls endpoint, I get public urls like this: https://kubevirt-prow.apps.ovirt.org/hook. I can also use them e.g. on github for webhook, however I have to disable tls verification. For instance github gives me otherwise: We couldn’t deliver this payload: Peer certificate cannot be authenticated with given CA certificates Should there be a verifyable certificate? Best Regards, Roman -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[CQ]: 94008,3 (otopi) failed "ovirt-master" system tests
by oVirt Jenkins 11 Sep '18

11 Sep '18

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

1 0

[CQ]: 92815, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Sep '18

11 Sep '18

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

1 0

oVirt infra daily report - unstable production jobs - 579
by jenkins＠jenkins.phx.ovirt.org 11 Sep '18

11 Sep '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/579//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 93444, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Sep '18

10 Sep '18

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

1 0

[JIRA] (OVIRT-2484) ovirt engine master and 4.2 are failing on random tests with possible cause an Invalid argument
by Dafna Ron (oVirt JIRA) 10 Sep '18

10 Sep '18

Dafna Ron created OVIRT-2484: -------------------------------- Summary: ovirt engine master and 4.2 are failing on random tests with possible cause an Invalid argument Key: OVIRT-2484 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2484 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra seems we are getting random tests failure which I believe are caused by this error: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/periodic.py", line 220, in __call__ self._func() File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 576, in __call__ sample = HostSample(self._pid) File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 240, in __init__ self.interfaces = _get_interfaces_and_samples() File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 202, in _get_interfaces_and_samples links_and_samples[link.name] = InterfaceSample(link) File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 109, in __init__ self.speed = _getLinkSpeed(link) File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 590, in _getLinkSpeed speed = vlan.speed(dev.name) File "/usr/lib/python2.7/site-packages/vdsm/network/link/vlan.py", line 35, in speed dev_speed = nic.read_speed_using_sysfs(dev_name) File "/usr/lib/python2.7/site-packages/vdsm/network/link/nic.py", line 47, in read_speed_using_sysfs s = int(f.read()) IOError: [Errno 22] Invalid argument ovirt 4.2 - migration test failed: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3069/artifact/b… master: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10176/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0