May 2017 - Infra - Ovirt List Archives

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

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1385: ------------------------------------- The runtime different between cache-using mock runs and non-cache using ones is more then a minute, so playing with the caching intervals would be I'll advised. Making this configurable would not be trivial at all. I suppose the {{*.packages}} file format can be extended to allow requesting certain versions or forcing updates. Such changes will need to go into the {{mock_runner.sh}} code. There had been similar requests made in the past (Can't locate the relevant tickets right now). I'm afraid I cannot prioritize this ticket very highly though. We are a bit reluctant to add any new features to {{mock_runner.sh}} for the time being. Patches will be welcome though.... > 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 > Reporter: Vojtech Szocs > Assignee: infra > > 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.967.1#100042)

7 years, 6 months

1
0
0 / 0

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

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1385: -------------------------------- Issue Type: Improvement (was: By-EMAIL) > 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 > Reporter: Vojtech Szocs > Assignee: infra > > 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.967.1#100042)

7 years, 6 months

1
0
0 / 0

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

by Vojtech Szocs (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jir... ] Vojtech Szocs updated OVIRT-1385: --------------------------------- Description: 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. was: There are multiple oVirt projects [1] which contain a `build.packages.force` (or similar) file, along with the following code in their build script: # 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} [1] 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 configurable per-project. Not sure what's the best approach here, please advise. > 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: By-EMAIL > Reporter: Vojtech Szocs > Assignee: infra > > 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.967.1#100042)

7 years, 6 months

1
0
0 / 0

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

by Vojtech Szocs (oVirt JIRA)

Vojtech Szocs created OVIRT-1385: ------------------------------------ Summary: 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: By-EMAIL Reporter: Vojtech Szocs Assignee: infra There are multiple oVirt projects [1] which contain a `build.packages.force` (or similar) file, along with the following code in their build script: # 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} [1] 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 configurable per-project. Not sure what's the best approach here, please advise. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1384) replace faulty hardware on PHX storage02

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1384?page=com.atlassian.jir... ] Evgheni Dereveanchin reassigned OVIRT-1384: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > replace faulty hardware on PHX storage02 > ---------------------------------------- > > Key: OVIRT-1384 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1384 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > ovirt-storage02 crashed a few months ago and Dell recommends replacing the motherboard and CPU which falls under warranty. For this we need to move workloads to ovirt-storage01 and shut down the faulty server. Then Dell's technicians can come on site to perform replacement. > Motherboard replacement will cause MAC address changes of the NICs and may affect the RAID. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1384) replace faulty hardware on PHX storage02

by Evgheni Dereveanchin (oVirt JIRA)

Evgheni Dereveanchin created OVIRT-1384: ------------------------------------------- Summary: replace faulty hardware on PHX storage02 Key: OVIRT-1384 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1384 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra ovirt-storage02 crashed a few months ago and Dell recommends replacing the motherboard and CPU which falls under warranty. For this we need to move workloads to ovirt-storage01 and shut down the faulty server. Then Dell's technicians can come on site to perform replacement. Motherboard replacement will cause MAC address changes of the NICs and may affect the RAID. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1383) Create Jenkisn+Python talk for PyCon

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1383?page=com.atlassian.jir... ] Barak Korren reassigned OVIRT-1383: ----------------------------------- Assignee: Barak Korren (was: infra) > Create Jenkisn+Python talk for PyCon > ------------------------------------ > > Key: OVIRT-1383 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1383 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > My proposal was accepted, now need to make a presentation and prepare for it. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1383) Create Jenkisn+Python talk for PyCon

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-1383: ----------------------------------- Summary: Create Jenkisn+Python talk for PyCon Key: OVIRT-1383 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1383 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Barak Korren Assignee: infra Priority: Highest My proposal was accepted, now need to make a presentation and prepare for it. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

7 years, 6 months

1
0
0 / 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6698 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_0_2085931500.1494940259890 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6698/, Build Number: 6698, Build Status: FAILURE ------=_Part_0_2085931500.1494940259890--

7 years, 6 months

1
1
0 / 0

[JIRA] (OVIRT-1382) Failing vdsm_master_build_artifacts-el7-ppc64 on check-merge

by Gil Shinar (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1382?page=com.atlassian.jir... ] Gil Shinar reassigned OVIRT-1382: --------------------------------- Assignee: Gil Shinar (was: infra) > Failing vdsm_master_build_artifacts-el7-ppc64 on check-merge > ------------------------------------------------------------ > > Key: OVIRT-1382 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1382 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: Gil Shinar > > Following https://gerrit.ovirt.org/76781 merge, the following build failed: > http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/1737/ > Is this a known issue? > Thanks, > Edy. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

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