- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 353
by jenkins＠jenkins.phx.ovirt.org 14 Jun '17

14 Jun '17

------=_Part_379_359593749.1497481201710 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/353//artifact/exported-a… Cheers, Jenkins ------=_Part_379_359593749.1497481201710 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 14/06/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/">system-sync_mirrors-centos-updates-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_379_359593749.1497481201710--

1 0

Re: [ovirt-devel] [ovirt-system-tests] Failed after fluentd rpm ubdate
by Eyal Edri 14 Jun '17

14 Jun '17

Adding infra as well. Currently, master OST is still failing on this. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7189/testR… On Wed, Jun 14, 2017 at 4:54 PM, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > On Wed, Jun 14, 2017 at 3:50 PM, Yedidyah Bar David <didi(a)redhat.com> > wrote: > >> On Wed, Jun 14, 2017 at 4:44 PM, Gil Shinar <gshinar(a)redhat.com> wrote: >> > This patch fixes the chgrp but not we see: >> > >> > Unable to start service fluentd: Job for fluentd.service failed because >> > start of the service was attempted too often >> >> Adding Shirly. >> >> Do we collect syslog (/var/log/messages or journalctl)? If so, we can try >> to see why it fails. >> > > Adding also Richard who may be interested on this. > > >> >> > >> > >> > On Wed, Jun 14, 2017 at 12:29 PM, Yedidyah Bar David <didi(a)redhat.com> >> > wrote: >> >> >> >> On Wed, Jun 14, 2017 at 11:34 AM, Valentina Makarova >> >> <makarovavs07(a)gmail.com> wrote: >> >> > Hello! >> >> > >> >> > Fluentd packages was modified yesterday there >> >> > >> >> > http://resources.ovirt.org/pub/ovirt-master-snapshot-static/ >> rpm/el7/noarch/ >> >> > This repository is referenced in reposync-config. >> >> > >> >> > And now run_suile.sh failed in 003_00_metrics_bootstrap test with >> error: >> >> > TASK [fluentd : Ensure fluentd configuration directory exists] >> >> > ***************** fatal: [localhost]: FAILED! => {"changed": false, >> >> > "failed": true, "gid": 0, "group": "root", "mode": "0755", "msg": >> "chgrp >> >> > failed: failed to look up group fluentd" >> >> > >> >> > And the same error on host0 and hos1. >> >> > >> >> > Does anyone know how to fix it? >> >> >> >> Should be fixed by [1]. Either wait for the repos to be updated or >> install >> >> the update from jenkins (link to it inside [1]). >> >> >> >> [1] https://gerrit.ovirt.org/#/c/78140/ >> >> >> >> > >> >> > Sincerely, Valentina Makarova >> >> > >> >> > >> >> > _______________________________________________ >> >> > Devel mailing list >> >> > Devel(a)ovirt.org >> >> > http://lists.ovirt.org/mailman/listinfo/devel >> >> >> >> >> >> >> >> -- >> >> Didi >> >> _______________________________________________ >> >> Devel mailing list >> >> Devel(a)ovirt.org >> >> http://lists.ovirt.org/mailman/listinfo/devel >> > >> > >> >> >> >> -- >> Didi >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> > > > > -- > > SANDRO BONAZZOLA > > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

2 1

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 184 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jun '17

14 Jun '17

------=_Part_324_1874063996.1497366515870 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build Number: 184 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #184 [Gil Shinar] Configured ovirt-host to use on-change instead of timed [Sandro Bonazzola] ovirt-host: drop fc26 and ppc64le [Yuval Turgeman] Revert "engine-appliance: build in selinux enforcing mode" ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_324_1874063996.1497366515870--

1 1

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Barak Korren (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1441: ------------------------------------- So again, I see 3 types of packages: 1. 3rd party packages for which an RPM is available for an official and reliable source (e.g. CentOS, Fedora) 2. 3rd party packages where there is no RPM avialable and we want to ship an RPM with oVirt 3. oVirt packages For the 1st case we setup the 3rd party repo in the '*release*.rpm'. For the 3rd case the package is usually built and managed by the CI systems. We seem to be dealing with the 2nd case here, the solution for that was to make an oVirt "adapter" source repo with a usual build-artifacts job that creates or downloads the RPM. One is runs, the rest works just like for packages of the 3rd case. Since we want to track and gate changes to oVirt, the "adapter" repo should be made so that is downloads a very specific version of the 3rd party package. That way getting an updated version of the upstream package requires a patch to the adapter repo which can be tracked and gated. See also discussion in OVIRT-1299. > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Yedidyah Bar David (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-1441: ------------------------------------------- On Wed, Jun 14, 2017 at 3:33 PM, Barak Korren (oVirt JIRA) That's a good question from oVirt-metrics' perspective. I am not sure. For now we wanted something quick and this was the solution - build in copr, copy to -static. I am not saying it's the best solution. I did open the other ticket... I am just suggesting it as a real-life use-case that we should consider when designing how to compose our repos etc. -- Didi > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Barak Korren (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1441: ------------------------------------- So how are we going to deal with this feature when targeting Fedora? Maybe we can ask them to just build for Fedora too? > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Yedidyah Bar David (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-1441: ------------------------------------------- On Wed, Jun 14, 2017 at 3:12 PM, Barak Korren (oVirt JIRA) IIRC they do build it in centos-opstools, but not for fedora. -- Didi > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Barak Korren (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1441: ------------------------------------- I'm guessing the copr functionality is based on some existing tools in Fedora and/or CentOS, so perhaps its just a matter of finding out what those are... As long as the package is going to be an oVirt dependency, and it is not shipped by anyone else, its better to move it through the oVirt CI process. If the upstream will release official RPMs at some point we can switch to mirroring their repos for the CI system. > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Yedidyah Bar David (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-1441: ------------------------------------------- On Wed, Jun 14, 2017 at 2:24 PM, Barak Korren (oVirt JIRA) That's indeed an option. This specific project is not really part of oVirt, IIUC. It will be used as part of the common-logging effort, aka https://github.com/ViaQ . Actually this was the first time I built a rubygem in copr (and one of the first few times I built anything. But I did have an account), and it was as simple as choosing a build type rubygem and passing the link to it. I don't think we can beat that yet... -- Didi > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by Barak Korren (oVirt JIRA) 14 Jun '17

14 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1441: ------------------------------------- See the path that the UX team took, they have "adapter" projects that get the dependencies from the upstream sources and then build the ovirt-specific packages from them. You can have your project run the build in copr, but it should be just as simple to just run the build on our hardware and not depend on an external service. > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)

1 0