June 2017 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1391) Add repo injection capabilities to STD-CI

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1391?page=com.atlassian.jir... ] Daniel Belenky reassigned OVIRT-1391: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Add repo injection capabilities to STD-CI > ----------------------------------------- > > Key: OVIRT-1391 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1391 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: Daniel Belenky > Priority: High > Labels: containers, mock_runner.sh, standard-ci > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSP...] flow implementation process. > We want to add to standard-CI ('{{mock-runner.sh}}') the capability to provide a project with information about package repositories that unrelated to the setup of the environment that standard-CI scripts run in. > A projects will specify required repositories by including one or more files that match the pattern “{{automation/$STD_CI_STAGE.\*.yumrepos.\*}}”, where “{{$STG_CI_STAGE}}” is e.g “{{build-system-artifacts}}” and the wildcard sections can be omitted along with the dots that precede them. The file should be in the format of a yum configuration file and include configuration for required yum repositories. To avoid the projects having to maintain URLs for yum repositories, the file may contain configurations without repository URLs specified and with the “skip_if_unavailable” parameter set to “true”. Only the names of the repository configuration sections will be meaningful for the purpose of the CI system. For each such file the CI system will: > # Replace any configuration section that defines the “{{ovirt-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt packages for the distribution identified by "{{<distro-id>}}" may be obtained. “{{<distro-id>}}" will be a string such as “el7” or “fc25”. To allow avoiding collisions with the released oVirt yum configuration, the “{{ovirt-ci-<repoid>}}” and “{{ovirt-experimental-<repoid>}}” configuration section will be treated the same way. > # Replace any configuration section that defines the “{{ovirt-dependencies-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt dependency packages need to be obtained. These will include, among others, base operating system packages. The “{{ovirt-ci-dependencies-<repoid>}}” and “{{ovirt-experimental-dependencies-<repoid>}}” configuration section will be treated the same way. > # Run the mirror injection process. Any repository handled by this process will have the the “{{skip_if_unavailable}}” parameter removed if specified (To make the default value of “{{false}}” come into effect). > # Prepend a “{{\[main]}}” section that disables the use of the “{{/etc/yum.repos.d}}” directory. This will allow the file to appended to the "{{/etc/yun.conf}}” file to automatically disable all internet-facing preconfigured repositories. > To allow automation scripts to find the repository files prepared for them, several environment variables will be made available in the Standard-CI runtime environment: > # {{STD_CI_STAGE}}: Will contain the name of the Standard-CI stage, e.g. “{{build-artifacts}}”. > # {{STD_CI_DISTRO}}: Will contain the distribution version identifier (e.g “el7” or “fc25”) of the Standard-CI runtime. > # {{STD_CI_YUMREPOS}}: Will point to an existing “{{*.yumrepos}}” file that most closely matches the current running stage and distribution -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

7 years, 4 months

1
0
0 / 0

[oVirt Jenkins] standard-enqueue - Build #2002 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_849_924255919.1498487460705 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/2002/ Build Name: 2002 ovirt-engine-extension-aaa-jdbc (4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/78366 - title: Fix encrypted option in password-reset - project: ovirt-engine-extension-aaa-jdbc - branch: master - author: Miroslava Voglova <mvoglova(a)redhat.com> ------=_Part_849_924255919.1498487460705--

7 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jir... ] Evgheni Dereveanchin commented on OVIRT-1475: --------------------------------------------- I don't see any retention settings in the [job configuration yaml|https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/pr...] and not entirely sure where they're inherited from. As for build #97 - it is marked with the "keep this build forever" tag, that's why it was not deleted. > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

7 years, 4 months

1
0
0 / 0

[oVirt Jenkins] ovirt_master_hc-system-tests - Build # 141 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_600_1684416853.1498014845835 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/141/ Build Number: 141 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #141 [Shani Leviim] Remove 'provisioned_size' disk parameter [Shirly Radco] ovirt-engine-metrics: add build-on-demand job ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.py.junit.xml.[empty] Error Message: Stack Trace: Test report file /home/jenkins/workspace/ovirt_master_hc-system-tests/exported-artifacts/002_bootstrap.py.junit.xml was length 0 ------=_Part_600_1684416853.1498014845835--

7 years, 4 months

1
11
0 / 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months

by Yuval Turgeman (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jir... ] Yuval Turgeman commented on OVIRT-1475: --------------------------------------- There were more than 2 builds in the job's history after Sep 2016... why did it save that single job from 2016 ? > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

7 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months

by eedri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jir... ] eedri commented on OVIRT-1475: ------------------------------ Can you check what is the current configuration in YAML for keeping history for this job? > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

7 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jir... ] Evgheni Dereveanchin commented on OVIRT-1475: --------------------------------------------- This job has "Max # of builds to keep" equal to 2 so all older builds are deleted by Jenkins itself. I do not see any "max-total: 2" configuration in our YAMLs so not sure when this change was introduced. Recent job config history doesn't have anything related to changes in this parameter: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

7 years, 4 months

1
0
0 / 0

Change 78548,4 (vdsm) failed system tests

by oVirt Jenkins

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

7 years, 4 months

1
0
0 / 0

[oVirt Jenkins] ovirt_master_he-system-tests - Build # 2 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_843_1122038011.1498479232852 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/2/ Build Number: 2 Build Status: Failure Triggered By: Started by user Yuval Turgeman ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_843_1122038011.1498479232852--

7 years, 4 months

1
0
0 / 0

[oVirt Jenkins] ovirt_master_he-system-tests - Build # 1 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_841_1510856062.1498478703250 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/1/ Build Number: 1 Build Status: Failure Triggered By: Started by user Yuval Turgeman ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_841_1510856062.1498478703250--

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2017