June 2017 - Infra - oVirt List Archives

[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

[JIRA] (OVIRT-1471) Add SSL to jenkins.ovirt.org
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1471?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1471: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Add SSL to jenkins.ovirt.org > ---------------------------- > > Key: OVIRT-1471 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1471 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > > We probably need SSL for '{{jenkins.ovirt.org}}'. That server has privileges on most stuff that is running in PHX, so better not have passwords to it be exposed to MITM attacks... -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1476) Infra-Ansible needs a CI
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1476?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1476: ----------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Infra-Ansible needs a CI > ------------------------ > > Key: OVIRT-1476 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1476 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, oVirt CI > Reporter: Marc Dequènes (Duck) > Assignee: Marc Dequènes (Duck) > Labels: ansible, standard-ci > > I have no knowledge of Gerrit administration and never touched the oVirt CI, and I would like avoiding breaking the universe, so I'm requesting help here :-). -- 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 Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1477?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1477: -------------------------------- Labels: repositories (was: ) > 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: infra > 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-1061) Update http://monitoring.ovirt.org/ovirt.apps/
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1061?page=com.atlassian.jira.… ] eedri updated OVIRT-1061: ------------------------- Epic Link: OVIRT-403 > Update http://monitoring.ovirt.org/ovirt.apps/ > ---------------------------------------------- > > Key: OVIRT-1061 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1061 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please update http://monitoring.ovirt.org/ovirt.apps/ with all monitoring > and production services currently being used in oVirt infra. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0