- Infra - oVirt List Archives

[JIRA] (OVIRT-711) Re: ovirt-provider-ovn - new gerrit.ovirt.org project
by Barak Korren (oVirt JIRA) 29 Aug '16

29 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-711?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-711: ------------------------------- Resolution: Fixed Status: Done (was: To Do) https://gerrit.ovirt.org/#/admin/projects/ovirt-provider-ovn > Re: ovirt-provider-ovn - new gerrit.ovirt.org project > ----------------------------------------------------- > > Key: OVIRT-711 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-711 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Barak Korren > > On Mon, Aug 29, 2016 at 1:11 PM, Marcin Mirecki <mmirecki(a)redhat.com> wrote: > > All, > > > > Can you please add a new project to gerrit.ovirt.org? > > The project name: ovirt-provider-ovn > > > > The project will contain the ovn external network provider. > > I will maintain it. > > > > Thanks, > > Marcin > > > -- > 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.285.1#100011)

1 0

[JIRA] (OVIRT-711) Re: ovirt-provider-ovn - new gerrit.ovirt.org project
by eyal edri [Administrator] (oVirt JIRA) 29 Aug '16

29 Aug '16

eyal edri [Administrator] created OVIRT-711: ----------------------------------------------- Summary: Re: ovirt-provider-ovn - new gerrit.ovirt.org project Key: OVIRT-711 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-711 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra On Mon, Aug 29, 2016 at 1:11 PM, Marcin Mirecki <mmirecki(a)redhat.com> wrote: > All, > > Can you please add a new project to gerrit.ovirt.org? > The project name: ovirt-provider-ovn > > The project will contain the ovn external network provider. > I will maintain it. > > Thanks, > Marcin > -- 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.285.1#100011)

1 0

Ansible work and organization
by Marc Dequènes (Duck) 29 Aug '16

29 Aug '16

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --rUake15nkmeqAJaPQq15DNkrU3qSBauM5 Content-Type: multipart/mixed; boundary="Bc659WIoxXX4Lhv6F7nK4c8PBqsasJf6j" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org> Cc: Michael Scherer <misc(a)redhat.com>, Karsten Wade <kwade(a)redhat.com> Message-ID: <81a28335-daf0-6bec-f7ae-92490f605606(a)redhat.com> Subject: Ansible work and organization --Bc659WIoxXX4Lhv6F7nK4c8PBqsasJf6j Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello folks, Since I started working on MM3 migration using Ansible, I received absolutely no feedback on the Ansible side of my work (and I asked several time, specifically on this aspect). At first I was new in the project, this was an attempt, I did not have much access, so it was created as an external git repository. Now very quickly an 'infra-ansible' repo was created and is already filling with review requests, but it seems to me we missed a few steps to coordinate. I'm not very familiar with the Gerrit workflow, but I'm learning, that's why I asked how I could integrate my work into the new repo but got no reply. It seemed to me my work could be a proper startup point, but now I'm faced with splitting and reintegrating my work with what is already coming in. It feels really useless a work, frustrating, and I also see no reason to loose all the history. Also I talked (ML, JIRA) about the roles we (in OSAS) were working on in order to share the load of the maintenance across several projects. Our experience is we often need almost the same classic features, so no reason to recreate the wheel and maintain different versions. We cannot trust any role on the Internet, but we can trust people in Red Hat or well known contributors. Nobody seemed to have an objection on this; nobody adked any question either. Nevertheless now the incoming reviews shows all of this is ignored and we're doing exactly it: a new postgresql role just popped-up in one review for example=C2=B8 but we alr= eady have one which is used by the MM3 work. I really tried to not be pushy, to ask for your opinions and reviews, but not much happened. I thought people were busy and it would come in time. Now I really don't know how I can catch up. So, we need to discuss: - how OSAS is going to work with the infra team: I'm new, so it's ok to feel a bit off, but I'd like better coordinati= on. I should not have to do extra work for integrating what I did on MM3, so clearly it's a failure I would like to avoid in the future. - how the config management will be organized/managed: there's many ways to organize, to call the roles, to test the rules. I've based my work on Misc's good work and added a few things myself.= I've also started working on testing using Vagrant: it works but has limitations. There's other attempts on the Internet but they also have drawbacks, maybe others we did not find yet. So there's room for discussion too, and integration with your CI. The current setup is in my repo. - how some resources (Ansible roles=E2=80=A6) are to be shared or not: the OSAS team is very small, shares its time and energy among several projects, you have several people with a good Puppet background but less so on Ansible, so I would advise sharing workload. The OSAS team can act as a neutral third party and insure all needed features are taken into account, reviews are done in a timely manner, for example. It was just a logical move from us to allow us spending less time on these tasks=C2=B8 but this is open to discussion (as stated on my previous mess= ages) As we say here: yoroshiku onegai shimasu. \_o< --Bc659WIoxXX4Lhv6F7nK4c8PBqsasJf6j-- --rUake15nkmeqAJaPQq15DNkrU3qSBauM5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXw8HRAAoJEFXp+fesHEQ/C5QP/27m98NAIpmdAi/tuJOruiOb y96pBd8KajR2ZUDtEqumZsNZaloVNHVBTDjPC4Cz6QHdiq4ECWUoe5L67fuscVow CNH8GNa6XwJyDnbas+57S0WSXHTkuZe3Tbib43kiYvI/VRrgJ9V9GdMe3KOwC2Pj 1LXnpCl3zSt3ktw99ErCj2c5nxzAl0AElPWzh0Ph6Mi7UfbhAAL05MpY3vK8Kwcq I/IKDytMLSJi8aeUqGGRZ7kj0G5Kvn2pvZ3ogA8dOgPopNMW4BysEuOoYcjzQZfB 8LujlKU8pVjb87gnQpJZcDiRPXkZVOwTplTvBhgr+RIaRTZ++NbDOvrM0kDIpnjp QEkD7x0Z8HkJ0vzX1j/sduiGPJ3xDK28mH/AtlmU4JIl2otYOgMoFPpgL+J3W+6C REcH9AFyEg0sCdaoGfKgOCXTQAYxNOgtiNw98QROE/LiVSkNv8ZUiupr0fM0Izfw HkCF+o5dES80Xl914gjSKXYnvv5EF1u76gMzBKvL/PcmCB4BbR6oo1ErOx1ZS3xX /+pJDSUIWiUxW6DBKNIGGfMNvEQYL8nI5mMBjXA8W7jA/3JWe+Gwnmd6/rkGNcA6 Bfq96ECwRrEcKhksYEam+FHeaVwdD8IcEfE3NF/liYi4Y3VGDHeUHmKFCYvoGWU8 bUveh9mS1l848tksFYWu =35u9 -----END PGP SIGNATURE----- --rUake15nkmeqAJaPQq15DNkrU3qSBauM5--

2 1

[JIRA] (OVIRT-244) Add RpmGrill and rpmlint validation to rpm build jobs
by sbonazzo (oVirt JIRA) 29 Aug '16

29 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-244?page=com.atlassian.jira.p… ] sbonazzo reassigned OVIRT-244: ------------------------------ Assignee: sbonazzo (was: infra) > Add RpmGrill and rpmlint validation to rpm build jobs > ----------------------------------------------------- > > Key: OVIRT-244 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-244 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: sbonazzo > > I suggest to add rpmlint and RpmGrill (https://gist.github.com/kholia/5899572) validation to rpm build jobs. > It may help finding issues in rpm packaging earlier. -- This message was sent by Atlassian JIRA (v1000.285.1#100011)

1 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
by sbonazzo (oVirt JIRA) 29 Aug '16

29 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] sbonazzo commented on OVIRT-226: -------------------------------- This is also really needed looking at recent history. > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.285.1#100011)

1 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
by sbonazzo (oVirt JIRA) 29 Aug '16

29 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] sbonazzo commented on OVIRT-226: -------------------------------- Moving to ovirt-system-tests checks. This is a functional test additional check; it requires engine to be deployed and running so looks like a lago related task. > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.285.1#100011)

1 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
by sbonazzo (oVirt JIRA) 29 Aug '16

29 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] sbonazzo reopened OVIRT-226: ---------------------------- > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.285.1#100011)

1 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
by sbonazzo (oVirt JIRA) 29 Aug '16

29 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-226: --------------------------- Summary: Add new checks to ovirt-system-test to ensure no sensitive data leak in logs (was: create new job to ensure no sensitive data leak in logs) > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.285.1#100011)

1 0

oVirt infra daily report - unstable production jobs - 60
by jenkins＠jenkins.phx.ovirt.org 29 Aug '16

29 Aug '16

------=_Part_105_1913039023.1472425207217 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/60//artifact/exported-ar… Cheers, Jenkins ------=_Part_105_1913039023.1472425207217 Content-Type: application/octet-stream; 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 - 28/08/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-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/fabric-ovirt_master_check-merged-fc23-x86_64/">fabric-ovirt_master_check-merged-fc23-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/mom_3.6_build-artifacts-el7-x86_64/">mom_3.6_build-artifacts-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/mom_3.6_build-artifacts-fc23-x86_64/">mom_3.6_build-artifacts-fc23-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/mom_4.0_build-artifacts-el7-x86_64/">mom_4.0_build-artifacts-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/mom_4.0_build-artifacts-fc23-x86_64/">mom_4.0_build-artifacts-fc23-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/mom_4.0_build-artifacts-fc24-x86_64/">mom_4.0_build-artifacts-fc24-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/mom_master_build-artifacts-el7-x86_64/">mom_master_build-artifacts-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/mom_master_build-artifacts-fc24-x86_64/">mom_master_build-artifacts-fc24-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/ovirt-live_4.0-create-iso/">ovirt-live_4.0-create-iso</a> </td><td> <h3>This job generates a nightly iso of ovirt-live 4.0</h3> Need to move to std-ci or yamlize </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_ovirt-3.6_chec…">ovirt-node-plugin-hosted-engine_ovirt-3.6_check-merged-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/ovirt-optimizer_4.0_build-artifacts-fc23-x86_6…">ovirt-optimizer_4.0_build-artifacts-fc23-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/repos_master_check-closure_merged/">repos_master_check-closure_merged</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/vdsm_4.0_build-artifacts-fc23-x86_64/">vdsm_4.0_build-artifacts-fc23-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/vdsm_master_check-merged-fc24-x86_64/">vdsm_master_check-merged-fc24-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> ------=_Part_105_1913039023.1472425207217--

1 0

[JIRA] (OVIRT-453) Gerrit: Issue 3885: Failed to index change
by Shlomo Ben David (oVirt JIRA) 28 Aug '16

28 Aug '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-453?page=com.atlassian.jira.p… ] Shlomo Ben David commented on OVIRT-453: ---------------------------------------- According to the fix that was made in gerrit v2.13 i will test it first on the test environment. > Gerrit: Issue 3885: Failed to index change > ------------------------------------------ > > Key: OVIRT-453 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-453 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > Its an open issue [1] in Gerrit, but still no fix available. > We'll track it and see if there is a pending fix, cc'ing infra-support to > open a ticket to track this. > [1] > https://code.google.com/p/gerrit/issues/detail?can=2&start=0&num=100&q=&col… > On Sun, Mar 27, 2016 at 7:03 AM, Nadav Goldin <ngoldin(a)redhat.com> wrote: > > Hi, > > gerrit started throwing weird errors this morning, such as: > > > >> internal server error: com.google.gerrit.server.git.UpdateException: > >> java.io.IOException: java.util.concurrent.ExecutionException: > >> org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed) > >> > > > > restarting it now. > > > > > > Nadav. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHEV 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.285.1#100011)

1 0