- Infra - oVirt List Archives

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I6de3b482ceb9772144ff53443743c4fbee7d8132 --- M automation/upstream_sources.yaml 1 file changed, 2 insertions(+), 2 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/25 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I6de3b482ceb9772144ff53443743c4fbee7d8132 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in us-jenkins-stg2[master]: Added b and d
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Added b and d ...................................................................... Added b and d Change-Id: If33c0f1feab9339cb404e22bd3487f0b05a51229 --- A b A d 2 files changed, 2 insertions(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/24 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: If33c0f1feab9339cb404e22bd3487f0b05a51229 Gerrit-PatchSet: 1 Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in us-jenkins-stg2[master]: Added b and d
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: Added b and d ...................................................................... Patch Set 1: Code-Review+2 Continuous-Integration+1 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/24 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: If33c0f1feab9339cb404e22bd3487f0b05a51229 Gerrit-PatchSet: 1 Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in us-jenkins-stg1[master]: added c
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: added c ...................................................................... added c Change-Id: I092638df1053ea92e813bc70ccfef2a3c50c638a --- A c 1 file changed, 1 insertion(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/23 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I092638df1053ea92e813bc70ccfef2a3c50c638a Gerrit-PatchSet: 1 Gerrit-Project: us-jenkins-stg1 Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in us-jenkins-stg1[master]: added c
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: added c ...................................................................... Patch Set 1: Code-Review+2 Continuous-Integration+1 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/23 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I092638df1053ea92e813bc70ccfef2a3c50c638a Gerrit-PatchSet: 1 Gerrit-Project: us-jenkins-stg1 Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I2ea3a724443e20153e62034f6218bcd95e6d10d5 --- A b 1 file changed, 1 insertion(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/22 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I2ea3a724443e20153e62034f6218bcd95e6d10d5 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I51d2d62d5a249e6730f14109951da2d151b086b9 --- A a 1 file changed, 1 insertion(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/21 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I51d2d62d5a249e6730f14109951da2d151b086b9 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I36512c85260781e0da1f1a50719a092cc07e012f --- A automation/poll-upstream-sources.sh 1 file changed, 3 insertions(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/20 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I36512c85260781e0da1f1a50719a092cc07e012f Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Initializing repo
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Initializing repo ...................................................................... Initializing repo Change-Id: I3585b757492f82ccae48dab666cccee8b5da6afe --- A automation/upstream_sources.yaml 1 file changed, 8 insertions(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/19 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I3585b757492f82ccae48dab666cccee8b5da6afe Gerrit-PatchSet: 1 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Initializing repo
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: Initializing repo ...................................................................... Patch Set 1: Continuous-Integration+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/19 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I3585b757492f82ccae48dab666cccee8b5da6afe Gerrit-PatchSet: 1 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in ds-jenkins-stg[master]: Initializing repo
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: Initializing repo ...................................................................... Patch Set 1: Code-Review+2 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/19 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I3585b757492f82ccae48dab666cccee8b5da6afe Gerrit-PatchSet: 1 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-1381) Re: Findbugs issues not reported correctly on Jenkins master jobs?
by Daniel Belenky (oVirt JIRA) 18 May '17

18 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1381?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1381: ---------------------------------- Status: In Progress (was: To Do) > Re: Findbugs issues not reported correctly on Jenkins master jobs? > ------------------------------------------------------------------ > > Key: OVIRT-1381 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1381 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Daniel Belenky > > Adding infra-support > On Mon, May 15, 2017 at 3:55 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Just a regular "mvn findbugs:findbugs" run on master, you can revert this > > patch and run it manually yourself: https://gerrit.ovirt.org/#/c/76820/ > > > > On Mon, May 15, 2017 at 2:15 PM, Daniel Belenky <dbelenky(a)redhat.com> > > wrote: > > > >> Hi Tal, > >> I'm checking this right now. > >> Can you provide the log from your local run? which files were exported on > >> your local run? > >> > >> On Mon, May 15, 2017 at 11:51 AM Tal Nisan <tnisan(a)redhat.com> wrote: > >> > >>> I've pushed this patch to master: > >>> https://gerrit.ovirt.org/#/c/75994/ > >>> Jenkins showed no findbugs error and I moved on to merging it > >>> > >>> Then I've pushed the same patch to 4.1: > >>> https://gerrit.ovirt.org/#/c/76803/ > >>> And it resulted in two findbugs errors (though minor and style related): > >>> http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_crea > >>> ted/898/findbugsResult/new/ > >>> > >>> Running findbugs manually in my environment on master did report these > >>> two issues so I'd expect the master jobs to report them as well. > >>> > >>> _______________________________________________ > >>> Infra mailing list > >>> Infra(a)ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/infra > >>> > >> -- > >> > >> DANIEL BELENKY > >> > >> RHV DEVOPS > >> > >> Red Hat EMEA <https://www.redhat.com/> > >> > >> IRC: #rhev-integ #rhev-dev > >> <https://red.ht/sig> > >> > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1381) Re: Findbugs issues not reported correctly on Jenkins master jobs?
by Tal Nisan (oVirt JIRA) 18 May '17

18 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1381?page=com.atlassian.jira.… ] Tal Nisan commented on OVIRT-1381: ---------------------------------- mvn findbugs:findbugs, it generates the report On Thu, May 18, 2017 at 2:45 PM, Daniel Belenky (oVirt JIRA) < > Re: Findbugs issues not reported correctly on Jenkins master jobs? > ------------------------------------------------------------------ > > Key: OVIRT-1381 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1381 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Daniel Belenky > > Adding infra-support > On Mon, May 15, 2017 at 3:55 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Just a regular "mvn findbugs:findbugs" run on master, you can revert this > > patch and run it manually yourself: https://gerrit.ovirt.org/#/c/76820/ > > > > On Mon, May 15, 2017 at 2:15 PM, Daniel Belenky <dbelenky(a)redhat.com> > > wrote: > > > >> Hi Tal, > >> I'm checking this right now. > >> Can you provide the log from your local run? which files were exported on > >> your local run? > >> > >> On Mon, May 15, 2017 at 11:51 AM Tal Nisan <tnisan(a)redhat.com> wrote: > >> > >>> I've pushed this patch to master: > >>> https://gerrit.ovirt.org/#/c/75994/ > >>> Jenkins showed no findbugs error and I moved on to merging it > >>> > >>> Then I've pushed the same patch to 4.1: > >>> https://gerrit.ovirt.org/#/c/76803/ > >>> And it resulted in two findbugs errors (though minor and style related): > >>> http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_crea > >>> ted/898/findbugsResult/new/ > >>> > >>> Running findbugs manually in my environment on master did report these > >>> two issues so I'd expect the master jobs to report them as well. > >>> > >>> _______________________________________________ > >>> Infra mailing list > >>> Infra(a)ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/infra > >>> > >> -- > >> > >> DANIEL BELENKY > >> > >> RHV DEVOPS > >> > >> Red Hat EMEA <https://www.redhat.com/> > >> > >> IRC: #rhev-integ #rhev-dev > >> <https://red.ht/sig> > >> > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1381) Re: Findbugs issues not reported correctly on Jenkins master jobs?
by Daniel Belenky (oVirt JIRA) 18 May '17

18 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1381?page=com.atlassian.jira.… ] Daniel Belenky edited comment on OVIRT-1381 at 5/18/17 2:45 PM: ---------------------------------------------------------------- I've checked the output files digested by the findbugs plugin in Jenkins with the assistance from [~rgolan(a)redhat.com] and it seems that all the findbugs.xml files are present. [~tnisan(a)redhat.com] can you provide the command you've used locally? was (Author: dbelenky(a)redhat.com) I've check the output files digested by the findbugs plugin in Jenkins with the assistance from [~rgolan(a)redhat.com] [~tnisan(a)redhat.com] can you provide the command you've used locally? > Re: Findbugs issues not reported correctly on Jenkins master jobs? > ------------------------------------------------------------------ > > Key: OVIRT-1381 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1381 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Daniel Belenky > > Adding infra-support > On Mon, May 15, 2017 at 3:55 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Just a regular "mvn findbugs:findbugs" run on master, you can revert this > > patch and run it manually yourself: https://gerrit.ovirt.org/#/c/76820/ > > > > On Mon, May 15, 2017 at 2:15 PM, Daniel Belenky <dbelenky(a)redhat.com> > > wrote: > > > >> Hi Tal, > >> I'm checking this right now. > >> Can you provide the log from your local run? which files were exported on > >> your local run? > >> > >> On Mon, May 15, 2017 at 11:51 AM Tal Nisan <tnisan(a)redhat.com> wrote: > >> > >>> I've pushed this patch to master: > >>> https://gerrit.ovirt.org/#/c/75994/ > >>> Jenkins showed no findbugs error and I moved on to merging it > >>> > >>> Then I've pushed the same patch to 4.1: > >>> https://gerrit.ovirt.org/#/c/76803/ > >>> And it resulted in two findbugs errors (though minor and style related): > >>> http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_crea > >>> ted/898/findbugsResult/new/ > >>> > >>> Running findbugs manually in my environment on master did report these > >>> two issues so I'd expect the master jobs to report them as well. > >>> > >>> _______________________________________________ > >>> Infra mailing list > >>> Infra(a)ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/infra > >>> > >> -- > >> > >> DANIEL BELENKY > >> > >> RHV DEVOPS > >> > >> Red Hat EMEA <https://www.redhat.com/> > >> > >> IRC: #rhev-integ #rhev-dev > >> <https://red.ht/sig> > >> > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1381) Re: Findbugs issues not reported correctly on Jenkins master jobs?
by Daniel Belenky (oVirt JIRA) 18 May '17

18 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1381?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1381: --------------------------------------- I've check the output files digested by the findbugs plugin in Jenkins with the assistance from [~rgolan(a)redhat.com] [~tnisan(a)redhat.com] can you provide the command you've used locally? > Re: Findbugs issues not reported correctly on Jenkins master jobs? > ------------------------------------------------------------------ > > Key: OVIRT-1381 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1381 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Daniel Belenky > > Adding infra-support > On Mon, May 15, 2017 at 3:55 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Just a regular "mvn findbugs:findbugs" run on master, you can revert this > > patch and run it manually yourself: https://gerrit.ovirt.org/#/c/76820/ > > > > On Mon, May 15, 2017 at 2:15 PM, Daniel Belenky <dbelenky(a)redhat.com> > > wrote: > > > >> Hi Tal, > >> I'm checking this right now. > >> Can you provide the log from your local run? which files were exported on > >> your local run? > >> > >> On Mon, May 15, 2017 at 11:51 AM Tal Nisan <tnisan(a)redhat.com> wrote: > >> > >>> I've pushed this patch to master: > >>> https://gerrit.ovirt.org/#/c/75994/ > >>> Jenkins showed no findbugs error and I moved on to merging it > >>> > >>> Then I've pushed the same patch to 4.1: > >>> https://gerrit.ovirt.org/#/c/76803/ > >>> And it resulted in two findbugs errors (though minor and style related): > >>> http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_crea > >>> ted/898/findbugsResult/new/ > >>> > >>> Running findbugs manually in my environment on master did report these > >>> two issues so I'd expect the master jobs to report them as well. > >>> > >>> _______________________________________________ > >>> Infra mailing list > >>> Infra(a)ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/infra > >>> > >> -- > >> > >> DANIEL BELENKY > >> > >> RHV DEVOPS > >> > >> Red Hat EMEA <https://www.redhat.com/> > >> > >> IRC: #rhev-integ #rhev-dev > >> <https://red.ht/sig> > >> > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1381) Re: Findbugs issues not reported correctly on Jenkins master jobs?
by Daniel Belenky (oVirt JIRA) 18 May '17

18 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1381?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1381: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Re: Findbugs issues not reported correctly on Jenkins master jobs? > ------------------------------------------------------------------ > > Key: OVIRT-1381 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1381 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Daniel Belenky > > Adding infra-support > On Mon, May 15, 2017 at 3:55 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Just a regular "mvn findbugs:findbugs" run on master, you can revert this > > patch and run it manually yourself: https://gerrit.ovirt.org/#/c/76820/ > > > > On Mon, May 15, 2017 at 2:15 PM, Daniel Belenky <dbelenky(a)redhat.com> > > wrote: > > > >> Hi Tal, > >> I'm checking this right now. > >> Can you provide the log from your local run? which files were exported on > >> your local run? > >> > >> On Mon, May 15, 2017 at 11:51 AM Tal Nisan <tnisan(a)redhat.com> wrote: > >> > >>> I've pushed this patch to master: > >>> https://gerrit.ovirt.org/#/c/75994/ > >>> Jenkins showed no findbugs error and I moved on to merging it > >>> > >>> Then I've pushed the same patch to 4.1: > >>> https://gerrit.ovirt.org/#/c/76803/ > >>> And it resulted in two findbugs errors (though minor and style related): > >>> http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_crea > >>> ted/898/findbugsResult/new/ > >>> > >>> Running findbugs manually in my environment on master did report these > >>> two issues so I'd expect the master jobs to report them as well. > >>> > >>> _______________________________________________ > >>> Infra mailing list > >>> Infra(a)ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/infra > >>> > >> -- > >> > >> DANIEL BELENKY > >> > >> RHV DEVOPS > >> > >> Red Hat EMEA <https://www.redhat.com/> > >> > >> IRC: #rhev-integ #rhev-dev > >> <https://red.ht/sig> > >> > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

Fwd: UPDATE: Bugzilla 5 beta server is back online
by Sandro Bonazzola 18 May '17

18 May '17

---------- Forwarded message ---------- From: Christine Freitas <cfreitas(a)redhat.com> Date: Mon, May 15, 2017 at 6:03 PM Subject: UPDATE: Bugzilla 5 beta server is back online Hello All, The Bugzilla 5 beta server [1] is back online. We encourage you to test your current scripts and take part in the beta discussions on the Fedora development list [2]. Partners and customers may also use their existing communications channels to share feedback or questions. We've extended the beta window and ask that you provide feedback or questions by Wednesday, June 14th. The official release date for Bugzilla 5 will be determined based on the beta feedback. We will communicate to you as the beta continues to progress. For more information refer to: https://beta-bugzilla.redhat.com/page.cgi?id=whats-new.html https://beta-bugzilla.redhat.com/page.cgi?id=release-notes.html https://beta-bugzilla.redhat.com/page.cgi?id=faq.html https://beta-bugzilla.redhat.com/docs/en/html/using/index.html https://beta-bugzilla.redhat.com/docs/en/html/api/index.html Cheers, the Red Hat Bugzilla team. 1: https://beta-bugzilla.redhat.com/ 2: https://lists.fedoraproject.org/archives/list/devel%40lists. fedoraproject.org/ -- 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>

1 0

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

17 May '17

------=_Part_28_917056408.1495062007393 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/325//artifact/exported-a… Cheers, Jenkins ------=_Part_28_917056408.1495062007393 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 - 17/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_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_28_917056408.1495062007393--

1 0

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

17 May '17

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

1 1

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

17 May '17

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

1 1

[JIRA] (OVIRT-1386) grant me with permissions in both staging Jenkins and Gerrit
by Gil Shinar (oVirt JIRA) 17 May '17

17 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1386?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1386: --------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > grant me with permissions in both staging Jenkins and Gerrit > ------------------------------------------------------------ > > Key: OVIRT-1386 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1386 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Evgheni Dereveanchin > > Please grant me with permissions to the staging Jenkins gshinar(a)redhat.com > and to the staging Gerrit -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1386) grant me with permissions in both staging Jenkins and Gerrit
by Gil Shinar (oVirt JIRA) 17 May '17

17 May '17

Gil Shinar created OVIRT-1386: --------------------------------- Summary: grant me with permissions in both staging Jenkins and Gerrit Key: OVIRT-1386 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1386 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra Please grant me with permissions to the staging Jenkins gshinar(a)redhat.com and to the staging Gerrit -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

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

16 May '17

------=_Part_4_1910983634.1494975603620 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/324//artifact/exported-a… Cheers, Jenkins ------=_Part_4_1910983634.1494975603620 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 - 16/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_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_4_1910983634.1494975603620--

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1385: -------------------------------- Labels: mock_runner.sh (was: ) > 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: Jenkins > 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.967.1#100042)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1385: -------------------------------- Component/s: Jenkins > 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: Jenkins > Reporter: Vojtech Szocs > Assignee: infra > Priority: Low > > 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.967.1#100042)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1385: -------------------------------- Priority: Low (was: Medium) > 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 > Reporter: Vojtech Szocs > Assignee: infra > Priority: Low > > 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.967.1#100042)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1385: ------------------------------------- The runtime different between cache-using mock runs and non-cache using ones is more then a minute, so playing with the caching intervals would be I'll advised. Making this configurable would not be trivial at all. I suppose the {{*.packages}} file format can be extended to allow requesting certain versions or forcing updates. Such changes will need to go into the {{mock_runner.sh}} code. There had been similar requests made in the past (Can't locate the relevant tickets right now). I'm afraid I cannot prioritize this ticket very highly though. We are a bit reluctant to add any new features to {{mock_runner.sh}} for the time being. Patches will be welcome though.... > 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 > Reporter: Vojtech Szocs > Assignee: infra > > 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.967.1#100042)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1385: -------------------------------- Issue Type: Improvement (was: By-EMAIL) > 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 > Reporter: Vojtech Szocs > Assignee: infra > > 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.967.1#100042)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Vojtech Szocs (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] Vojtech Szocs updated OVIRT-1385: --------------------------------- Description: 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. was: There are multiple oVirt projects [1] which contain a `build.packages.force` (or similar) file, along with the following code in their build script: # 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} [1] 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 configurable per-project. Not sure what's the best approach here, please advise. > 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: By-EMAIL > Reporter: Vojtech Szocs > Assignee: infra > > 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.967.1#100042)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Vojtech Szocs (oVirt JIRA) 16 May '17

16 May '17

Vojtech Szocs created OVIRT-1385: ------------------------------------ Summary: 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: By-EMAIL Reporter: Vojtech Szocs Assignee: infra There are multiple oVirt projects [1] which contain a `build.packages.force` (or similar) file, along with the following code in their build script: # 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} [1] 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 configurable per-project. Not sure what's the best approach here, please advise. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1384) replace faulty hardware on PHX storage02
by Evgheni Dereveanchin (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1384?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1384: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > replace faulty hardware on PHX storage02 > ---------------------------------------- > > Key: OVIRT-1384 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1384 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > ovirt-storage02 crashed a few months ago and Dell recommends replacing the motherboard and CPU which falls under warranty. For this we need to move workloads to ovirt-storage01 and shut down the faulty server. Then Dell's technicians can come on site to perform replacement. > Motherboard replacement will cause MAC address changes of the NICs and may affect the RAID. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1384) replace faulty hardware on PHX storage02
by Evgheni Dereveanchin (oVirt JIRA) 16 May '17

16 May '17

Evgheni Dereveanchin created OVIRT-1384: ------------------------------------------- Summary: replace faulty hardware on PHX storage02 Key: OVIRT-1384 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1384 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra ovirt-storage02 crashed a few months ago and Dell recommends replacing the motherboard and CPU which falls under warranty. For this we need to move workloads to ovirt-storage01 and shut down the faulty server. Then Dell's technicians can come on site to perform replacement. Motherboard replacement will cause MAC address changes of the NICs and may affect the RAID. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1383) Create Jenkisn+Python talk for PyCon
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1383?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1383: ----------------------------------- Assignee: Barak Korren (was: infra) > Create Jenkisn+Python talk for PyCon > ------------------------------------ > > Key: OVIRT-1383 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1383 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > My proposal was accepted, now need to make a presentation and prepare for it. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1383) Create Jenkisn+Python talk for PyCon
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

Barak Korren created OVIRT-1383: ----------------------------------- Summary: Create Jenkisn+Python talk for PyCon Key: OVIRT-1383 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1383 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Barak Korren Assignee: infra Priority: Highest My proposal was accepted, now need to make a presentation and prepare for it. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

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

16 May '17

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

1 1

[JIRA] (OVIRT-1382) Failing vdsm_master_build_artifacts-el7-ppc64 on check-merge
by Gil Shinar (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1382?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1382: --------------------------------- Assignee: Gil Shinar (was: infra) > Failing vdsm_master_build_artifacts-el7-ppc64 on check-merge > ------------------------------------------------------------ > > Key: OVIRT-1382 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1382 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: Gil Shinar > > Following https://gerrit.ovirt.org/76781 merge, the following build failed: > http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/1737/ > Is this a known issue? > Thanks, > Edy. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1382) Failing vdsm_master_build_artifacts-el7-ppc64 on check-merge
by Gil Shinar (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1382?page=com.atlassian.jira.… ] Gil Shinar commented on OVIRT-1382: ----------------------------------- FYI [~danken(a)redhat.com] [~nsoffer(a)redhat.com] [~eedri(a)redaht.com] There's an issue with non X86* platforms and ssh-agent. VDSM jobs that are running on PPC64 archs are failing. [~ederevea] Please upgrade ssh-agent plugin to at least 1.14 (you can also upgrade to the latest 1.15) ASAP > Failing vdsm_master_build_artifacts-el7-ppc64 on check-merge > ------------------------------------------------------------ > > Key: OVIRT-1382 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1382 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: infra > > Following https://gerrit.ovirt.org/76781 merge, the following build failed: > http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/1737/ > Is this a known issue? > Thanks, > Edy. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1382) Failing vdsm_master_build_artifacts-el7-ppc64 on check-merge
by Edward Haas (oVirt JIRA) 16 May '17

16 May '17

Edward Haas created OVIRT-1382: ---------------------------------- Summary: Failing vdsm_master_build_artifacts-el7-ppc64 on check-merge Key: OVIRT-1382 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1382 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: infra Following https://gerrit.ovirt.org/76781 merge, the following build failed: http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/1737/ Is this a known issue? Thanks, Edy. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[oVirt Jenkins] ovirt_master_hc-system-tests - Build # 97 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 May '17

15 May '17

------=_Part_320_400161136.1494647961953 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/97/ Build Number: 97 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #97 [Barak Korren] Fix local repo handling in mock env [Eyal Edri] add build-on-demand jobs to python-sdk ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: status: 409 reason: Conflict detail: Cannot add Host. There is no available server in the cluster to probe the new server. -------------------- >> begin captured logging << -------------------- lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 142, in _add_host return api.hosts.add(p) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 18306, in add headers={"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add return self.request('POST', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: status: 409 reason: Conflict detail: Cannot add Host. There is no available server in the cluster to probe the new server. lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 142, in _add_host return api.hosts.add(p) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 18306, in add headers={"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add return self.request('POST', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: status: 409 reason: Conflict detail: Cannot add Host. There is no available server in the cluster to probe the new server. --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 161, in add_hosts nt.assert_true(all(vt.join_all())) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 142, in _add_host return api.hosts.add(p) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 18306, in add headers={"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add return self.request('POST', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) status: 409 reason: Conflict detail: Cannot add Host. There is no available server in the cluster to probe the new server. -------------------- >> begin captured logging << -------------------- lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 142, in _add_host return api.hosts.add(p) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 18306, in add headers={"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add return self.request('POST', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: status: 409 reason: Conflict detail: Cannot add Host. There is no available server in the cluster to probe the new server. lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 142, in _add_host return api.hosts.add(p) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 18306, in add headers={"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add return self.request('POST', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: status: 409 reason: Conflict detail: Cannot add Host. There is no available server in the cluster to probe the new server. --------------------- >> end captured logging << --------------------- ------=_Part_320_400161136.1494647961953--

1 3

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #411
by jenkins＠jenkins.phx.ovirt.org 15 May '17

15 May '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/hudson5141561752913654367.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 112, in retrieveAllMD repo._revertOldRepoXML() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1323, in _revertOldRepoXML os.rename(old_data['old_local'], old_data['local']) OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

1 1

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

15 May '17

------=_Part_354_466055397.1494889210564 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/323//artifact/exported-a… Cheers, Jenkins ------=_Part_354_466055397.1494889210564 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 - 15/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_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> <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> ------=_Part_354_466055397.1494889210564--

1 0

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

15 May '17

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

1 1

[JIRA] (OVIRT-1380) Have no privileges to +2 patches
by Shlomo Ben David (oVirt JIRA) 15 May '17

15 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1380?page=com.atlassian.jira.… ] Shlomo Ben David reassigned OVIRT-1380: --------------------------------------- Assignee: Shlomo Ben David (was: infra) > Have no privileges to +2 patches > -------------------------------- > > Key: OVIRT-1380 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1380 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eli Mesika > Assignee: Shlomo Ben David > > Hi > I had problems with my Yahoo ID singing in and switched to my Google ID ( > elimesika(a)gmail.com) > However, I need +2 privileges for upstream patches > Thanks -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

[JIRA] (OVIRT-1381) Re: Findbugs issues not reported correctly on Jenkins master jobs?
by Gil Shinar (oVirt JIRA) 15 May '17

15 May '17

Gil Shinar created OVIRT-1381: --------------------------------- Summary: Re: Findbugs issues not reported correctly on Jenkins master jobs? Key: OVIRT-1381 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1381 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Gil Shinar Assignee: infra Adding infra-support On Mon, May 15, 2017 at 3:55 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > Just a regular "mvn findbugs:findbugs" run on master, you can revert this > patch and run it manually yourself: https://gerrit.ovirt.org/#/c/76820/ > > On Mon, May 15, 2017 at 2:15 PM, Daniel Belenky <dbelenky(a)redhat.com> > wrote: > >> Hi Tal, >> I'm checking this right now. >> Can you provide the log from your local run? which files were exported on >> your local run? >> >> On Mon, May 15, 2017 at 11:51 AM Tal Nisan <tnisan(a)redhat.com> wrote: >> >>> I've pushed this patch to master: >>> https://gerrit.ovirt.org/#/c/75994/ >>> Jenkins showed no findbugs error and I moved on to merging it >>> >>> Then I've pushed the same patch to 4.1: >>> https://gerrit.ovirt.org/#/c/76803/ >>> And it resulted in two findbugs errors (though minor and style related): >>> http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_crea >>> ted/898/findbugsResult/new/ >>> >>> Running findbugs manually in my environment on master did report these >>> two issues so I'd expect the master jobs to report them as well. >>> >>> _______________________________________________ >>> Infra mailing list >>> Infra(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/infra >>> >> -- >> >> DANIEL BELENKY >> >> RHV DEVOPS >> >> Red Hat EMEA <https://www.redhat.com/> >> >> IRC: #rhev-integ #rhev-dev >> <https://red.ht/sig> >> > > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

Findbugs issues not reported correctly on Jenkins master jobs?
by Tal Nisan 15 May '17

15 May '17

I've pushed this patch to master: https://gerrit.ovirt.org/#/c/75994/ Jenkins showed no findbugs error and I moved on to merging it Then I've pushed the same patch to 4.1: https://gerrit.ovirt.org/#/c/76803/ And it resulted in two findbugs errors (though minor and style related): http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_created/898/findbug… Running findbugs manually in my environment on master did report these two issues so I'd expect the master jobs to report them as well.

3 3

[JIRA] (OVIRT-1380) Have no privileges to +2 patches
by eyal edri [Administrator] (oVirt JIRA) 15 May '17

15 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1380?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1380: -------------------------------------------------- Hi Eli, Can you give more info, which project are you referring to and which branch? Thanks, On Mon, May 15, 2017 at 11:56 AM, Eli Mesika (oVirt JIRA) < -- 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) > Have no privileges to +2 patches > -------------------------------- > > Key: OVIRT-1380 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1380 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eli Mesika > Assignee: infra > > Hi > I had problems with my Yahoo ID singing in and switched to my Google ID ( > elimesika(a)gmail.com) > However, I need +2 privileges for upstream patches > Thanks -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

[JIRA] (OVIRT-1380) Have no privileges to +2 patches
by Eli Mesika (oVirt JIRA) 15 May '17

15 May '17

Eli Mesika created OVIRT-1380: --------------------------------- Summary: Have no privileges to +2 patches Key: OVIRT-1380 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1380 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Eli Mesika Assignee: infra Hi I had problems with my Yahoo ID singing in and switched to my Google ID ( elimesika(a)gmail.com) However, I need +2 privileges for upstream patches Thanks -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

2 1

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

15 May '17

------=_Part_347_2007666877.1494838487321 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/1147/ Build Name: 1147 vdsm (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/76750 - title: tests: Add tests for logged methods - project: vdsm - branch: master - author: Nir Soffer <nsoffer(a)redhat.com> ------=_Part_347_2007666877.1494838487321--

1 0

[JIRA] (OVIRT-1379) Re: Building ovirt-imageio for rawhide
by Barak Korren (oVirt JIRA) 15 May '17

15 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1379?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1379: ------------------------------------- [~nsoffer(a)redhat.com] [~sbonazzo(a)redhat.com] lets move this here. > Re: Building ovirt-imageio for rawhide > -------------------------------------- > > 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.962.0#100041)

1 0

[JIRA] (OVIRT-1379) Re: Building ovirt-imageio for rawhide
by Barak Korren (oVirt JIRA) 15 May '17

15 May '17

Barak Korren created OVIRT-1379: ----------------------------------- Summary: Re: Building ovirt-imageio for rawhide 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.962.0#100041)

1 0