October 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1128) Add Jenkins job for testing
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508868183-10536-389 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1128?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1128: -------------------------------- Resolution: Fixed Status: Done (was: To Do) We have full CI flows running in the staging system now > Add Jenkins job for testing > --------------------------- > > Key: OVIRT-1128 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1128 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Pavel Zhukov > Assignee: infra > Labels: staging > > it'd be good to have jenkins job to test and regenerate jenkins jobs :) > which uses "good" jjb configuration and available for infra team from > any machine. > Currently local JJB instances and configs are used which is not perfect > because configs can be different as well as jjb versions, not rebased > repos can be used for testing Besides of that it requires copying of > configs between machines and so on. > -- > Pavel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508868183-10536-389 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1128?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1128:</h3> <pre>Resolution: Fixed Status: Done (was: To Do)</pre> <p>We have full CI flows running in the staging system now</p> <blockquote><h3>Add Jenkins job for testing</h3> <pre> Key: OVIRT-1128 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1128 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Pavel Zhukov Assignee: infra Labels: staging</pre> <p>it'd be good to have jenkins job to test and regenerate jenkins jobs :) which uses “good” jjb configuration and available for infra team from any machine. Currently local JJB instances and configs are used which is not perfect because configs can be different as well as jjb versions, not rebased repos can be used for testing Besides of that it requires copying of configs between machines and so on. — Pavel</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508868183-10536-389--

1 0

[JIRA] (OVIRT-1124) Automate oVirt official release process
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1124?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1124: ----------------------------------- Assignee: Barak Korren (was: infra) > Automate oVirt official release process > --------------------------------------- > > Key: OVIRT-1124 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1124 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: Barak Korren > > Current release flow is 100% manual and depends on multiple sources of built RPMs. > We should support one automated flow which will use the standard CI to build and publish official oVirt releases. > Some initial thoughts to consider: > * We'll need to trigger 'build-artifacts' job when a new tag is added to project and build the official release ( in ovirt-engine we do it already with a special if in build-artifacts.sh ) > * The new RPMS should pass OST / Experimental verification and deployed to 'pre' repo after verification. > * We should support only this flow and not external build systems like koji/copr, any project maintainer that still wants to build in other system is welcome, but for oVirt repos we'll do it from the official tag > * Consider using repoman for signing the RPMs when we compose the 'pre' repo > * If a project doesn't have a new tag to build from, we'll use the latest official release of that project. > [~bkorren@redhat.com][~amarchuk][~sbonazolla@redhat.com] thoughts? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508867991-21521-355 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1014: ----------------------------------- Assignee: Daniel Belenky (was: infra) > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: Daniel Belenky > Labels: standard-ci > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068) ------------=_1508867991-21521-355 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1014:</h3> <pre>Assignee: Daniel Belenky (was: infra)</pre> <blockquote><h3>avoid repetition in automation/*packages</h3> <pre> Key: OVIRT-1014 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: Daniel Belenky Labels: standard-ci</pre> <p>Currently we have many automation/*packages* files, mostly repeating each other. Most of the information there is then repeated in vdsm.spec as well. It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508867991-21521-355--

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1014: ------------------------------------- Adding OVIRT-1629 as a blocker. The new '{{automation.yaml}}' format will allow using the usual YAML tricks to reduce duplication between package lists. > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: standard-ci > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)

1 0

[JIRA] (OVIRT-907) Add CI for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Oct '17

24 Oct '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-907?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-907: ------------------------------- Resolution: Fixed Status: Done (was: To Do) The '{{check-patch.sh}}' script in the jenkins repo provides pretty good coverage these days > Add CI for mock_runner.sh > ------------------------- > > Key: OVIRT-907 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-907 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > We have some CI jobs running on our "Jenkins" repo right now. Those jobs mostly check YAML, but they are also useful for checking changes to mock_runner.sh because they are running inside it. However: > # These jobs do a full YAML check even when it is not needed. > # We're not actually checking mock_runner.sh for all the platforms it simulates. > We've already seem some regressions happen in the CI system because we don't have enough tests for mock_runner.sh > This ticket is for creating good CI coverage for mock_runner.sh, all that is needed to be done in practice is make some changes to the check_patch.sh script and the YAML so that: > * YAML checking is skipped if no JJB-related changes were done > * Various features of mock_runner like the installation of packages for the *.packages files are checked. > * The tests are ran for all platforms that mock_runner.sh supports. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #845
by jenkins＠jenkins.phx.ovirt.org 24 Oct '17

24 Oct '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/845/displa…> Changes: [Barak Korren] Converted hard-coded publisher job to a template [Barak Korren] Add nightly publisher job for 4.2 [Daniel Belenky] Added setup_project script ------------------------------------------ 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-epel-el6-x86_64/ws/> > 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/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision d62f1d28800e9fd7d99e8c059388d0c8cb3fc742 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f d62f1d28800e9fd7d99e8c059388d0c8cb3fc742 Commit message: "Added setup_project script" > git rev-list 3917e5b7cbfd863d48ffd707636093432c80c68a # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins5775303989387570256.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 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 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1478, in _commonLoadRepoXML self._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

[JIRA] (OVIRT-1705) Re: Can't login to Grafana via Google auth.?
by eyal edri (oVirt JIRA) 24 Oct '17

24 Oct '17

This is a multi-part message in MIME format... ------------=_1508851762-32732-336 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1705?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1705: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Re: Can't login to Grafana via Google auth.? > -------------------------------------------- > > Key: OVIRT-1705 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1705 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > > Also sending to infra-support to open a ticket. > I think there were some issues with the Graphana instance, but not sure if > we already have a ticket on it. > On Mon, Oct 16, 2017 at 4:28 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: > > I'm trying to login to http://graphite.phx.ovirt.org/login and it fails > > miserably when trying with Google auth. Any ideas? > > TIA, > > Y. > > > > _______________________________________________ > > 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 (v1001.0.0-SNAPSHOT#100068) ------------=_1508851762-32732-336 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1705?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1705:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>Re: Can't login to Grafana via Google auth.?</h3> <pre> Key: OVIRT-1705 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1705 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri Assignee: Evgheni Dereveanchin</pre> <p>Also sending to infra-support to open a ticket. I think there were some issues with the Graphana instance, but not sure if we already have a ticket on it. On Mon, Oct 16, 2017 at 4:28 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote:</p> <blockquote><p>I'm trying to login to <a href="http://graphite.phx.ovirt.org/login">http://graphite.phx.ovirt.org/login</a> and it fails miserably when trying with Google auth. Any ideas? TIA, Y.</p> <p><em>____________________________________________</em>_ Infra mailing list Infra(a)ovirt.org <a href="http://lists.ovirt.org/mailman/listinfo/infra">http://lists.ovirt.org/mailman/listinfo/infra</a></p></blockquote> <p>— Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1508851762-32732-336--

1 0

[oVirt Jenkins] standard-enqueue - Build #6028 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Oct '17

24 Oct '17

------=_Part_168_680963528.1508851142957 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/6028/ Build Name: #6028 Build Description: Gerrit: 83133 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/83133 - title: build: post ovirt-engine-3.6.12.1 - project: ovirt-engine - branch: ovirt-engine-3.6 - author: Lev Veyde <lveyde(a)redhat.com> ------=_Part_168_680963528.1508851142957--

1 0

[CQ]: 83134,2 (cockpit-ovirt) failed "ovirt-4.2" system tests
by oVirt Jenkins 24 Oct '17

24 Oct '17

Change 83134,2 (cockpit-ovirt) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83134/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/14/

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 7 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Oct '17

24 Oct '17

------=_Part_79_1347199170.1508242833747 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build Number: 7 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #7 [Sandro Bonazzola] ovirt-guest-agent: dropping fc25 [Sandro Bonazzola] ovirt-wgt: drop legacy jobs [Sandro Bonazzola] repoman: drop el6 jobs [Barak Korren] Add Fedora rawhide support [Sandro Bonazzola] nightly-4.1: move ovirt-wgt to standard ci [Barak Korren] Capture head commit info from GitHub events [Barak Korren] Added submission of GitHub changes to CQ [Barak Korren] Generalized CQ tester pipeline code [Sandro Bonazzola] jasper-reports: drop job [Eyal Edri] remove getbadges Jenkins integration [Yuval Turgeman] automation: view install log in console ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_79_1347199170.1508242833747--

1 1