- Infra - oVirt List Archives

DAO test
by Yevgeny Zaspitsky 29 Mar '16

29 Mar '16

Hi All, I renamed NetworkAttachmentDaoTest.java to NetworkAttachmentDaoImplTest.java (note the added "Impl") and Jenkins now includes the test in the regular unit-tests run rather than running that as a dao-unit-tests job. That causes test to fail as it cannot connect ot the tests DB. Where the logic of choosing the right configuration sits? Shouldn't any dal change trigger the dao tests rather than the regular ones? Yevgeny

3 3

[JIRA] (OVIRT-459) create ovirt-system-tests feature page on ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 29 Mar '16

29 Mar '16

eyal edri [Administrator] created OVIRT-459: ----------------------------------------------- Summary: create ovirt-system-tests feature page on ovirt.org Key: OVIRT-459 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-459 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra We need to have a single page on ovirt.org to concentrate all ovirt-system-tests docs and plans per ovirt version. Ideally we'll want a test plan attached to each feature page in oVirt 4.0 to start with. [~ykaul] what do you think? -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

1 0

[JIRA] (OVIRT-458) Re: ovirt-engine-3.6.5 branch is not treated by the hooks as a stable branch
by Anton Marchukov (oVirt JIRA) 29 Mar '16

29 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-458?page=com.atlassian.jira.p… ] Anton Marchukov commented on OVIRT-458: --------------------------------------- Hello Tal. ovirt-engine-3.6.5 has been added to the stable branches. Anton. On Tue, Mar 29, 2016 at 1:01 PM, Eyal Edri <eedri(a)redhat.com> wrote: > Anton, > Can you add 3.6.5 to the hooks? > > On Tue, Mar 29, 2016 at 2:00 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > >> Taken from https://gerrit.ovirt.org/55385 - >> >> - Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6 >> ovirt-engine-3.6.0 ovirt-engine-3.6.1 ovirt-engine-3.6.2 ovirt-engine-3.5 >> ovirt-engine-3.4 ovirt-engine-3.3 engine_3.2 engine_3.1 ovirt-engine-3.5.2 >> ovirt-engine-3.4.0 ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 >> ovirt-engine-3.3.1) >> - Check merged to previous::IGNORE, Not in stable branch >> (['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.6.1', >> 'ovirt-engine-3.6.2', 'ovirt-engine-3.6.3', 'ovirt-engine-3.6.4', >> 'ovirt-engine-3.5', 'ovirt-engine-3.4', 'ovirt-engine-3.3', >> 'ovirt-engine-3.5.2', 'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', >> 'ovirt-engine-3.3.3', 'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1']) >> >> >> _______________________________________________ >> 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) > -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat > Re: ovirt-engine-3.6.5 branch is not treated by the hooks as a stable branch > ---------------------------------------------------------------------------- > > Key: OVIRT-458 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-458 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > Anton, > Can you add 3.6.5 to the hooks? > On Tue, Mar 29, 2016 at 2:00 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Taken from https://gerrit.ovirt.org/55385 - > > > > - Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6 > > ovirt-engine-3.6.0 ovirt-engine-3.6.1 ovirt-engine-3.6.2 ovirt-engine-3.5 > > ovirt-engine-3.4 ovirt-engine-3.3 engine_3.2 engine_3.1 ovirt-engine-3.5.2 > > ovirt-engine-3.4.0 ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 > > ovirt-engine-3.3.1) > > - Check merged to previous::IGNORE, Not in stable branch > > (['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.6.1', > > 'ovirt-engine-3.6.2', 'ovirt-engine-3.6.3', 'ovirt-engine-3.6.4', > > 'ovirt-engine-3.5', 'ovirt-engine-3.4', 'ovirt-engine-3.3', > > 'ovirt-engine-3.5.2', 'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', > > 'ovirt-engine-3.3.3', 'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1']) > > > > > > _______________________________________________ > > 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 (v7.2.0-OD-04-029#72002)

1 0

ovirt-engine-3.6.5 branch is not treated by the hooks as a stable branch
by Tal Nisan 29 Mar '16

29 Mar '16

Taken from https://gerrit.ovirt.org/55385 - - Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6 ovirt-engine-3.6.0 ovirt-engine-3.6.1 ovirt-engine-3.6.2 ovirt-engine-3.5 ovirt-engine-3.4 ovirt-engine-3.3 engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0 ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 ovirt-engine-3.3.1) - Check merged to previous::IGNORE, Not in stable branch (['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.6.1', 'ovirt-engine-3.6.2', 'ovirt-engine-3.6.3', 'ovirt-engine-3.6.4', 'ovirt-engine-3.5', 'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2', 'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3', 'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])

3 3

[JIRA] (OVIRT-458) Re: ovirt-engine-3.6.5 branch is not treated by the hooks as a stable branch
by eyal edri [Administrator] (oVirt JIRA) 29 Mar '16

29 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-458?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-458: ------------------------------------------------- Also, Its good if we'll have this documented in the infra docs. On Tue, Mar 29, 2016 at 2:01 PM, Eyal Edri <eedri(a)redhat.com> wrote: > Anton, > Can you add 3.6.5 to the hooks? > > On Tue, Mar 29, 2016 at 2:00 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > >> Taken from https://gerrit.ovirt.org/55385 - >> >> - Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6 >> ovirt-engine-3.6.0 ovirt-engine-3.6.1 ovirt-engine-3.6.2 ovirt-engine-3.5 >> ovirt-engine-3.4 ovirt-engine-3.3 engine_3.2 engine_3.1 ovirt-engine-3.5.2 >> ovirt-engine-3.4.0 ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 >> ovirt-engine-3.3.1) >> - Check merged to previous::IGNORE, Not in stable branch >> (['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.6.1', >> 'ovirt-engine-3.6.2', 'ovirt-engine-3.6.3', 'ovirt-engine-3.6.4', >> 'ovirt-engine-3.5', 'ovirt-engine-3.4', 'ovirt-engine-3.3', >> 'ovirt-engine-3.5.2', 'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', >> 'ovirt-engine-3.3.3', 'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1']) >> >> >> _______________________________________________ >> 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) > -- 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) > Re: ovirt-engine-3.6.5 branch is not treated by the hooks as a stable branch > ---------------------------------------------------------------------------- > > Key: OVIRT-458 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-458 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > Anton, > Can you add 3.6.5 to the hooks? > On Tue, Mar 29, 2016 at 2:00 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Taken from https://gerrit.ovirt.org/55385 - > > > > - Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6 > > ovirt-engine-3.6.0 ovirt-engine-3.6.1 ovirt-engine-3.6.2 ovirt-engine-3.5 > > ovirt-engine-3.4 ovirt-engine-3.3 engine_3.2 engine_3.1 ovirt-engine-3.5.2 > > ovirt-engine-3.4.0 ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 > > ovirt-engine-3.3.1) > > - Check merged to previous::IGNORE, Not in stable branch > > (['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.6.1', > > 'ovirt-engine-3.6.2', 'ovirt-engine-3.6.3', 'ovirt-engine-3.6.4', > > 'ovirt-engine-3.5', 'ovirt-engine-3.4', 'ovirt-engine-3.3', > > 'ovirt-engine-3.5.2', 'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', > > 'ovirt-engine-3.3.3', 'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1']) > > > > > > _______________________________________________ > > 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 (v7.2.0-OD-04-029#72002)

1 0

[JIRA] (OVIRT-458) Re: ovirt-engine-3.6.5 branch is not treated by the hooks as a stable branch
by eyal edri [Administrator] (oVirt JIRA) 29 Mar '16

29 Mar '16

eyal edri [Administrator] created OVIRT-458: ----------------------------------------------- Summary: Re: ovirt-engine-3.6.5 branch is not treated by the hooks as a stable branch Key: OVIRT-458 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-458 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra Anton, Can you add 3.6.5 to the hooks? On Tue, Mar 29, 2016 at 2:00 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > Taken from https://gerrit.ovirt.org/55385 - > > - Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6 > ovirt-engine-3.6.0 ovirt-engine-3.6.1 ovirt-engine-3.6.2 ovirt-engine-3.5 > ovirt-engine-3.4 ovirt-engine-3.3 engine_3.2 engine_3.1 ovirt-engine-3.5.2 > ovirt-engine-3.4.0 ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 > ovirt-engine-3.3.1) > - Check merged to previous::IGNORE, Not in stable branch > (['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.6.1', > 'ovirt-engine-3.6.2', 'ovirt-engine-3.6.3', 'ovirt-engine-3.6.4', > 'ovirt-engine-3.5', 'ovirt-engine-3.4', 'ovirt-engine-3.3', > 'ovirt-engine-3.5.2', 'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', > 'ovirt-engine-3.3.3', 'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1']) > > > _______________________________________________ > 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 (v7.2.0-OD-04-029#72002)

1 0

[JIRA] (OVIRT-457) Re: Change in otopi[master]: core: rewrite buildSequence using toposort
by eyal edri [Administrator] (oVirt JIRA) 29 Mar '16

29 Mar '16

eyal edri [Administrator] created OVIRT-457: ----------------------------------------------- Summary: Re: Change in otopi[master]: core: rewrite buildSequence using toposort Key: OVIRT-457 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-457 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra On Mar 28, 2016 9:44 AM, "Yedidyah Bar David" <didi(a)redhat.com> wrote: > On Mon, Mar 28, 2016 at 9:08 AM, Jenkins CI <gerrit2(a)gerrit.ovirt.org> > wrote: > > Jenkins CI has posted comments on this change. > > > > Change subject: core: rewrite buildSequence using toposort > > ...................................................................... > > > > > > Patch Set 22: Continuous-Integration-1 > > > > Build Failed > > > > http://jenkins.ovirt.org/job/otopi_master_check-patch-fc23-x86_64/23/ : > FAILURE > > This one still fails, still not sure why: > > 06:58:05 > /usr/bin/git clean -fdx # timeout=10 > 06:58:05 ERROR: Error fetching remote repo 'origin' > > > > > > http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/11… > : SUCCESS > > > > http://jenkins.ovirt.org/job/otopi_master_check-patch-el7-x86_64/25/ : > SUCCESS > > > > > http://jenkins.ovirt.org/job/otopi_master_create-rpms-fc23-x86_64_created/7… > : SUCCESS > > > > -- > > To view, visit https://gerrit.ovirt.org/28775 > > To unsubscribe, visit https://gerrit.ovirt.org/settings > > > > Gerrit-MessageType: comment > > Gerrit-Change-Id: I9a7e9a26ac68543331dc869ab151883ac8bd5b30 > > Gerrit-PatchSet: 22 > > Gerrit-Project: otopi > > Gerrit-Branch: master > > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: Jenkins CI > > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > > Gerrit-Reviewer: Rafael Martins <rmartins(a)redhat.com> > > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > > Gerrit-HasComments: No > > > > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > > -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

1 0

Re: Change in otopi[master]: core: rewrite buildSequence using toposort
by Yedidyah Bar David 29 Mar '16

29 Mar '16

On Mon, Mar 28, 2016 at 9:08 AM, Jenkins CI <gerrit2(a)gerrit.ovirt.org> wrote: > Jenkins CI has posted comments on this change. > > Change subject: core: rewrite buildSequence using toposort > ...................................................................... > > > Patch Set 22: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/otopi_master_check-patch-fc23-x86_64/23/ : FAILURE This one still fails, still not sure why: 06:58:05 > /usr/bin/git clean -fdx # timeout=10 06:58:05 ERROR: Error fetching remote repo 'origin' > > http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/11… : SUCCESS > > http://jenkins.ovirt.org/job/otopi_master_check-patch-el7-x86_64/25/ : SUCCESS > > http://jenkins.ovirt.org/job/otopi_master_create-rpms-fc23-x86_64_created/7… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/28775 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: I9a7e9a26ac68543331dc869ab151883ac8bd5b30 > Gerrit-PatchSet: 22 > Gerrit-Project: otopi > Gerrit-Branch: master > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > Gerrit-Reviewer: Rafael Martins <rmartins(a)redhat.com> > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No -- Didi

2 1

[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds
by David Caro Estevez (oVirt JIRA) 29 Mar '16

29 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-422?page=com.atlassian.jira.p… ] David Caro Estevez updated OVIRT-422: ------------------------------------- Assignee: David Caro Estevez (was: infra) Status: Accepted (was: Accepted) > Create jenkins job to compose ovirt 4.0 snaphost early builds > ------------------------------------------------------------- > > Key: OVIRT-422 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins, repoman > Reporter: eyal edri [Administrator] > Assignee: David Caro Estevez > Priority: Highest > > We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build. > * Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on > resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/ > * Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1] > * This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1 > * We'll run repoclosure on it once the copy is finished > * run sanity (either manually or via Lago manual if possible) > * rhevh team run sanity on the node builds from nightly > * Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link. > * Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg. > * Send email to users/devel with info on release (list of bugs + link to release rpm). > [2] cat ovirt-4.0-snapshots.repoman (the conf file) > rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest > rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

1 0

[JIRA] (OVIRT-455) puppetdb ran out of memory
by Nadav Goldin (oVirt JIRA) 29 Mar '16

29 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-455?page=com.atlassian.jira.p… ] Nadav Goldin reassigned OVIRT-455: ---------------------------------- Assignee: Nadav Goldin (was: infra) Component/s: Puppet Foreman Issue Type: Bug (was: By-EMAIL) Summary: puppetdb ran out of memory (was: Fwd: ** RECOVERY Service Alert: foreman/PuppetDB Service is OK **) > puppetdb ran out of memory > -------------------------- > > Key: OVIRT-455 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-455 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Foreman, Puppet > Reporter: Nadav Goldin > Assignee: Nadav Goldin > > puppetdb ran out of memory during the night and crashed, causing all puppet > agents to fail. > I've increased the java heap size as recommended[1] to 228mb in > /etc/sysoconfig/puppetdb. > opening a ticket for tracking. > [1] https://docs.puppetlabs.com/puppetdb/latest/scaling_recommendations.html > --------- Forwarded message ---------- > From: icinga <icinga(a)monitoring.ovirt.org> > Date: Tue, Mar 29, 2016 at 9:12 AM > Subject: ** RECOVERY Service Alert: foreman/PuppetDB Service is OK ** > To: ngoldin(a)redhat.com > ***** Icinga ***** > Notification Type: RECOVERY > Service: PuppetDB Service > Host: foreman > Address: 31.15.26.1 > State: OK > Date/Time: Tue Mar 29 06:12:37 UTC 2016 > Additional Info: > OK: 1 processes -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002)

1 0