August 2021 - Infra - oVirt List Archives

[CQ]: 116269, 7 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Aug '21

24 Aug '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 774 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Aug '21

24 Aug '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/77… Build Number: 774 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #774 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 5

oVirt infra daily report - unstable production jobs - 1657
by jenkins＠jenkins.phx.ovirt.org 24 Aug '21

24 Aug '21

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1657//artifact/exported… Cheers, Jenkins

1 0

[JIRA] (OVIRT-3116) Fail fast on unsupported configuration
by Ehud Yonasi (oVirt JIRA) 23 Aug '21

23 Aug '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3116?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-3116: ------------------------------------ [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] Currently it is implemented that it will take the user request value or the default parameters. To make this work I need to split that apart and make it throw an exception on wrong configuration. > Fail fast on unsupported configuration > -------------------------------------- > > Key: OVIRT-3116 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3116 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > When using: > host-distro: el8 > The CI ignores the unknown configuration "el8" runs the job anywhere. > Then the job fails after many minutes, wasting resources and developers > time running on el7, where the tests cannot pass. > Lets fix to fail fast on the first unknown configuration, don't run anything > if the configuration is invalid. > Example builds: > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/29292/ > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/29293/ > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/29295/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100174)

1 0

[CQ]: 116298,4 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 23 Aug '21

23 Aug '21

Change 116298,4 (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/jenkins/+/#/c/116298/4 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/674/

1 0

[CQ]: 116073, 10 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Aug '21

23 Aug '21

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

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #592 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Aug '21

23 Aug '21

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

1 1

[CQ]: 116220, 2 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Aug '21

23 Aug '21

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

1 0

[oVirt Jenkins] cleanup-gated-ovirt-master - Build #608 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Aug '21

23 Aug '21

Build: https://jenkins.ovirt.org/job/cleanup-gated-ovirt-master/608/ Build Name: #608 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 4

[JIRA] (OVIRT-3116) Fail fast on unsupported configuration
by Evgheni Dereveanchin (oVirt JIRA) 23 Aug '21

23 Aug '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3116?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-3116: --------------------------------------------- [~accountid:5aa0f39f5a4d022884128a0f] could you please check how this can be implemented? I had a feeling that failing jobs if the distro is unknown was expected behavior. > Fail fast on unsupported configuration > -------------------------------------- > > Key: OVIRT-3116 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3116 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > When using: > host-distro: el8 > The CI ignores the unknown configuration "el8" runs the job anywhere. > Then the job fails after many minutes, wasting resources and developers > time running on el7, where the tests cannot pass. > Lets fix to fail fast on the first unknown configuration, don't run anything > if the configuration is invalid. > Example builds: > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/29292/ > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/29293/ > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/29295/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100174)

1 0