December 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1651) Jenkins EL7 slaves configured as Fedora slaves
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1651?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1651: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) doesn't seem to be a real issue, please reopen if you still think something should be done. > Jenkins EL7 slaves configured as Fedora slaves > ---------------------------------------------- > > Key: OVIRT-1651 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1651 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: sbonazzo > Assignee: infra > Priority: Lowest > > This morning I'm seeing jobs failing trying to use DNF instead of YUM on EL7 slaves because of the existence of /etc/dnf directory on EL7 slaves: > Example job:http://jenkins.ovirt.org/job/ovirt-release_4.1_check-patch-el7-x86_64/1… > Example slave: http://jenkins.ovirt.org/computer/vm0085.workers-phx.ovirt.org > println "ls -l /etc/dnf".execute().text > println "cat /etc/os-release".execute().text > Result > total 8 > -rw-r--r--. 1 root root 1562 Sep 16 05:43 dnf.conf > -rw-r--r--. 1 root root 72 Mar 4 2015 dnf.conf.old > drwxr-xr-x. 2 root root 6 Jul 7 2015 plugins > drwxr-xr-x. 2 root root 21 Sep 14 21:57 protected.d > NAME="CentOS Linux" > VERSION="7 (Core)" > ID="centos" > ID_LIKE="rhel fedora" > VERSION_ID="7" > PRETTY_NAME="CentOS Linux 7 (Core)" > ANSI_COLOR="0;31" > CPE_NAME="cpe:/o:centos:centos:7" > HOME_URL="https://www.centos.org/" > BUG_REPORT_URL="https://bugs.centos.org/" > CENTOS_MANTISBT_PROJECT="CentOS-7" > CENTOS_MANTISBT_PROJECT_VERSION="7" > REDHAT_SUPPORT_PRODUCT="centos" > REDHAT_SUPPORT_PRODUCT_VERSION="7" > Please fix slaves configuration. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

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

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1239?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1239: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) No need for it anymore due to std-ci V2 > tracking ticket for supporting multiple organization in GH CR builder plugin > ---------------------------------------------------------------------------- > > Key: OVIRT-1239 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1239 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Lowest > > In current implementation credentials can be specified only per server so it's not possible to use different credentials for ovirt and lago projects using same jenkins instance as we do. > During meeting with [~eedri] we decided to evaluate two possible options: > 1) Webhooks to trigger build. From first glance it looks good but not sure if it's solve the problem with credentials. It should be implemented anyway and it's tracked under OVIRT-1142 > 2) Open RFE under GH PR Builder plugin to support this out of the box. > This ticket is opened to track progress on second option. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1527) Make Change-Id clickable
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

This is a multi-part message in MIME format... ------------=_1514292570-19796-118 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1527?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1527: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) If possible, try to reach out to OpenStack to see how they implemented it and if its requires a special plugin. > Make Change-Id clickable > ------------------------ > > Key: OVIRT-1527 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: Evgheni Dereveanchin > Priority: Low > > In openstack's gerrit, e.g. [1], the "Change-Id:" in the commit > message is clickable, and pressing it searches for patches including > it (e.g. in other branches). Might be useful for oVirt too. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514292570-19796-118 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1527?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1527:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <p>If possible, try to reach out to OpenStack to see how they implemented it and if its requires a special plugin.</p> <blockquote><h3>Make Change-Id clickable</h3> <pre> Key: OVIRT-1527 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yedidyah Bar David Assignee: Evgheni Dereveanchin Priority: Low</pre> <p>In openstack's gerrit, e.g. [1], the “Change-Id:” in the commit message is clickable, and pressing it searches for patches including it (e.g. in other branches). Might be useful for oVirt too. [1] <a href="https://review.openstack.org/471802">https://review.openstack.org/471802</a> — Didi</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514292570-19796-118--

1 0

[JIRA] (OVIRT-1109) Create jobs parameter in manual system tests
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1109?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1109: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) > Create jobs parameter in manual system tests > -------------------------------------------- > > Key: OVIRT-1109 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1109 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > You should do that by adding a dynamic parameter that'll have a groovy script such as: > {code} > import jenkins.model.* > def list = [] > def matchedJobs = Jenkins.instance.items.findAll { job -> > job.name =~ /build-artifacts/ > } > matchedJobs.each { job -> > if (!job.name.contains("archived_for_deletion")) { > list << job.name.split('_')[0] > } > } > return list.unique() > {code} > With the above script you'll have all project names. From the project name and the other parameters you can build any job's name: > {code} > {project}_{ovirt_version}_build-artifacts-{distro}-{arch} > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1113: ----------------------------- Labels: easy_task (was: ) > Automate project Gerrit repo creation > ------------------------------------- > > Key: OVIRT-1113 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Labels: easy_task > > Because the doc is annoying to follow manually, and its easy to automate Gerrit, the API is basically 'ssh'. > Long term if the automation is good we could make this "self service". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1333: ----------------------------- Labels: easy_task (was: ) > Exclude game/desktop packages from mirrors > ------------------------------------------ > > Key: OVIRT-1333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: easy_task > > Our mirrors currently contain full copies of the CentOS and Fedora repos, including many large game and desktop productivity packages. > We should probably clean these packages from the repos to save space and bandwidth. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1465) Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

This is a multi-part message in MIME format... ------------=_1514291743-11828-156 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1465: ---------------------------------- We have this in d/s jenkins already right? > Run JJB from 'check-merged' of 'jenkins' repo instead of its own job > -------------------------------------------------------------------- > > Key: OVIRT-1465 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, jjb, standard-ci > > Right not we have a custom job for running JJB after patches are merged to the 'jenkins' repo. > Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514291743-11828-156 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1465:</h3> <p>We have this in d/s jenkins already right?</p> <blockquote><h3>Run JJB from ‘check-merged’ of ‘jenkins’ repo instead of its own job</h3> <pre> Key: OVIRT-1465 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: jenkins, jjb, standard-ci</pre> <p>Right not we have a custom job for running JJB after patches are merged to the ‘jenkins’ repo. Once we can handle credentials in standard-CI we can move this functionality into the ‘check-merged’ job.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514291743-11828-156--

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

This is a multi-part message in MIME format... ------------=_1514291674-26699-130 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1479: ----------------------------- Resolution: Fixed Status: Done (was: To Do) slaves are now using mirrors, so issue should be fixed. > 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: Nadav Goldin > 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 (v1001.0.0-SNAPSHOT#100075) ------------=_1514291674-26699-130 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ]</pre> <h3>eyal edri updated OVIRT-1479:</h3> <pre>Resolution: Fixed Status: Done (was: To Do)</pre> <p>slaves are now using mirrors, so issue should be fixed.</p> <blockquote><h3>dnf install in jobs setup scripts fails due to corrupted rpmdb</h3> <pre> Key: OVIRT-1479 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt Infra Reporter: Nadav Goldin Assignee: infra Labels: rpmdb, standard-ci</pre> <p>{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} <a href="http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/…">http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/…</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514291674-26699-130--

1 0

[JIRA] (OVIRT-1551) Add slaves to staging Jenkins instance
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

This is a multi-part message in MIME format... ------------=_1514291346-16631-179 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1551?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1551: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Add slaves to staging Jenkins instance > -------------------------------------- > > Key: OVIRT-1551 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1551 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, slaves > > We currently have just one slave attached to the staging Jenkins instance. > We need some more, at least one of each slave platform we support so that we can: > # Test jobs running in paralllel > # Test jobs running on different slave platforms. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514291346-16631-179 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1551?page=com.atlassian.jira.… ]</pre> <h3>eyal edri updated OVIRT-1551:</h3> <pre>Resolution: Fixed Status: Done (was: To Do)</pre> <blockquote><h3>Add slaves to staging Jenkins instance</h3> <pre> Key: OVIRT-1551 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1551 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt Infra Reporter: Barak Korren Assignee: infra Labels: jenkins, slaves</pre> <p>We currently have just one slave attached to the staging Jenkins instance. We need some more, at least one of each slave platform we support so that we can: # Test jobs running in paralllel # Test jobs running on different slave platforms.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514291346-16631-179--

1 0

[JIRA] (OVIRT-1551) Add slaves to staging Jenkins instance
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1551?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1551: ---------------------------------- [http://jenkins-staging.phx.ovirt.org/] has multiple slaves now, closing. > Add slaves to staging Jenkins instance > -------------------------------------- > > Key: OVIRT-1551 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1551 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, slaves > > We currently have just one slave attached to the staging Jenkins instance. > We need some more, at least one of each slave platform we support so that we can: > # Test jobs running in paralllel > # Test jobs running on different slave platforms. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0