July 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1526) Re-factor github std-CI job templates
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

Barak Korren created OVIRT-1526: ----------------------------------- Summary: Re-factor github std-CI job templates Key: OVIRT-1526 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1526 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: Low There are several issues with the YAML for the GiHUb job templates we currently have in '{{standard-stage.yaml}}': # The 'check-patch' job has got a different template then the other jobs. This makes it harder to write project YAML files, And also very different from YAML files for Gerrit-based projects. # Because of #1, the 'check-patch' jobs don't have any publishers defined. This makes them different from other STD-CI jobs that always have publishers that do things like collect and display test results. Doing this is probably a prerequisite to OVIRT-1084 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1526) Re-factor github std-CI job templates
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1526?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1526: -------------------------------- Epic Link: OVIRT-400 > Re-factor github std-CI job templates > ------------------------------------- > > Key: OVIRT-1526 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1526 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: standard-ci > > There are several issues with the YAML for the GiHUb job templates we currently have in '{{standard-stage.yaml}}': > # The 'check-patch' job has got a different template then the other jobs. This makes it harder to write project YAML files, And also very different from YAML files for Gerrit-based projects. > # Because of #1, the 'check-patch' jobs don't have any publishers defined. This makes them different from other STD-CI jobs that always have publishers that do things like collect and display test results. > Doing this is probably a prerequisite to OVIRT-1084 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1525) Automatically send welcome message on first push to gerrit
by Yedidyah Bar David (oVirt JIRA) 12 Jul '17

12 Jul '17

Yedidyah Bar David created OVIRT-1525: ----------------------------------------- Summary: Automatically send welcome message on first push to gerrit Key: OVIRT-1525 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1525 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Some weeks ago I pushed my first patch to openstack [1], and it automatically added a reviewer called 'Welcome, new contributor' which reviewed/commented (and so sent an email) with some introductory material. Might be nice to have on oVirt's gerrit. [1] https://review.openstack.org/471802 -- Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1524) ovirt-release_4.1_check-patch-el7-x86_64 failing due to missing yum.conf
by Evgheni Dereveanchin (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1524?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1524: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > ovirt-release_4.1_check-patch-el7-x86_64 failing due to missing yum.conf > ------------------------------------------------------------------------ > > Key: OVIRT-1524 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1524 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The [job|http://jenkins.ovirt.org/job/ovirt-release_4.1_check-patch-el7-x86_64/7…] recently started failing consistently with the following error: > + rm -f /etc/yum/yum.conf > + yum repolist enabled > CRITICAL:yum.cli:Config error: Error accessing file for config file:///etc/yum.conf > Related [test code|https://github.com/oVirt/ovirt-release/blob/master/automation/check-pa…] hasn't been changed recently, so maybe it is related to the new version of mock in use. Opening this to investigate the cause and possible solutions -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1524) ovirt-release_4.1_check-patch-el7-x86_64 failing due to missing yum.conf
by Evgheni Dereveanchin (oVirt JIRA) 12 Jul '17

12 Jul '17

Evgheni Dereveanchin created OVIRT-1524: ------------------------------------------- Summary: ovirt-release_4.1_check-patch-el7-x86_64 failing due to missing yum.conf Key: OVIRT-1524 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1524 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra The [job|http://jenkins.ovirt.org/job/ovirt-release_4.1_check-patch-el7-x86_64/7…] recently started failing consistently with the following error: + rm -f /etc/yum/yum.conf + yum repolist enabled CRITICAL:yum.cli:Config error: Error accessing file for config file:///etc/yum.conf Related [test code|https://github.com/oVirt/ovirt-release/blob/master/automation/check-pa…] hasn't been changed recently, so maybe it is related to the new version of mock in use. Opening this to investigate the cause and possible solutions -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-682) Improve CI logging and reporting to Gerrit (v2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-682: ------------------------------------ Gerrit trigger feedback configuration is not flexible enough to let us have each job customize the output it sends to Gerrit. Instead we will need to send the results to Gerrit ourselves with something like the GerritServer object (See [Gerrit 74874|https://gerrit.ovirt.org/#/c/74874/] But when sending results, the Gerrit trigger also calculates the votes for the flags by looking at all the jobs that it invoked. To do this ourselves we will need to be able to track all the checking scripts that are running in parallel for a given patchset, this probably means we have to implement OVIRT-1522 first. > Improve CI logging and reporting to Gerrit (v2) > ----------------------------------------------- > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: eedri > Assignee: infra > Priority: Low > Labels: standard-ci > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-682) Improve CI logging and reporting to Gerrit (v2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-682: ------------------------------- Summary: Improve CI logging and reporting to Gerrit (v2) (was: Improve CI logging) > Improve CI logging and reporting to Gerrit (v2) > ----------------------------------------------- > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: eedri > Assignee: infra > Priority: Low > Labels: standard-ci > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1523: ------------------------------------- One quick and dirty way to achieve this that was suggested by [~nsoffer(a)redhat.com] and made possible by [Gerrit 79316|https://gerrit.ovirt.org/#/c/79316/] is to create "fake distributions" such as "el7:a" and "el7:b". This will allow people to use YAML to make jobs that target those fake distributions. Making such "fake distributions" is actually quite easy in practice since we got [Gerrit 73690|https://gerrit.ovirt.org/#/c/73690/] > Support multipile executors per CI stage (V2) > --------------------------------------------- > > Key: OVIRT-1523 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. > It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. > Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

Barak Korren created OVIRT-1523: ----------------------------------- Summary: Support multipile executors per CI stage (V2) Key: OVIRT-1523 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1523: -------------------------------- Epic Link: OVIRT-400 > Support multipile executors per CI stage (V2) > --------------------------------------------- > > Key: OVIRT-1523 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. > It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. > Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0