May 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-476) migrate puppet infra jobs to standard ci
by eyal edri [Administrator] (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-476?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-476: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > migrate puppet infra jobs to standard ci > ---------------------------------------- > > Key: OVIRT-476 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-476 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins, Puppet > Reporter: Nadav Goldin > Assignee: Daniel Belenky > > * existing(none-yamlized) jobs: > http://jenkins.ovirt.org/job/system_update_puppet/ > http://jenkins.ovirt.org/job/infra-puppet_production_check-puppet-manifests… > * add puppet parser validate check -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

[JIRA] (OVIRT-1296) review Rebase Always submit strategy on Gerrit
by eyal edri [Administrator] (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1296?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1296: --------------------------------------------- Blocked By: pending on gerrit version 2.14 Status: Blocked (was: To Do) > review Rebase Always submit strategy on Gerrit > ---------------------------------------------- > > Key: OVIRT-1296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1296 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Lowest > > A new submit strategy was included in recent builds of Gerrit: Rebase Always. > [Docs|https://gerrit-review.googlesource.com/Documentation/project-configura…] > {quote}Basically, the same as Rebase If Necessary, but it creates a new patchset even if fast forward is possible AND like Cherry Pick it ensures footers such as Change-Id, Reviewed-On, and others are present in resulting commit that is merged. > Thus, Rebase Always can be considered similar to Cherry Pick, but with the important distinction that Rebase Always does not ignore dependencies.{quote} > It is only available in [2.14|https://gerrit.googlesource.com/gerrit/+/stable-2.14/gerrit-server/src…] while we are still at 2.12 and [2.13|https://gerrit.googlesource.com/gerrit/+/stable-2.13/gerrit-server/src…] is the current stable branch. -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

[JIRA] (OVIRT-1311) Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty
by eyal edri [Administrator] (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1311?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1311: -------------------------------------------------- Does this also related to the new way we create snapshot repos or for the old one? > Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty > --------------------------------------------------------------------------------------- > > Key: OVIRT-1311 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1311 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > If The '{{*.ready}}' directory does not contain any RPMs, the cron job fails. This failure causes all repos not to get published until the failure is fixed. -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

[JIRA] (OVIRT-1340) Fwd: whitelist request
by eyal edri [Administrator] (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1340?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1340: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Fwd: whitelist request > ---------------------- > > Key: OVIRT-1340 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1340 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > ---------- Messaggio inoltrato ---------- > Da: "Aleksei Slaikovskii" <aslaikov(a)redhat.com> > Data: 07/Apr/2017 15:01 > Oggetto: whitelist request > A: <infra(a)ovirt.org> > Cc: > Hi! > Could you please add me to whitelist, I need to run CI on this patch > https://gerrit.ovirt.org/#/c/75309/ > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

[JIRA] (OVIRT-1313) Make OST manual job build history more useful
by eyal edri [Administrator] (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1313?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1313: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > Make OST manual job build history more useful > --------------------------------------------- > > Key: OVIRT-1313 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1313 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Daniel Belenky > Priority: Low > Labels: ost > > Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run. > We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used. > We can also consider adding the name of the person that ran the job. -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

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

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1239?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1239: -------------------------------------------------- We don't need for now, since we use the infra bot for both Lago and oVirt projects. Will keep this on backlog to follow on github RFE > 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.929.1#100040)

1 0

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

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1239?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1239: --------------------------------------------- Priority: Lowest (was: Medium) > 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.929.1#100040)

1 0

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

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1239?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1239: --------------------------------------------- Status: To Do (was: Blocked) > 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 > > 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.929.1#100040)

1 0

[JIRA] (OVIRT-1351) lago-devel isn't archiving since Jan 2017
by eyal edri [Administrator] (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1351?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1351: ------------------------------------------------ Assignee: Marc Dequènes (Duck) (was: infra) Duck, can you please check? > lago-devel isn't archiving since Jan 2017 > ----------------------------------------- > > Key: OVIRT-1351 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1351 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: Marc Dequènes (Duck) > > Seems like the list stopped archiving around Jan. > Can we check and enable it back? -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0

[JIRA] (OVIRT-1342) Re: Java exception when pushing changes to Gerrit
by eyal edri [Administrator] (oVirt JIRA) 01 May '17

01 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1342?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1342: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) Merged 4 accounts into the main one: account_id | full_name | preferred_email | registered_on | inactive | ex_ids | changes | comments -----------+------------+------------------+----------------------------+----------+--------+---------+--------- 1000060 | Yaniv Kaul | ykaul(a)redhat.com | 2011-11-08 10:55:57.759-05 | N | 7 | 124 | 1148 1001031 | Yaniv Kaul | NULL | 2015-09-02 08:24:26.023-04 | Y | 0 | 0 | 0 1001032 | Yaniv Kaul | NULL | 2015-09-02 08:26:38.841-04 | Y | 0 | 0 | 6 1001510 | Yaniv Kaul | NULL | 2017-04-13 05:40:56.337-04 | Y | 0 | 0 | 0 Should be resolved now. Please report if you have any issues > Re: Java exception when pushing changes to Gerrit > ------------------------------------------------- > > Key: OVIRT-1342 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1342 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > > Adding infra-support to open a ticket as well. > On Wed, Apr 19, 2017 at 1:42 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: > > [ykaul@ykaul ovirt-system-tests]$ git review -r origin master > > remote: Processing changes: refs: 2, done > > To ssh://gerrit.ovirt.org:29418/ovirt-system-tests.git > > ! [remote rejected] HEAD -> refs/publish/master (internal server error: > > java.lang.IllegalArgumentException: expected one element but was: > > <1000060, 1001032>) > > error: failed to push some refs to 'ssh://ykaul@gerrit.ovirt.org: > > 29418/ovirt-system-tests.git' > > > > > > It does seem to be pushed, though. Any ideas? > > Y. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > 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) -- This message was sent by Atlassian JIRA (v1000.929.1#100040)

1 0