May 2017 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1318) configure backup of status.ovirt.org

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1318?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1318: --------------------------------------------- Epic Link: OVIRT-403 > configure backup of status.ovirt.org > ------------------------------------ > > Key: OVIRT-1318 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1318 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > status.ovirt.org was set up - need to investigate if it needs to be backed up or we can produce documentation to set up a new stats page in case something happens to the existing OpenShift gear. > We can use OpenShift's built in backup/restore functionality: > https://developers.openshift.com/managing-your-applications/backing-up-ap... -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1319) configure backup of stats.phx.ovirt.org

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1319?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1319: --------------------------------------------- Epic Link: OVIRT-403 > configure backup of stats.phx.ovirt.org > --------------------------------------- > > Key: OVIRT-1319 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1319 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > The stats server is accumulating historical data, backups need to be set up so that we don't risk losing it. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1319) configure backup of stats.phx.ovirt.org

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1319?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1319: --------------------------------------------- Epic Link: OVIRT-403 > configure backup of stats.phx.ovirt.org > --------------------------------------- > > Key: OVIRT-1319 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1319 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > The stats server is accumulating historical data, backups need to be set up so that we don't risk losing it. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1385: --------------------------------------------- Epic Link: OVIRT-400 > Support installing latest version of specific pkgs > -------------------------------------------------- > > Key: OVIRT-1385 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1385 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Vojtech Szocs > Assignee: infra > Priority: Low > Labels: mock_runner.sh > > There are multiple oVirt projects (see below) which contain a {{build.packages.force}} (or similar) file, along with the following code in their build script: > {code} > # The "build.packages.force" file contains BuildRequires packages > # to be installed using their latest version. > # Force CI to get the latest version of these packages: > dependencies="$(sed -e '/^[ \t]*$/d' -e '/^#/d' automation/build.packages.force)" > yum-deprecated clean metadata || yum clean metadata > yum-deprecated -y install ${dependencies} || yum -y install ${dependencies} > {code} > Used in projects: ovirt-engine-dashboard, ovirt-engine-nodejs-modules, ovirt-web-ui > Is it possible for CI to support this out of the box, using {{.force}} file convention? (basically a suffix to standard {{.packages}} files) > I've looked at OVIRT-921 and IIUC the yum cache is cleaned every 2 days, so an alternative to above proposal would be to have this interval configurable per-project. > Not sure what's the best approach here, please advise. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1385: --------------------------------------------- Epic Link: OVIRT-400 > Support installing latest version of specific pkgs > -------------------------------------------------- > > Key: OVIRT-1385 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1385 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Vojtech Szocs > Assignee: infra > Priority: Low > Labels: mock_runner.sh > > There are multiple oVirt projects (see below) which contain a {{build.packages.force}} (or similar) file, along with the following code in their build script: > {code} > # The "build.packages.force" file contains BuildRequires packages > # to be installed using their latest version. > # Force CI to get the latest version of these packages: > dependencies="$(sed -e '/^[ \t]*$/d' -e '/^#/d' automation/build.packages.force)" > yum-deprecated clean metadata || yum clean metadata > yum-deprecated -y install ${dependencies} || yum -y install ${dependencies} > {code} > Used in projects: ovirt-engine-dashboard, ovirt-engine-nodejs-modules, ovirt-web-ui > Is it possible for CI to support this out of the box, using {{.force}} file convention? (basically a suffix to standard {{.packages}} files) > I've looked at OVIRT-921 and IIUC the yum cache is cleaned every 2 days, so an alternative to above proposal would be to have this interval configurable per-project. > Not sure what's the best approach here, please advise. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #1598 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_22_1705966496.1495714122113 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/1598/ Build Name: 1598 ovirt-vdsmfake (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/77310 - title: README proofreading - project: ovirt-vdsmfake - branch: master - author: Roy Golan <rgolan(a)redhat.com> ------=_Part_22_1705966496.1495714122113--

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1198) Job times out on: 'Removing the used loop devices' on the initial clean up stage

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1198?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1198: --------------------------------------------- Epic Link: OVIRT-400 > Job times out on: 'Removing the used loop devices' on the initial clean up stage > -------------------------------------------------------------------------------- > > Key: OVIRT-1198 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1198 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: infra > > 15:44:38 Making sure there are no device mappings... > 15:44:38 Removing the used loop devices... > 21:44:37 Build timed out (after 360 minutes). Marking the build as failed. > 21:44:37 Build was aborted > (Notice the 6 hours between). > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/710/c... > I think I saw another one earlier this week, also on fc25. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1198) Job times out on: 'Removing the used loop devices' on the initial clean up stage

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1198?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1198: --------------------------------------------- Epic Link: OVIRT-400 > Job times out on: 'Removing the used loop devices' on the initial clean up stage > -------------------------------------------------------------------------------- > > Key: OVIRT-1198 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1198 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: infra > > 15:44:38 Making sure there are no device mappings... > 15:44:38 Removing the used loop devices... > 21:44:37 Build timed out (after 360 minutes). Marking the build as failed. > 21:44:37 Build was aborted > (Notice the 6 hours between). > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/710/c... > I think I saw another one earlier this week, also on fc25. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1226?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1226: --------------------------------------------- Blocked By: pending backport of findbugs code to 4.1 checkpatch Status: Blocked (was: To Do) > https://gerrit.ovirt.org/#/c/73161 marked with CI-1 > --------------------------------------------------- > > Key: OVIRT-1226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1226 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yevgeny Zaspitsky > Assignee: infra > > Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful > CI runs it had. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1226?page=com.atlassian.jir... ] eyal edri [Administrator] commented on OVIRT-1226: -------------------------------------------------- This shouldn't happen anymore on master since the code was moved to check-patch. We are waiting for dev to backport for 4.1 so you won't see this issue there as well. cc [~tnisan(a)redhat.com] > https://gerrit.ovirt.org/#/c/73161 marked with CI-1 > --------------------------------------------------- > > Key: OVIRT-1226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1226 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yevgeny Zaspitsky > Assignee: infra > > Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful > CI runs it had. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra May 2017