- Infra - oVirt List Archives

[JIRA] (OVIRT-1413) Enable configuring mirrors from a file
by Barak Korren (oVirt JIRA) 28 May '17

28 May '17

Barak Korren created OVIRT-1413: ----------------------------------- Summary: Enable configuring mirrors from a file Key: OVIRT-1413 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1413 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: Barak Korren Assignee: infra Right now mirror configuration can only come from a JSON file stored on the mirrors server. We want to enable taking the configuration from a local file also, this will enable jobs to manipulate mirror information before running the mirror injection process. This would be especially useful for change queue test jobs in order to enable fine-grained control over the mirrors being tested. -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-1413) Enable configuring mirrors from a file
by Barak Korren (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1413?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1413: -------------------------------- Epic Link: OVIRT-403 > Enable configuring mirrors from a file > -------------------------------------- > > Key: OVIRT-1413 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1413 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: mirrors > > Right now mirror configuration can only come from a JSON file stored on the mirrors server. > We want to enable taking the configuration from a local file also, this will enable jobs to manipulate mirror information before running the mirror injection process. > This would be especially useful for change queue test jobs in order to enable fine-grained control over the mirrors being tested. -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-1379) add support for fedora rawhide in mock_runner
by eedri (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1379?page=com.atlassian.jira.… ] eedri commented on OVIRT-1379: ------------------------------ [~sbonazzo@redhat.com][~bkorren@redhat.com] I think we need to agree on the amount of Fedora versions we should support/run in CI. IMO we should support only latest and maybe even consider only rawhide if it makes sense and working ( it will reduce our work to refresh Fedora OSs on each release which takes a significant amount of time both from dev and CI ). > add support for fedora rawhide in mock_runner > --------------------------------------------- > > Key: OVIRT-1379 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1379 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: infra > > Moving this to Jira. > On 15 May 2017 at 10:31, Barak Korren <bkorren(a)redhat.com> wrote: > > On 15 May 2017 at 10:13, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > >> > >> > >> > >> On Sat, May 13, 2017 at 11:12 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >>> > >>> Hi Sandro, what is needed to build and public ovirt-imageio for Fedora rawhide? > >> > >> > >> We miss support for rawhide in mock runner, within jenkins git repo. > >> Adding Barak > > > > Get we get a mock configuration for it from somewhere? > > They are building it in Koji so I guess they have rawhide buildroots already no? > > > > Is there any other special behaviour needed besides the proper mock > > configuration? > > > > -- > > Barak Korren > > RHV DevOps team , RHCE, RHCi > > Red Hat EMEA > > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-1379) add support for fedora rawhide in mock_runner
by eedri (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1379?page=com.atlassian.jira.… ] eedri updated OVIRT-1379: ------------------------- Summary: add support for fedora rawhide in mock_runner (was: Re: Building ovirt-imageio for rawhide) > add support for fedora rawhide in mock_runner > --------------------------------------------- > > Key: OVIRT-1379 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1379 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: infra > > Moving this to Jira. > On 15 May 2017 at 10:31, Barak Korren <bkorren(a)redhat.com> wrote: > > On 15 May 2017 at 10:13, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > >> > >> > >> > >> On Sat, May 13, 2017 at 11:12 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >>> > >>> Hi Sandro, what is needed to build and public ovirt-imageio for Fedora rawhide? > >> > >> > >> We miss support for rawhide in mock runner, within jenkins git repo. > >> Adding Barak > > > > Get we get a mock configuration for it from somewhere? > > They are building it in Koji so I guess they have rawhide buildroots already no? > > > > Is there any other special behaviour needed besides the proper mock > > configuration? > > > > -- > > Barak Korren > > RHV DevOps team , RHCE, RHCi > > Red Hat EMEA > > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-1275) Allow anonymous access to nagios dashboard
by eedri (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1275?page=com.atlassian.jira.… ] eedri updated OVIRT-1275: ------------------------- Epic Link: (was: OVIRT-840) > Allow anonymous access to nagios dashboard > ------------------------------------------ > > Key: OVIRT-1275 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1275 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: infra > > Right now you need a password to just view the main page of monitoring.ovirt.org. > It will be better if you won't need to login just to view the status, that way anyone can look at current status w/o logging in and verify if there is an outage. -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-1061) Update http://monitoring.ovirt.org/ovirt.apps/
by eedri (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1061?page=com.atlassian.jira.… ] eedri updated OVIRT-1061: ------------------------- Epic Link: (was: OVIRT-840) > Update http://monitoring.ovirt.org/ovirt.apps/ > ---------------------------------------------- > > Key: OVIRT-1061 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1061 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please update http://monitoring.ovirt.org/ovirt.apps/ with all monitoring > and production services currently being used in oVirt infra. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-840) oVirt Monitoring & Reporting
by eedri (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-840?page=com.atlassian.jira.p… ] eedri updated OVIRT-840: ------------------------ Parent: OVIRT-103 Issue Type: Sub-task (was: Epic) Epic Name: (was: oVirt Monitoring & Reporting) Epic Status: (was: To Do) Epic Color: (was: ghx-label-2) > oVirt Monitoring & Reporting > ---------------------------- > > Key: OVIRT-840 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-840 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eedri > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-840) oVirt Monitoring & Reporting
by eedri (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-840?page=com.atlassian.jira.p… ] eedri updated OVIRT-840: ------------------------ Status: Done (was: To Do) Resolution: Fixed trying to reduce the epics to one per domain. detailed projects can use components. > oVirt Monitoring & Reporting > ---------------------------- > > Key: OVIRT-840 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-840 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: eedri > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-1412) mock_runner root cache only holds for one day
by Barak Korren (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1412?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1412: ----------------------------------- Assignee: Barak Korren (was: infra) > mock_runner root cache only holds for one day > --------------------------------------------- > > Key: OVIRT-1412 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1412 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > > It turns out that 'mock' check the timestamp on the mock cache and compares it with the timestamp on the mock configuration file. If the cache is older, mock removes it. > As a work-around for that, mock_runner includes a '{{touch}}' command that changes the timestamp on the mock configuration file to be a day older then the current time. Once the cache becomes older then a day it should also become older then the configuration file and therefore cleaned. > We need to change this so that instead of touching the configuration file we will touch the cache itself to ensure it is newer. That will guarantee the cache will stick around and will be used until it is erased by our cleanup script. -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-1412) mock_runner root cache only holds for one day
by Barak Korren (oVirt JIRA) 28 May '17

28 May '17

Barak Korren created OVIRT-1412: ----------------------------------- Summary: mock_runner root cache only holds for one day Key: OVIRT-1412 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1412 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Barak Korren Assignee: infra It turns out that 'mock' check the timestamp on the mock cache and compares it with the timestamp on the mock configuration file. If the cache is older, mock removes it. As a work-around for that, mock_runner includes a '{{touch}}' command that changes the timestamp on the mock configuration file to be a day older then the current time. Once the cache becomes older then a day it should also become older then the configuration file and therefore cleaned. We need to change this so that instead of touching the configuration file we will touch the cache itself to ensure it is newer. That will guarantee the cache will stick around and will be used until it is erased by our cleanup script. -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-1412) mock_runner root cache only holds for one day
by Barak Korren (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1412?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1412: -------------------------------- Epic Link: OVIRT-400 > mock_runner root cache only holds for one day > --------------------------------------------- > > Key: OVIRT-1412 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1412 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > It turns out that 'mock' check the timestamp on the mock cache and compares it with the timestamp on the mock configuration file. If the cache is older, mock removes it. > As a work-around for that, mock_runner includes a '{{touch}}' command that changes the timestamp on the mock configuration file to be a day older then the current time. Once the cache becomes older then a day it should also become older then the configuration file and therefore cleaned. > We need to change this so that instead of touching the configuration file we will touch the cache itself to ensure it is newer. That will guarantee the cache will stick around and will be used until it is erased by our cleanup script. -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

Gerrit HTTP-500 error
by Gil Shinar 28 May '17

28 May '17

Hi, Today we have seen this error again. Restart of Gerrit fixed this issue. I have look a bit and found the following thread: https://groups.google.com/forum/#!topic/repo-discuss/N5bIo4VlPGU According to the above, there's a bug in Jgit. Its cache gets corrupted and it cannot find objects. Restart of Gerrit causes it to clear the cache and that fixes the problem. In order to fix that, you cannot only upgrade JGit (as it is built in inside Gerrit installation) but you have to upgrade Gerrit. According to Gerrit's release notes, this issue had been fixed only since Gerrit 2.13.7 <https://www.gerritcodereview.com/releases/2.13.md#2.13.7> It is not urgent but looks like a good idea to upgrade to this version or the latest (2.13.8). Gil

2 1

[JIRA] (OVIRT-1411) Reviewing some (most) patches on Gerrit causes HTTP-500
by Barak Korren (oVirt JIRA) 28 May '17

28 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1411?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1411: ----------------------------------- Assignee: Barak Korren (was: infra) > Reviewing some (most) patches on Gerrit causes HTTP-500 > ------------------------------------------------------- > > Key: OVIRT-1411 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1411 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Gerrit/git > Reporter: Allon Mureinik > Assignee: Barak Korren > Priority: High > > Clicking through Gerrit's dashboard to review patches ends up with HTTP-500 instead of getting to the patch. E.g. link: > https://gerrit.ovirt.org/#/c/77210/ > It's impossible to review patches like this. -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

[JIRA] (OVIRT-1411) Reviewing some (most) patches on Gerrit causes HTTP-500
by Allon Mureinik (oVirt JIRA) 28 May '17

28 May '17

Allon Mureinik created OVIRT-1411: ------------------------------------- Summary: Reviewing some (most) patches on Gerrit causes HTTP-500 Key: OVIRT-1411 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1411 Project: oVirt - virtualization made easy Issue Type: Outage Components: Gerrit/git Reporter: Allon Mureinik Assignee: infra Priority: High Clicking through Gerrit's dashboard to review patches ends up with HTTP-500 instead of getting to the patch. E.g. link: https://gerrit.ovirt.org/#/c/77210/ It's impossible to review patches like this. -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

oVirt infra daily report - unstable production jobs - 335
by jenkins＠jenkins.phx.ovirt.org 27 May '17

27 May '17

------=_Part_51_416327784.1495926006851 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/335//artifact/exported-a… Cheers, Jenkins ------=_Part_51_416327784.1495926006851 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 - 27/05/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/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</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/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</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/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</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/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</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_51_416327784.1495926006851--

1 0

[JIRA] (OVIRT-1410) Please update #ovirt motd with oVirt 4.1.2
by eedri (oVirt JIRA) 27 May '17

27 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1410?page=com.atlassian.jira.… ] eedri commented on OVIRT-1410: ------------------------------ I don't even know if we have permissions to change the IRC channel settings, I guess it's up to the moderator in the channel, Which is the first person to log in? > Please update #ovirt motd with oVirt 4.1.2 > ------------------------------------------ > > Key: OVIRT-1410 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1410 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Joining #ovirt channel gives: > *oVirt 4.1.0 is now available. Please register your nick to participate in > this channel.* > Please, update with oVirt 4.1.2. > -- > 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> -- This message was sent by Atlassian JIRA (v1000.1010.1#100044)

1 0

oVirt infra daily report - unstable production jobs - 334
by jenkins＠jenkins.phx.ovirt.org 26 May '17

26 May '17

------=_Part_41_598452139.1495839607354 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/334//artifact/exported-a… Cheers, Jenkins ------=_Part_41_598452139.1495839607354 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 - 26/05/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/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</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_41_598452139.1495839607354--

1 0

[JIRA] (OVIRT-1410) Please update #ovirt motd with oVirt 4.1.2
by sbonazzo (oVirt JIRA) 26 May '17

26 May '17

sbonazzo created OVIRT-1410: ------------------------------- Summary: Please update #ovirt motd with oVirt 4.1.2 Key: OVIRT-1410 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1410 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Joining #ovirt channel gives: *oVirt 4.1.0 is now available. Please register your nick to participate in this channel.* Please, update with oVirt 4.1.2. -- 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> -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1548 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 May '17

25 May '17

------=_Part_33_1893911001.1495738209416 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1548/, Build Number: 1548, Build Status: FAILURE ------=_Part_33_1893911001.1495738209416--

1 1

oVirt infra daily report - unstable production jobs - 333
by jenkins＠jenkins.phx.ovirt.org 25 May '17

25 May '17

------=_Part_35_501644934.1495753209090 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/333//artifact/exported-a… Cheers, Jenkins ------=_Part_35_501644934.1495753209090 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 - 25/05/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/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</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_4.1/">test-repo_ovirt_experimental_4.1</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_35_501644934.1495753209090--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6844 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 May '17

25 May '17

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

1 1

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #1604 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 May '17

25 May '17

------=_Part_29_604233638.1495724765671 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/1604/ Build Name: 1604 ovirt-log-collector (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/77274 - title: produceReport: Rename DWH to Data Warehouse - project: ovirt-log-collector - branch: master - author: Douglas Schilling Landgraf <dougsland(a)redhat.com> ------=_Part_29_604233638.1495724765671--

1 0

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1408: -------------------------------------------------- [~sbonazolla(a)redhat.com] fyi. > Please remove github/ovirt-web-ui from standard CI > -------------------------------------------------- > > Key: OVIRT-1408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please remove github/ovirt-web-ui from standard CI since Travis is used instead. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1408: -------------------------------------------------- this patch should remove the jenkins jobs https://gerrit.ovirt.org/#/c/77342/1 Once its merged you can delete the automation dir on the project itself. > Please remove github/ovirt-web-ui from standard CI > -------------------------------------------------- > > Key: OVIRT-1408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please remove github/ovirt-web-ui from standard CI since Travis is used instead. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI
by Michal Skrivanek (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1408: ----------------------------------------- ah, ok, thanks for clarification. [~eedri] to answer - well, the project decided to go through a more simple way than what's currently implemented for most other ovirt projects, being quite different in technology and scope. It works well and I do not see a need for more complex verification any time soon.(It doesn't mean it cannot be consumed by OST like anything else, I just currently do not see any way how would it be useful) The automation dir is getting in a way just in the sense of the broken jobs. So..it saves some common oVirt infrastructure resources. > Please remove github/ovirt-web-ui from standard CI > -------------------------------------------------- > > Key: OVIRT-1408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please remove github/ovirt-web-ui from standard CI since Travis is used instead. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OST-39) Support for testing ovirt-containers in OST
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plug… ] eyal edri [Administrator] updated OST-39: ----------------------------------------- Summary: Support for testing ovirt-containers in OST (was: Run OST against vdsm+Engine on kubernetes) > Support for testing ovirt-containers in OST > ------------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI
by Barak Korren (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1408: ------------------------------------- If you just remove 'automation', you'll just get broken jobs. You need to remove the jobs themselves by removing the project YAML from the 'jenkins' repo. > Please remove github/ovirt-web-ui from standard CI > -------------------------------------------------- > > Key: OVIRT-1408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please remove github/ovirt-web-ui from standard CI since Travis is used instead. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI
by Michal Skrivanek (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1408: ----------------------------------------- [~mlibra(a)redhat.com] I wonder what is being requested from infra? Why you can't simply remove the automation/ directory in the project when it's not needed? Does it break anything? > Please remove github/ovirt-web-ui from standard CI > -------------------------------------------------- > > Key: OVIRT-1408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please remove github/ovirt-web-ui from standard CI since Travis is used instead. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1409) Build oVirt 4.1.3 tc1
by sbonazzo (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1409?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1409: ---------------------------- Assignee: sbonazzo (was: infra) Status: In Progress (was: To Do) > Build oVirt 4.1.3 tc1 > --------------------- > > Key: OVIRT-1409 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1409 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: oVirt Release Mgmt > Reporter: sbonazzo > Assignee: sbonazzo > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1409) Build oVirt 4.1.3 tc1
by sbonazzo (oVirt JIRA) 25 May '17

25 May '17

sbonazzo created OVIRT-1409: ------------------------------- Summary: Build oVirt 4.1.3 tc1 Key: OVIRT-1409 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1409 Project: oVirt - virtualization made easy Issue Type: Task Components: oVirt Release Mgmt Reporter: sbonazzo Assignee: infra Priority: Highest -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1409) Build oVirt 4.1.3 tc1
by sbonazzo (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1409?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1409: ---------------------------- Epic Link: OVIRT-411 > Build oVirt 4.1.3 tc1 > --------------------- > > Key: OVIRT-1409 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1409 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: oVirt Release Mgmt > Reporter: sbonazzo > Assignee: infra > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1239) tracking ticket for supporting multiple organization in GH CR builder plugin
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1239?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1239: --------------------------------------------- Epic Link: OVIRT-403 > tracking ticket for supporting multiple organization in GH CR builder plugin > ---------------------------------------------------------------------------- > > Key: OVIRT-1239 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1239 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Lowest > > In current implementation credentials can be specified only per server so it's not possible to use different credentials for ovirt and lago projects using same jenkins instance as we do. > During meeting with [~eedri] we decided to evaluate two possible options: > 1) Webhooks to trigger build. From first glance it looks good but not sure if it's solve the problem with credentials. It should be implemented anyway and it's tracked under OVIRT-1142 > 2) Open RFE under GH PR Builder plugin to support this out of the box. > This ticket is opened to track progress on second option. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1239) tracking ticket for supporting multiple organization in GH CR builder plugin
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1239?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1239: --------------------------------------------- Epic Link: OVIRT-403 > tracking ticket for supporting multiple organization in GH CR builder plugin > ---------------------------------------------------------------------------- > > Key: OVIRT-1239 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1239 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Lowest > > In current implementation credentials can be specified only per server so it's not possible to use different credentials for ovirt and lago projects using same jenkins instance as we do. > During meeting with [~eedri] we decided to evaluate two possible options: > 1) Webhooks to trigger build. From first glance it looks good but not sure if it's solve the problem with credentials. It should be implemented anyway and it's tracked under OVIRT-1142 > 2) Open RFE under GH PR Builder plugin to support this out of the box. > This ticket is opened to track progress on second option. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1271) GH plugin tries to consume gerrit's projects
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1271?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1271: --------------------------------------------- Epic Link: OVIRT-403 > GH plugin tries to consume gerrit's projects > -------------------------------------------- > > Key: OVIRT-1271 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1271 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > Jenkins logs are flooded with: > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins-whitelist.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL git://gerrit.ovirt.org/vdsm.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > While the messages itself are harmless they floods the logs and consume jenkins master's resources. > See https://issues.jenkins-ci.org/browse/JENKINS-24422 for more details. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1271) GH plugin tries to consume gerrit's projects
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1271?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1271: --------------------------------------------- Epic Link: OVIRT-403 > GH plugin tries to consume gerrit's projects > -------------------------------------------- > > Key: OVIRT-1271 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1271 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > Jenkins logs are flooded with: > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins-whitelist.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL git://gerrit.ovirt.org/vdsm.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > While the messages itself are harmless they floods the logs and consume jenkins master's resources. > See https://issues.jenkins-ci.org/browse/JENKINS-24422 for more details. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1318) configure backup of status.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1318?page=com.atlassian.jira.… ] 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-appl… -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1318) configure backup of status.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1318?page=com.atlassian.jira.… ] 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-appl… -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1319) configure backup of stats.phx.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1319?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-1319) configure backup of stats.phx.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1319?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] 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)

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #1598 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 May '17

25 May '17

------=_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--

1 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) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1198?page=com.atlassian.jira.… ] 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/con… > I think I saw another one earlier this week, also on fc25. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 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) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1198?page=com.atlassian.jira.… ] 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/con… > I think I saw another one earlier this week, also on fc25. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1226?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1226?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-1273) Greetings from Jessie
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1273?page=com.atlassian.jira.… ] eyal edri [Administrator] deleted OVIRT-1273: --------------------------------------------- > Greetings from Jessie > --------------------- > > Key: OVIRT-1273 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1273 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: jp005(a)jp-balancer.com > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1276) generate a link to OST automation job
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1276: --------------------------------------------- Epic Link: OVIRT-400 > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: rgolan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1276) generate a link to OST automation job
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1276: --------------------------------------------- Epic Link: OVIRT-400 > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: rgolan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0

[JIRA] (OVIRT-1374) Provide a mechanism to obtain an ever increasing build number
by eyal edri [Administrator] (oVirt JIRA) 25 May '17

25 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1374?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1374: --------------------------------------------- Epic Link: OVIRT-400 > Provide a mechanism to obtain an ever increasing build number > ------------------------------------------------------------- > > Key: OVIRT-1374 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1374 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Juan Hernández > Assignee: infra > > Currently when a project needs to generate unique names for artifacts, they have to use mechanisms like embedding the date and/or the git hash into the artifact name. For example, when a new build of the Ruby SDK is generated, the name of the RPM is like this: > rubygem-ovirt-engine-sdk4-4.2.0-1.alpha0.20170505gita6de891.el7.centos.ppc64le.rpm > That information is useful, and usually unique. But can be repeated if the same jobs is manually triggered the same day, as the date and the git hash will be the same. > In addition the date may be misleading, because a build performed later but using an old commit, will look newer than an older build that uses a newer commit. > A possible solution is to count the number of commits since certain well known commit. But this isn't reliable if the repository isn't completely cloned, for example if it is cloned with '--depth 1', as that well known commit may not be in the cloned repository. That cloning out of the control of the automation scripts. > So my suggestion/request is to add to the CI/CD environment a mechanism to provide that sequence to the jobs explicitly. I'd suggest to use the count of commits since the initial commit of the repository. The CI/CD environment performs the clone, so it can make sure it has all the relevant commits. > This information could be passed to the build-artifacts.sh script in an environment variable, or in the command line, or in a file in a known location. > With that each project could (optionally) modify its automation scripts to include that number. for example, in the Ruby SDK I'd like to generate RPMs like this: > rubygem-ovirt-engine-sdk4-4.2.0-1.alpha0.<that-number>.rpm -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

1 0