September 2019 - Infra - Ovirt List Archives

[CQ]: 102935, 5 (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 102935,5 (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/102935/5 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/16032/

5 years, 2 months

1
0
0 / 0

[CQ]: 102934,5 (ovirt-engine) failed "ovirt-master" system tests

by oVirt Jenkins

Change 102934,5 (ovirt-engine) 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/102934/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16028/

5 years, 2 months

1
0
0 / 0

[CQ]: 103476,2 (vdsm) failed "ovirt-master" system tests

by oVirt Jenkins

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

5 years, 2 months

1
0
0 / 0

[oVirt CI] standard-enqueue - Build #24069 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: http://jenkins.ovirt.org/job/standard-enqueue/24069/ Build Name: #24069 Build Description: Gerrit: 103524 - ovirt-engine (4.2) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/103524 - title: core: Fill jackson deserialization whitelist - project: ovirt-engine - branch: ovirt-engine-4.2 - author: Martin Peřina <mperina(a)redhat.com>

5 years, 2 months

1
0
0 / 0

[oVirt CI] standard-enqueue - Build #24065 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: http://jenkins.ovirt.org/job/standard-enqueue/24065/ Build Name: #24065 Build Description: Gerrit: 103533 - ovirt-engine (4.3.5.z) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/103533 - title: build: post ovirt-engine-4.3.5.5 - project: ovirt-engine - branch: ovirt-engine-4.3.5.z - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

5 years, 2 months

1
2
0 / 0

[JIRA] (OVIRT-2798) add ovirt-provider-ovn project to the new gating system

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2798?page=com.atlassian.jir... ] Anton Marchukov commented on OVIRT-2798: ---------------------------------------- We are currently working on running OST in gating and can switch once it is finished. > add ovirt-provider-ovn project to the new gating system > ------------------------------------------------------- > > Key: OVIRT-2798 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2798 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Miguel Duarte de Mora Barroso > Assignee: infra > > Hi, > I'd like to request that ovirt-provider-ovn is added to the new gating system. > Thanks in advance, > Miguel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

5 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1448: ------------------------------------- well, we're probably not going to implement this, but as long as we use CQ - we can still get issues where dependent patches get tested alone > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

5 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-2801) ovirt-provider-ovn needs to be built downstream: last built: '1.2.26' while last tagged is '4.2.2.5'

by Sandro Bonazzola (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2801?page=com.atlassian.jir... ] Sandro Bonazzola reassigned OVIRT-2801: --------------------------------------- Assignee: Sandro Bonazzola (was: infra) > ovirt-provider-ovn needs to be built downstream: last built: '1.2.26' while last tagged is '4.2.2.5' > ---------------------------------------------------------------------------------------------------- > > Key: OVIRT-2801 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2801 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: Sandro Bonazzola > > Hi, > just noticed this weird error while checking latest available version with > my tools: > ovirt-provider-ovn needs to be built downstream: last built: '1.2.26' while > last tagged is '4.2.2.5' > and checking https://github.com/oVirt/ovirt-provider-ovn/releases I indeed > see > on 20 Mar 2018 ovirt-engine-4.2.2.5 tag. > can you please check what screwed up ovirt-provider-ovn tagging? > Thanks, > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

5 years, 2 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 957

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

5 years, 2 months

1
0
0 / 0

[CQ]: ceeadd7 (ovirt-web-ui) 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 ceeadd7 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change b1ee64c (ovirt-web-ui) 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 b1ee64c (ovirt-web-ui) 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-web-ui/commit/ceeadd7fe44a51ff5f8058bf4256... For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/b1ee64c14323aca370dc5470426e... For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16011/

5 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra September 2019