- Infra - oVirt List Archives

[JIRA] (OVIRT-1173) Please use git shallow clone as jobs default
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1173?page=com.atlassian.jira.… ] eedri updated OVIRT-1173: ------------------------- Issue Type: New Feature (was: By-EMAIL) > Please use git shallow clone as jobs default > -------------------------------------------- > > Key: OVIRT-1173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: rgolan(a)redhat.com > Assignee: infra > Labels: standard-ci > > Most if not all the git clone of the jobs don't need history at all. > For ovirt-engine I see it downloading *11Mb* using --depth 1 vs. *157Mb* > for regular clone. > R -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1198) Job times out on: 'Removing the used loop devices' on the initial clean up stage
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1198?page=com.atlassian.jira.… ] eedri commented on OVIRT-1198: ------------------------------ [~ngoldin(a)redhat.com] have you seen it again since? > Job times out on: 'Removing the used loop devices' on the initial clean up stage > -------------------------------------------------------------------------------- > > Key: OVIRT-1198 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1198 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: ngoldin(a)redhat.com > Assignee: infra > > 15:44:38 Making sure there are no device mappings... > 15:44:38 Removing the used loop devices... > 21:44:37 Build timed out (after 360 minutes). Marking the build as failed. > 21:44:37 Build was aborted > (Notice the 6 hours between). > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/710/con… > I think I saw another one earlier this week, also on fc25. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1226?page=com.atlassian.jira.… ] eedri updated OVIRT-1226: ------------------------- Resolution: Fixed Status: Done (was: Blocked) this should already be solved by moving find bugs code to check-patch.sh > https://gerrit.ovirt.org/#/c/73161 marked with CI-1 > --------------------------------------------------- > > Key: OVIRT-1226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1226 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yevgeny Zaspitsky > Assignee: infra > > Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful > CI runs it had. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1424) Re: Build timed out in Vdsm check-merged (was: False OST failure)
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1424?page=com.atlassian.jira.… ] eedri updated OVIRT-1424: ------------------------- Resolution: Duplicate Status: Done (was: To Do) ovirt-1442 > Re: Build timed out in Vdsm check-merged (was: False OST failure) > ----------------------------------------------------------------- > > Key: OVIRT-1424 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1424 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: infra > > adding infra-support to open a ticket. > On Thu, Jun 1, 2017 at 10:28 AM, Milan Zamazal <mzamazal(a)redhat.com> wrote: > > Another "Build timed out": > > > > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1870/ > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1477) Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1477?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1477: ---------------------------- Assignee: Barak Korren (was: infra) > Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own > --------------------------------------------------------------------------------------- > > Key: OVIRT-1477 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1477 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > Labels: repositories > > The 4.1 nightly publisher jobs are still using the old scheme of collecting packages directly from build-artifacts jobs instead of from 'tested'. We should move them to collect from 'tested' like the 'master' niightly publisher jobs. > As part of this work we should re-factor the YAML for the publisher jobs to make all of them use the same YAML job template instead of hard-coded job definitions. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eedri updated OVIRT-1479: ------------------------- Epic Link: OVIRT-403 (was: OVIRT-400) > dnf install in jobs setup scripts fails due to corrupted rpmdb > -------------------------------------------------------------- > > Key: OVIRT-1479 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt Infra > Reporter: ngoldin(a)redhat.com > Assignee: infra > Labels: rpmdb, standard-ci > > {code} > 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML > 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: BDB1507 Thread died in Berkeley DB library > 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery > 10:24:59 error: cannot open Packages index using db5 - (-30973) > 10:24:59 error: cannot open Packages database in /var/lib/rpm > 10:24:59 Error: Error: rpmdb open failed > 10:24:59 + failed=true > {code} > http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/… -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eedri updated OVIRT-1479: ------------------------- Epic Link: OVIRT-403 (was: OVIRT-400) > dnf install in jobs setup scripts fails due to corrupted rpmdb > -------------------------------------------------------------- > > Key: OVIRT-1479 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt Infra > Reporter: ngoldin(a)redhat.com > Assignee: infra > Labels: rpmdb, standard-ci > > {code} > 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML > 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: BDB1507 Thread died in Berkeley DB library > 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery > 10:24:59 error: cannot open Packages index using db5 - (-30973) > 10:24:59 error: cannot open Packages database in /var/lib/rpm > 10:24:59 Error: Error: rpmdb open failed > 10:24:59 + failed=true > {code} > http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/… -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eedri updated OVIRT-1479: ------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > dnf install in jobs setup scripts fails due to corrupted rpmdb > -------------------------------------------------------------- > > Key: OVIRT-1479 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt Infra > Reporter: ngoldin(a)redhat.com > Assignee: infra > Labels: rpmdb, standard-ci > > {code} > 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML > 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: BDB1507 Thread died in Berkeley DB library > 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery > 10:24:59 error: cannot open Packages index using db5 - (-30973) > 10:24:59 error: cannot open Packages database in /var/lib/rpm > 10:24:59 Error: Error: rpmdb open failed > 10:24:59 + failed=true > {code} > http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/… -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eedri updated OVIRT-1479: ------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > dnf install in jobs setup scripts fails due to corrupted rpmdb > -------------------------------------------------------------- > > Key: OVIRT-1479 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt Infra > Reporter: ngoldin(a)redhat.com > Assignee: infra > Labels: rpmdb, standard-ci > > {code} > 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML > 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: BDB1507 Thread died in Berkeley DB library > 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery > 10:24:59 error: cannot open Packages index using db5 - (-30973) > 10:24:59 error: cannot open Packages database in /var/lib/rpm > 10:24:59 Error: Error: rpmdb open failed > 10:24:59 + failed=true > {code} > http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/… -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1257) Setup mail delivery from Jenkins and slaves
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1257?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1257: ---------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Setup mail delivery from Jenkins and slaves > ------------------------------------------- > > Key: OVIRT-1257 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1257 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Marc Dequènes (Duck) > Priority: High > > I'm setting up some jobs that will require Jenkins and/or the slaves to send email to various places. Jenkins and the slaves seem to currently run Postfix in a default configuration that makes them attempt to deliver email directly to its destination. This causes sent email to get delayed. > We typically don't notice this because our SPF setting for ovirt.org are quite lax (We allow anyone to say he is from @ovirt.org, but delay messages that are not from "{{lists.phx.ovirt.org}}, "{{mail.phx.ovirt.org}}", or "{{gerrit.ovirt.org}}") abd because our ML server where we typically send to, only imposes a 60second delay. > We need to have a better setup. I suggest we configure Jenkins and the slaves to use some other server as a smart host (maybe "{{mail.phx.ovirt.org}}"?). To make the configuration as generic as possible I suggest we make the slaves deliver via Jenkins and only make Jenkins deliver to the smart host. > I think smart host configuration on Postfix is simple enough that we can make our usual job-embedded slave setup scrips set it up insead of having to resort to Puppet or Ansible. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0