May 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2064) "Borrow" slaves from CentOS CI

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-2064: ----------------------------------- Summary: "Borrow" slaves from CentOS CI Key: OVIRT-2064 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2064 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra Priority: High [CentOS CI|https://wiki.centos.org/QaWiki/CI] is a generic shared platform for building CI service for Open Source projects. Amount other things, CentOS CI makes physical and virtual hosts available for running CI processes via the [Duffy|http://wiki.centos.org/QaWiki/CI/Duffy] system. We should make oVirt CI able to consume resources from CentOs CI to augment and someday replace the hardware resources available to oVirt CI. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

6 years, 5 months

1
0
0 / 0

[CQ]: 87243, 1 (ovirt-engine-extension-aaa-misc) failed "ovirt-4.1" system tests

by oVirt Jenkins

Change 87243,1 (ovirt-engine-extension-aaa-misc) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/87243/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1787/

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2058) rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2058?page=com.atlassian.jir... ] eyal edri commented on OVIRT-2058: ---------------------------------- Didn't Yaniv said it should be ovirt-engine because it's just supporting the engine and not hosts? I don't mind either way, just let me know the final name. On Wed, May 30, 2018, 14:57 sbonazzo (oVirt JIRA) < > rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade > ----------------------------------------------------------------------- > > Key: OVIRT-2058 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2058 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Douglas Landgraf > Assignee: infra > > Hi, > Please rename project ovirt-engine-hyper-upgrade to > rhvm-fast-forward-upgrade in gerrit and related components. > Reason: project name consistency > Thanks! > -- > Cheers > Douglas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2058) rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade

by sbonazzo (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2058?page=com.atlassian.jir... ] sbonazzo commented on OVIRT-2058: --------------------------------- > So is it OK to rename it to ovirt-engine-fast-forward-upgrade? Last decision I got is "ovirt-fast-forward-upgrade" > rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade > ----------------------------------------------------------------------- > > Key: OVIRT-2058 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2058 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Douglas Landgraf > Assignee: infra > > Hi, > Please rename project ovirt-engine-hyper-upgrade to > rhvm-fast-forward-upgrade in gerrit and related components. > Reason: project name consistency > Thanks! > -- > Cheers > Douglas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2058) rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2058?page=com.atlassian.jir... ] eyal edri commented on OVIRT-2058: ---------------------------------- So is it OK to rename it to ovirt-engine-fast-forward-upgrade? On Sun, May 27, 2018, 08:01 eyal edri (oVirt JIRA) < > rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade > ----------------------------------------------------------------------- > > Key: OVIRT-2058 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2058 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Douglas Landgraf > Assignee: infra > > Hi, > Please rename project ovirt-engine-hyper-upgrade to > rhvm-fast-forward-upgrade in gerrit and related components. > Reason: project name consistency > Thanks! > -- > Cheers > Douglas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2058) rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2058?page=com.atlassian.jir... ] eyal edri commented on OVIRT-2058: ---------------------------------- I'm not sure it's a good idea to name upstream project rhvm just for consistency, there are other projects which have this diff between upstream and downstream. Maybe you meant ovirt-fast-forward-upgrade? Also, I'm not sure it's possible to rename a git repo, we probably need to create new one and repush all content. On Fri, May 25, 2018, 19:16 Douglas Landgraf (oVirt JIRA) < > rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade > ----------------------------------------------------------------------- > > Key: OVIRT-2058 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2058 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Douglas Landgraf > Assignee: infra > > Hi, > Please rename project ovirt-engine-hyper-upgrade to > rhvm-fast-forward-upgrade in gerrit and related components. > Reason: project name consistency > Thanks! > -- > Cheers > Douglas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

6 years, 5 months

3
2
0 / 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 194 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-mast... Build Number: 194 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #194 [Marcin Mirecki] network: add sshlib exec_command ----------------- Failed Tests: ----------------- No tests ran.

6 years, 5 months

1
2
0 / 0

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

6 years, 5 months

1
0
0 / 0

[CQ]: 88007, 1 (ovirt-engine-extension-aaa-ldap) failed "ovirt-4.1" system tests

by oVirt Jenkins

Change 88007,1 (ovirt-engine-extension-aaa-ldap) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/88007/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1784/

6 years, 5 months

1
0
0 / 0

[CQ]: 91691, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

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

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra May 2018