- Infra - oVirt List Archives

[JIRA] (OVIRT-930) check why ost 4.0 failed on vm run job even though not change was done
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-930?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-930: -------------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > check why ost 4.0 failed on vm run job even though not change was done > ---------------------------------------------------------------------- > > Key: OVIRT-930 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-930 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: ost_failures > > Looks like false positive or race issue, but still needs to be debug for RCA. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3389/consoleF… -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5918 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

------=_Part_177_1617334180.1490017236299 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5918/, Build Number: 5918, Build Status: FAILURE ------=_Part_177_1617334180.1490017236299--

1 2

[JIRA] (OVIRT-1084) Merge github and gerrit jobs
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1084?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1084: -------------------------------------------------- [~landgraf] can we close this ? > Merge github and gerrit jobs > ---------------------------- > > Key: OVIRT-1084 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1084 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > As per https://ovirt-jira.atlassian.net/browse/OVIRT-970 gerrit and github jobs contan a lot of common code and features so they should be merged and _github_ suffix removed from the job names. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1250: --------------------------------------------- Epic Link: OVIRT-403 > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1245) Consider way for organize disaster recovery solution for lists
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1245?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1245: --------------------------------------------- Epic Link: OVIRT-403 > Consider way for organize disaster recovery solution for lists > -------------------------------------------------------------- > > Key: OVIRT-1245 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1245 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > > │08:50:51 sbonazzo1 | landgraf: we're lucky enough we have mirrors for users │ > │08:51:05 sbonazzo1 | landgraf: too bad we don't have redundant CI infra :-) │ > │08:51:27 landgraf | sbonazzo1: and lists.. │ > │08:51:40 landgraf | sbonazzo1: so we cannot send outage ntifications there :) │ > │08:51:51 sbonazzo1 | landgraf: yep │ > │08:52:03 sbonazzo1 | landgraf: maybe worth to open a jira ticket for it │ > │08:52:10 sbonazzo1 | landgraf: it will be a huge improvement │ > │08:53:30 sbonazzo1 | landgraf: do we have a disaster recovery plan? -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1245) Consider way for organize disaster recovery solution for lists
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1245?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1245: --------------------------------------------- Epic Link: OVIRT-403 > Consider way for organize disaster recovery solution for lists > -------------------------------------------------------------- > > Key: OVIRT-1245 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1245 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > > │08:50:51 sbonazzo1 | landgraf: we're lucky enough we have mirrors for users │ > │08:51:05 sbonazzo1 | landgraf: too bad we don't have redundant CI infra :-) │ > │08:51:27 landgraf | sbonazzo1: and lists.. │ > │08:51:40 landgraf | sbonazzo1: so we cannot send outage ntifications there :) │ > │08:51:51 sbonazzo1 | landgraf: yep │ > │08:52:03 sbonazzo1 | landgraf: maybe worth to open a jira ticket for it │ > │08:52:10 sbonazzo1 | landgraf: it will be a huge improvement │ > │08:53:30 sbonazzo1 | landgraf: do we have a disaster recovery plan? -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1250: --------------------------------------------- Epic Link: OVIRT-403 > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1223) Nightly/bare metal vdsm check-merged jobs
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1223?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1223: --------------------------------------------- Resolution: Won't Do Status: Done (was: To Do) As discussed, please add these tests to the OST suite. If we'll find out that they are taking too long, we'll introduce a nightly OST suite if needed. > Nightly/bare metal vdsm check-merged jobs > ----------------------------------------- > > Key: OVIRT-1223 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1223 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Leon Goldberg > Assignee: infra > > Hey, > We're trying to come up with a solution to our lengthy check-merged > jobs, that are about to become even lengthier now when we've > discovered we're missing a permutation to our network tests. > check-merged currently takes roughly 50 minutes to run to completion, > with the network tests taking roughly 30 minutes; with the additional > permutation check-merged will run for more than an hour. > We thought of 2 possible solutions: > 1) Only run the additional permutation once a day (e.g. introduce a > nightly job). > 2) Run check-merged on bare metal -- network tests take roughly 1/3 of > the time on bare metal. > Somehow closing the gap to bare metal would also of course be nice. > We'd love your input. > Thanks, > Leon -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1237) Move repclosure jobs to OST
by Daniel Belenky (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1237?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1237: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Move repclosure jobs to OST > --------------------------- > > Key: OVIRT-1237 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1237 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Daniel Belenky > > (14:08:22) sbonazzo: bkorren: I'm thinking about moving check-closure jobs > to standard CI. Do I need a new git repo for it? > (14:08:47) sbonazzo: bkorren: or now standard CI supports subdirectories? > (14:14:55) bkorren: sbonazzo, I think the best place for it is OST > (14:15:29) bkorren: sbonazzo, because then it can run against the > experimental repo, as well as the pre-release and stable ones > (14:16:57) sbonazzo: bkorren: OST has a learning curve I can't afford :-) > if that's the best place, I'll open a bz to track it and will plan for it > (14:17:49) bkorren: sbonazzo, okok, but its as easy as adding one > repoclosure command to run against the repo it already composes on its own > (14:18:26) bkorren: sbonazzo, please open a Jira as well, we might find a > good time to add it at some point <- eedri|afk > -- > 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.824.3#100035)

1 0

[JIRA] (OVIRT-1237) Move repclosure jobs to OST
by eyal edri [Administrator] (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1237?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1237: --------------------------------------------- Resolution: Duplicate Status: Done (was: To Do) OVIRT-911 > Move repclosure jobs to OST > --------------------------- > > Key: OVIRT-1237 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1237 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > (14:08:22) sbonazzo: bkorren: I'm thinking about moving check-closure jobs > to standard CI. Do I need a new git repo for it? > (14:08:47) sbonazzo: bkorren: or now standard CI supports subdirectories? > (14:14:55) bkorren: sbonazzo, I think the best place for it is OST > (14:15:29) bkorren: sbonazzo, because then it can run against the > experimental repo, as well as the pre-release and stable ones > (14:16:57) sbonazzo: bkorren: OST has a learning curve I can't afford :-) > if that's the best place, I'll open a bz to track it and will plan for it > (14:17:49) bkorren: sbonazzo, okok, but its as easy as adding one > repoclosure command to run against the repo it already composes on its own > (14:18:26) bkorren: sbonazzo, please open a Jira as well, we might find a > good time to add it at some point <- eedri|afk > -- > 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.824.3#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4581 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

------=_Part_82_1776490534.1489546652415 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4581/, Build Number: 4581, Build Status: FAILURE ------=_Part_82_1776490534.1489546652415--

1 8

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5915 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

------=_Part_171_1127805282.1490011346152 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5915/, Build Number: 5915, Build Status: FAILURE ------=_Part_171_1127805282.1490011346152--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5909 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

------=_Part_160_1401082672.1489998378761 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5909/, Build Number: 5909, Build Status: FAILURE ------=_Part_160_1401082672.1489998378761--

1 1

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #170
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/170/displa…> ------------------------------------------ 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 a5038d6893e1ea9d19c2253e18ff28b6e8c7311f (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f a5038d6893e1ea9d19c2253e18ff28b6e8c7311f > git rev-list a5038d6893e1ea9d19c2253e18ff28b6e8c7311f # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson1434698995110565518.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 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, 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 1451, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1420, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1278, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-base-fc24/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt_4.1_he-system-tests - Build # 47 - Still Failing!
by jenkins＠jenkins.phx.ovirt.org 20 Mar '17

20 Mar '17

------=_Part_154_1962669375.1489977573997 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/47/ Build Number: 47 Build Status: Still Failing Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #44 [Lev Veyde] Configure NFSv3 to use static ports Changes for Build #45 [Lev Veyde] Configure NFSv3 to use static ports [Sandro Bonazzola] ovirt-engine-cli: drop fc24 on master [Sandro Bonazzola] ovirt-engine-yarn: drop fc24 on master [Sandro Bonazzola] ovirt-imageio: drop fc24 on master [Sandro Bonazzola] ovirt-vmconsole: drop fc24 on master Changes for Build #46 [Lev Veyde] Configure NFSv3 to use static ports Changes for Build #47 [Ondra Machacek] Fix Ansible modules tests [Daniel Belenky] ost publisher: replaced 'email' with 'email-ext' [Gil Shinar] New builder that includes a few more std steps ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_154_1962669375.1489977573997--

1 2

[JIRA] (OVIRT-1264) Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects'
by Barak Korren (oVirt JIRA) 20 Mar '17

20 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1264?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1264: -------------------------------- Epic Link: OVIRT-400 > Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects' > ------------------------------------------------------------------------------- > > Key: OVIRT-1264 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1264 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > We've been doing some work recently to enable using the 'jenkins' repo to create different jobs for different Jenkins instances. I had been working on enabling its use to configure the staging server, while Gil had been working on using it downstream. > This work is based on the assumption that the '{{jobs/confs/yaml}}' directory only contains job templates and not individual job definitions. This is certainly true for all standard-CI jobs. > I have found, however, a few jobs that are defined inside the YAML directory. These include: > - ovirt-engine_master_coverity-analysis > - scan_security_and_license_ovirt-engine_master > - system_gerrit-alert-old-patches > - system_jenkins-report > Some of these jobs seem quite old. Can we remove them? Alternatively we could move the definitions to the '{{projects}}' directory, or, ideally, re-factor them into separate 'job-template' and 'project' definitions that reside in the right places. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1264) Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects'
by Barak Korren (oVirt JIRA) 20 Mar '17

20 Mar '17

Barak Korren created OVIRT-1264: ----------------------------------- Summary: Move individual job definitions from 'jobs/confs/yaml' to 'jobs/confs/projects' Key: OVIRT-1264 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1264 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra We've been doing some work recently to enable using the 'jenkins' repo to create different jobs for different Jenkins instances. I had been working on enabling its use to configure the staging server, while Gil had been working on using it downstream. This work is based on the assumption that the '{{jobs/confs/yaml}}' directory only contains job templates and not individual job definitions. This is certainly true for all standard-CI jobs. I have found, however, a few jobs that are defined inside the YAML directory. These include: - ovirt-engine_master_coverity-analysis - scan_security_and_license_ovirt-engine_master - system_gerrit-alert-old-patches - system_jenkins-report Some of these jobs seem quite old. Can we remove them? Alternatively we could move the definitions to the '{{projects}}' directory, or, ideally, re-factor them into separate 'job-template' and 'project' definitions that reside in the right places. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

oVirt infra daily report - unstable production jobs - 263
by jenkins＠jenkins.phx.ovirt.org 19 Mar '17

19 Mar '17

------=_Part_148_975747284.1489964418248 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/263//artifact/exported-a… Cheers, Jenkins ------=_Part_148_975747284.1489964418248 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 19/03/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_…">ovirt-system-tests_master_check-patch-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_image-ng-system-tests/">ovirt_4.0_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  NOT STABLE YET </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc25_merged/">repos_master_check-closure_fc25_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_148_975747284.1489964418248--

1 0

Job definitions in the 'yaml' directory
by Barak Korren 19 Mar '17

19 Mar '17

Hi guys, We've been doing some work recently to enable using the 'jenkins' repo to create different jobs for different Jenkins instances. I had be working on enabling its use to configure the staging server, while Gil had been working on using it downstream. This work is based on the assumption that the 'jobs/confs/yaml' directory only contains job templates and not individual job definitions. This is certainly true for all standard-CI jobs. I have found, however, a few jobs that are defined inside the YAML directory. These include: - ovirt-engine_master_coverity-analysis - scan_security_and_license_ovirt-engine_master - system_gerrit-alert-old-patches - system_jenkins-report Some of these jobs seem quite old. Can we remove them? Alternatively we could move the definitions to the 'projects' directory, or, ideally, re-factor them into separate 'job-template' and 'project' definitions that reside in the right places. -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

2 2

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5881 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 19 Mar '17

19 Mar '17

------=_Part_146_1936651830.1489925604532 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5881/, Build Number: 5881, Build Status: FAILURE ------=_Part_146_1936651830.1489925604532--

1 0

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by Barak Korren (oVirt JIRA) 19 Mar '17

19 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-973: ------------------------------------ [~eedri] [~gshereme(a)redhat.com] The question is *when* do we want to build all permutations, what would be the conditions that cause this to be done. Unfortunately, setting detailed specifications from Gerrit comments is not doable currently, because AFAIK the Jenkins Gerrit plugin does not make the comment text available to running jobs. We could, however, tell patch-set events apart from comment events, so we can theoretically make "{{build-artifacts.sh}}" behave differently if it was triggered manually as opposed to automatically (We will need to think how to expose this information to the script is a useful manner). > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > Labels: standard-ci > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

Re: [ovirt-devel] [ OST Failure Report ] [ ovirt-engine-4.1 ] [ 02.03.2017 ] [004_basic_sanity]
by Piotr Kliczewski 19 Mar '17

19 Mar '17

+ infra On Thu, Mar 16, 2017 at 5:32 PM, Piotr Kliczewski <piotr.kliczewski(a)gmail.com> wrote: > I checked the logs and I checked that the job somehow used older > version without the fix: > > 2017-03-16 14:16:07,212::INFO::repoman.common.stores.RPM::Adding > package /var/lib/lago/reposync/ovirt-4.1-el7/noarch/vdsm-jsonrpc-java-1.3.8-1.el7.centos.noarch.rpm > to repo /dev/shm/ost/deployment-basic-suite-4.1/default/internal_repo > > How is it possible? > > On Thu, Mar 16, 2017 at 4:30 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: >> Just had this failure again[1], relevant log[2]. >> >> I still feel there's an issue here: >> {"jsonrpc": "2.0", "id": "aa241c36-d61d-4f9f-9baf-040b00638d00", "result": >> [{"username": "Unknown", "displayInfo": [{"tlsPort": "-1", "ipAddress": >> "192.168.201.4", "type": "vnc", "port": "5900"}, {"tlsPort": "5901", >> "ipAddress": "192.168.201.4", "type": "spice", "port": "-1"}], "hash": >> "964568653906073065", "acpiEnable": "true", "displayIp": "192.168.201.4", >> "guestFQDN": "", "vmId": "c9db9f94-3086-47e4-b997-01564ecb5319", "pid": >> "23127", "timeOffset": "0", "session": "Unknown", "displaySecurePort": "-1", >> "displayPort": "5900", "memUsage": "0", "guestIPs": "", "vcpuQuota": "-1", >> "kvmEnable": "true", "displayType": "vnc", "cpuUser": "0.00", "vmJobs": {}, >> "monitorResponse": "0", "elapsedTime": "477", "vmType": "kvm", "cpuSys": >> "0.00", "status": "Up", "guestCPUCount": -1, "appsList": [], "clientIp": "", >> "statusTime": "4295847140", "vmName": "vm0", "vcpuPeriod": 100000}]} >> 2017-03-16 10:36:17,558-04 DEBUG >> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) >> [cb68faa] Internal server error 880 > 879: >> java.lang.IllegalArgumentException: 880 > 879 >> at java.util.Arrays.copyOfRange(Arrays.java:3519) [rt.jar:1.8.0_121] >> at >> org.ovirt.vdsm.jsonrpc.client.reactors.stomp.StompCommonClient.processIncoming(StompCommonClient.java:145) >> [vdsm-jsonrpc-java-client.jar:] >> at >> org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient.process(ReactorClient.java:195) >> [vdsm-jsonrpc-java-client.jar:] >> at >> org.ovirt.vdsm.jsonrpc.client.reactors.SSLClient.process(SSLClient.java:121) >> [vdsm-jsonrpc-java-client.jar:] >> at >> org.ovirt.vdsm.jsonrpc.client.reactors.Reactor.lambda$processChannels$2(Reactor.java:80) >> [vdsm-jsonrpc-java-client.jar:] >> >> Y. >> >> [1] >> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… >> [2] >> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… >> >> On Fri, Mar 3, 2017 at 9:53 AM, Pavel Zhukov <pzhukov(a)redhat.com> wrote: >>> >>> >>> Hi, >>> >>> This is one-time failure. Non reproducible. disk_id was not inserted >>> into DB because of jsonrpc/networking issue. But once OST runs on >>> localhost networking (should not) be a problem here so adding Piotr. >>> >>> Failed jobs: >>> >>> http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… >>> >>> Logs: >>> >>> http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… >>> >>> http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… >>> >>> [LOGS SNIPPETS] >>> >>> 35897:2017-03-02 07:12:28,721-05 INFO >>> [org.ovirt.engine.core.vdsbroker.irsbroker.CreateImageVDSCommand] (default >>> task-19) [4adab878] START, CreateImageVDSCommand( >>> CreateImageVDSCommandParameters:{runAsync='true', >>> storagePoolId='9314c679-9a20-48b4-b62a-f7b6a3703287', >>> ignoreFailoverLimit='false', >>> storageDomainId='49226db8-e43f-4a15-a3a3-0bddd690d06b', >>> imageGroupId='9cf5a90d-05fc-45de-a3c1-adbb6822150e', imageSizeInBytes='2', >>> volumeFormat='COW', newImageId='c5275e2f-ac80-47c2-a43e-b5a0420a4211', >>> newImageDescription='{"DiskAlias":"vm0_disk0","DiskDescription":""}', >>> imageInitialSizeInBytes='0'}), log id: 657ef611 >>> >>> 35920:{"jsonrpc":"2.0","method":"Volume.create","params":{"volumeID":"c5275e2f-ac80-47c2-a43e-b5a0420a4211","storagepoolID":"9314c679-9a20-48b4-b62a-f7b6a3703287","storagedomainID":"49226db8-e43f-4a15-a3a3-0bddd690d06b","imageID":"9cf5a90d-05fc-45de-a3c1-adbb6822150e","size":"2","volFormat":4,"preallocate":2,"diskType":2,"desc":"{\"DiskAlias\":\"vm0_disk0\",\"DiskDescription\":\"\"}","srcImgUUID":"00000000-0000-0000-0000-000000000000","srcVolUUID":"00000000-0000-0000-0000-000000000000"},"id":"0a757eae-0cc2-4f15-9bb5-05ad3221f697"} >>> <=== NOTE NULL character here >>> 35926:<JsonRpcRequest id: "0a757eae-0cc2-4f15-9bb5-05ad3221f697", >>> method: Volume.create, params: >>> {volumeID=c5275e2f-ac80-47c2-a43e-b5a0420a4211, >>> storagepoolID=9314c679-9a20-48b4-b62a-f7b6a3703287, >>> storagedomainID=49226db8-e43f-4a15-a3a3-0bddd690d06b, >>> imageID=9cf5a90d-05fc-45de-a3c1-adbb6822150e, size=2, volFormat=4, >>> preallocate=2, diskType=2, >>> desc={"DiskAlias":"vm0_disk0","DiskDescription":""}, >>> srcImgUUID=00000000-0000-0000-0000-000000000000, >>> srcVolUUID=00000000-0000-0000-0000-000000000000}> >>> 35996:2017-03-02 07:12:30,468-05 ERROR >>> [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (default >>> task-19) [4adab878] ERROR, CreateImageVDSCommand( >>> CreateImageVDSCommandParameters:{runAsync='true', >>> storagePoolId='9314c679-9a20-48b4-b62a-f7b6a3703287', >>> ignoreFailoverLimit='false', >>> storageDomainId='49226db8-e43f-4a15-a3a3-0bddd690d06b', >>> imageGroupId='9cf5a90d-05fc-45de-a3c1-adbb6822150e', imageSizeInBytes='2', >>> volumeFormat='COW', newImageId='c5275e2f-ac80-47c2-a43e-b5a0420a4211', >>> newImageDescription='{"DiskAlias":"vm0_disk0","DiskDescription":""}', >>> imageInitialSizeInBytes='0'}), exception: VDSGenericException: >>> VDSNetworkException: 880 > 879, log id: 657ef611 >>> 36511:2017-03-02 07:12:35,744-05 INFO >>> [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] >>> (default task-19) [4adab878] Command >>> [id=35007fba-781c-4a15-8f29-a8efe441b2f3]: Compensating NEW_ENTITY_ID of >>> org.ovirt.engine.core.common.businessentities.storage.DiskImage; snapshot: >>> 9cf5a90d-05fc-45de-a3c1-adbb6822150e. >>> 2017-03-02 07:12:35,766-05 WARN >>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >>> (DefaultQuartzScheduler7) [6dc0e793] EVENT_ID: >>> SYSTEM_CHANGE_STORAGE_POOL_STATUS_PROBLEMATIC(980), Correlation ID: >>> 6dc0e793, Call Stack: null, Custom Event ID: -1, Message: Invalid status on >>> Data Center test-dc. Setting status to Non Responsive. >>> 2017-03-02 07:12:35,773-05 INFO >>> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-19) >>> [4adab878] Removed task '10b3bd58-8f3e-4b23-a8b6-27db110810d5' from DataBase >>> 2017-03-02 07:12:35,779-05 DEBUG >>> [org.ovirt.engine.core.dal.dbbroker.CustomSQLErrorCodeSQLExceptionTranslator] >>> (default task-19) [4adab878] Translating SQLException with SQL state >>> '23503', error code '0', message [ERROR: insert or update on table >>> "disk_vm_element" violates foreign key constraint >>> "fk_disk_vm_element_base_disks" >>> Detail: Key (disk_id)=(9cf5a90d-05fc-45de-a3c1-adbb6822150e) is not >>> present in table "base_disks". >>> >>> -- >>> Pavel >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/devel >> >> >> >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel

4 6

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by eyal edri [Administrator] (oVirt JIRA) 19 Mar '17

19 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-973: ------------------------------------------------- We need to find a solution for allowing builds with non default params to be triggered as part of build-on-demand, which we don't want to run all the time in CI. This makes sense for many reasons, especially now that these jobs are used for OST manual testing, for e.g: * Build all permutations to verify a UI bug * Build with DEBUG mode on, to have more logs So we need to find a generic way to support this in standard CI. > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > Labels: standard-ci > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by eyal edri [Administrator] (oVirt JIRA) 19 Mar '17

19 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-973: -------------------------------------------- Issue Type: Improvement (was: Bug) > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > Labels: standard-ci > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5888 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 18 Mar '17

18 Mar '17

------=_Part_138_1114274809.1489847808022 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5888/, Build Number: 5888, Build Status: FAILURE ------=_Part_138_1114274809.1489847808022--

1 1

oVirt infra daily report - unstable production jobs - 262
by jenkins＠jenkins.phx.ovirt.org 18 Mar '17

18 Mar '17

------=_Part_140_131075862.1489878017685 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/262//artifact/exported-a… Cheers, Jenkins ------=_Part_140_131075862.1489878017685 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 18/03/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  NOT STABLE YET </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc25_merged/">repos_master_check-closure_fc25_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_140_131075862.1489878017685--

1 0

oVirt infra daily report - unstable production jobs - 261
by jenkins＠jenkins.phx.ovirt.org 17 Mar '17

17 Mar '17

------=_Part_134_589437812.1489791617833 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/261//artifact/exported-a… Cheers, Jenkins ------=_Part_134_589437812.1489791617833 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 17/03/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_image-ng-system-tests/">ovirt_4.0_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  NOT STABLE YET </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc25_merged/">repos_master_check-closure_fc25_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_134_589437812.1489791617833--

1 0

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by Greg Sheremeta (oVirt JIRA) 17 Mar '17

17 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-973: -------------------------------------- [~bkorren(a)redhat.com] For the reporter of the issue, the goal is to have an entirely-built engine, all 3 GWT permutations [*]. I assume to save resources (?), we stopped building the Chrome permutation. The builds now only do 1 permutation for Firefox. > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > Labels: standard-ci > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

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

17 Mar '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/162/displa…> ------------------------------------------ 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 909e51dadfbb8969b6ac776bf9c646ead1a394f2 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 909e51dadfbb8969b6ac776bf9c646ead1a394f2 > git rev-list 909e51dadfbb8969b6ac776bf9c646ead1a394f2 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson2403755655707638215.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 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, 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 1451, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1429, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 911, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 899, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc24/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1263) Admin privileges for ovirt-ui-components
by eyal edri [Administrator] (oVirt JIRA) 17 Mar '17

17 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1263?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1263: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) Added mareklibra as admin to the ovirt-ui-components project, you can now enable any intergration in github like travis > Admin privileges for ovirt-ui-components > ---------------------------------------- > > Key: OVIRT-1263 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1263 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please grant @mareklibra admin rights on the ovirt-ui-components project > in both travis and github. > The project is mandatory part of the ovirt-web-ui developed together. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5877 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 17 Mar '17

17 Mar '17

------=_Part_129_1689376950.1489744135380 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5877/, Build Number: 5877, Build Status: FAILURE ------=_Part_129_1689376950.1489744135380--

1 1

[JIRA] (OVIRT-1260) Assign dev role to my Jenkins account
by Evgheni Dereveanchin (oVirt JIRA) 17 Mar '17

17 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1260?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1260: ------------------------------------------- Assignee: Gil Shinar (was: infra) > Assign dev role to my Jenkins account > ------------------------------------- > > Key: OVIRT-1260 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1260 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shmuel Melamud > Assignee: Gil Shinar > > Hi! > Can you please assign 'dev role' to my Jenkins account (smelamud)? I > need it to run OST Manual job. > Shmuel -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1259) Create new gerrit project: ovirt-containers
by Evgheni Dereveanchin (oVirt JIRA) 17 Mar '17

17 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1259?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1259: ---------------------------------------- Resolution: Done Status: Done (was: To Do) I see that there are commits in the repo and they get mirrored to GitHub properly: https://github.com/oVirt/ovirt-containers Closing for now. > Create new gerrit project: ovirt-containers > ------------------------------------------- > > Key: OVIRT-1259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1259 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > Adding infra-support to open a ticket. > On Tue, Mar 14, 2017 at 5:04 PM, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Yes, please do - ovirt-containers , with mirror in github.com/ovirt > > ..important > > > > Thanks. > > > > On Tue, Mar 14, 2017 at 4:26 PM Anton Marchukov <amarchuk(a)redhat.com> > > wrote: > > > >> Hello Yaniv. > >> > >> Renaming projects in gerrit is not possible. Well it is possible through > >> SQL hacks and some DB wrangling following a reindex and thus is far from a > >> standard operation. There is also rename-project plugin that we do not have > >> installed and tested. > >> > >> Instead I can create a new project with the same permissions etc, what do > >> you think? > >> > >> Anton. > >> > >> On Tue, Mar 14, 2017 at 3:18 PM, Yaniv Bronheim <ybronhei(a)redhat.com> > >> wrote: > >> > >> > >> Hi, > >> > >> short version: rename ovirt-container-engine project to ovirt-containers > >> > >> long version: recently we decided to gather all ovirt container under > >> ovirt-containers project instead of splitting it to engine and node. can > >> you please rename the current ovirt-container-engine to ovirt-containers > >> > >> Thanks. > >> -- > >> Yaniv Bronhaim. > >> > >> _______________________________________________ > >> Infra mailing list > >> Infra(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/infra > >> > >> > >> > >> > >> -- > >> Anton Marchukov > >> Senior Software Engineer - RHEV CI - Red Hat > >> > >> -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV 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 (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-1262) Please install the "Pipeline Utility Steps" plugin
by Evgheni Dereveanchin (oVirt JIRA) 17 Mar '17

17 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1262?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1262: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Please install the "Pipeline Utility Steps" plugin > -------------------------------------------------- > > Key: OVIRT-1262 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1262 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > > It provides various useful stuff for pipeline jobs: > https://jenkins.io/doc/pipeline/steps/pipeline-utility-steps/ -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5874 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 17 Mar '17

17 Mar '17

------=_Part_122_1986480707.1489726889622 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5874/, Build Number: 5874, Build Status: FAILURE ------=_Part_122_1986480707.1489726889622--

1 2

[JIRA] (OVIRT-1263) Admin privileges for ovirt-ui-components
by Marek Libra (oVirt JIRA) 17 Mar '17

17 Mar '17

Marek Libra created OVIRT-1263: ---------------------------------- Summary: Admin privileges for ovirt-ui-components Key: OVIRT-1263 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1263 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Marek Libra Assignee: infra Please grant @mareklibra admin rights on the ovirt-ui-components project in both travis and github. The project is mandatory part of the ovirt-web-ui developed together. -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by Barak Korren (oVirt JIRA) 17 Mar '17

17 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-973: ------------------------------------ [~gshereme(a)redhat.com] I'm kind of opposed to adding parameters to the Standard-CI process. The whole point of it is that one can just run "{{mock-runner.sh}}" from a project directory without knowing anything and get results. We need to think what is the goal we want to achieve, and then see how to fit it in the existing framework. I will have to read the discussion here and think about this. > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > Labels: standard-ci > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.824.3#100035)

1 0

oVirt infra daily report - unstable production jobs - 260
by jenkins＠jenkins.phx.ovirt.org 16 Mar '17

16 Mar '17

------=_Part_118_435547176.1489705225143 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/260//artifact/exported-a… Cheers, Jenkins ------=_Part_118_435547176.1489705225143 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 16/03/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_…">ovirt-system-tests_master_check-patch-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  NOT STABLE YET </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc25_merged/">repos_master_check-closure_fc25_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_118_435547176.1489705225143--

1 0

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by Greg Sheremeta (oVirt JIRA) 16 Mar '17

16 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-973: -------------------------------------- > Alternatively, provide a way to retrigger the nightly build with some parameter enabling the Chrome GWT permutation. +1. That seems like the best way. [~eedri] [~bkorren(a)redhat.com] What is the proper way to do this in Jenkins? I can try to take a stab at it. Will every engine job need to be updated to have this parameter added? I think (for this use case) we could get away with only needing master on EL7 compiled for both browsers. That's what mburman is using. > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > Labels: standard-ci > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.824.2#100035)

1 0

[JIRA] (OVIRT-1262) Please install the "Pipeline Utility Steps" plugin
by Barak Korren (oVirt JIRA) 16 Mar '17

16 Mar '17

Barak Korren created OVIRT-1262: ----------------------------------- Summary: Please install the "Pipeline Utility Steps" plugin Key: OVIRT-1262 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1262 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: High It provides various useful stuff for pipeline jobs: https://jenkins.io/doc/pipeline/steps/pipeline-utility-steps/ -- This message was sent by Atlassian JIRA (v1000.824.2#100035)

1 0

[JIRA] (OVIRT-1262) Please install the "Pipeline Utility Steps" plugin
by Barak Korren (oVirt JIRA) 16 Mar '17

16 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1262?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1262: -------------------------------- Epic Link: OVIRT-403 > Please install the "Pipeline Utility Steps" plugin > -------------------------------------------------- > > Key: OVIRT-1262 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1262 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > It provides various useful stuff for pipeline jobs: > https://jenkins.io/doc/pipeline/steps/pipeline-utility-steps/ -- This message was sent by Atlassian JIRA (v1000.824.2#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5864 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 16 Mar '17

16 Mar '17

------=_Part_112_152253438.1489669794783 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5864/, Build Number: 5864, Build Status: FAILURE ------=_Part_112_152253438.1489669794783--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #981 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 16 Mar '17

16 Mar '17

------=_Part_110_305690534.1489656096513 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/981/, Build Number: 981, Build Status: FAILURE ------=_Part_110_305690534.1489656096513--

1 1

[JIRA] (OVIRT-1260) Assign dev role to my Jenkins account
by Gil Shinar (oVirt JIRA) 16 Mar '17

16 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1260?page=com.atlassian.jira.… ] Gil Shinar updated OVIRT-1260: ------------------------------ Resolution: Fixed Status: Done (was: To Do) > Assign dev role to my Jenkins account > ------------------------------------- > > Key: OVIRT-1260 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1260 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shmuel Melamud > Assignee: infra > > Hi! > Can you please assign 'dev role' to my Jenkins account (smelamud)? I > need it to run OST Manual job. > Shmuel -- This message was sent by Atlassian JIRA (v1000.824.2#100035)

1 0

[JIRA] (OVIRT-1260) Assign dev role to my Jenkins account
by Shmuel Melamud (oVirt JIRA) 16 Mar '17

16 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1260?page=com.atlassian.jira.… ] Shmuel Melamud commented on OVIRT-1260: --------------------------------------- Works. Thanks! > Assign dev role to my Jenkins account > ------------------------------------- > > Key: OVIRT-1260 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1260 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shmuel Melamud > Assignee: infra > > Hi! > Can you please assign 'dev role' to my Jenkins account (smelamud)? I > need it to run OST Manual job. > Shmuel -- This message was sent by Atlassian JIRA (v1000.824.2#100035)

1 0

[JIRA] (OVIRT-1261) Enable travis for github/oVirt/cockpit-machines-ovirt-provider
by eyal edri [Administrator] (oVirt JIRA) 16 Mar '17

16 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1261?page=com.atlassian.jira.… ] eyal edri [Administrator] edited comment on OVIRT-1261 at 3/16/17 2:25 PM: --------------------------------------------------------------------------- What we do in these cases is to give the maintainer admin rights to the repo, so you can add any integration you'd lilke. I gave you admin rights on the project, so you can enable the travis integration. was (Author: eedri): What we do in these cases if to give the maintainer admin rights to the repo, so you can add any intergration you'd lilke. I gave you admin rights on the project, so you can enable the travis intergration. > Enable travis for github/oVirt/cockpit-machines-ovirt-provider > -------------------------------------------------------------- > > Key: OVIRT-1261 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1261 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please enable travis for > https://travis-ci.org/oVirt/cockpit-machines-ovirt-provider -- This message was sent by Atlassian JIRA (v1000.824.2#100035)

1 0

[JIRA] (OVIRT-1261) Enable travis for github/oVirt/cockpit-machines-ovirt-provider
by eyal edri [Administrator] (oVirt JIRA) 16 Mar '17

16 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1261?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1261: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) What we do in these cases if to give the maintainer admin rights to the repo, so you can add any intergration you'd lilke. I gave you admin rights on the project, so you can enable the travis intergration. > Enable travis for github/oVirt/cockpit-machines-ovirt-provider > -------------------------------------------------------------- > > Key: OVIRT-1261 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1261 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please enable travis for > https://travis-ci.org/oVirt/cockpit-machines-ovirt-provider -- This message was sent by Atlassian JIRA (v1000.824.2#100035)

1 0

[JIRA] (OVIRT-1259) Create new gerrit project: ovirt-containers
by Evgheni Dereveanchin (oVirt JIRA) 16 Mar '17

16 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1259?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1259: --------------------------------------------- New project created, github mirroring enabled: https://gerrit.ovirt.org/#/admin/projects/ovirt-containers [~ybronhei(a)redhat.com] please confirm if it works as expected for you so that we can close this ticket. > Create new gerrit project: ovirt-containers > ------------------------------------------- > > Key: OVIRT-1259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1259 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > Adding infra-support to open a ticket. > On Tue, Mar 14, 2017 at 5:04 PM, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Yes, please do - ovirt-containers , with mirror in github.com/ovirt > > ..important > > > > Thanks. > > > > On Tue, Mar 14, 2017 at 4:26 PM Anton Marchukov <amarchuk(a)redhat.com> > > wrote: > > > >> Hello Yaniv. > >> > >> Renaming projects in gerrit is not possible. Well it is possible through > >> SQL hacks and some DB wrangling following a reindex and thus is far from a > >> standard operation. There is also rename-project plugin that we do not have > >> installed and tested. > >> > >> Instead I can create a new project with the same permissions etc, what do > >> you think? > >> > >> Anton. > >> > >> On Tue, Mar 14, 2017 at 3:18 PM, Yaniv Bronheim <ybronhei(a)redhat.com> > >> wrote: > >> > >> > >> Hi, > >> > >> short version: rename ovirt-container-engine project to ovirt-containers > >> > >> long version: recently we decided to gather all ovirt container under > >> ovirt-containers project instead of splitting it to engine and node. can > >> you please rename the current ovirt-container-engine to ovirt-containers > >> > >> Thanks. > >> -- > >> Yaniv Bronhaim. > >> > >> _______________________________________________ > >> Infra mailing list > >> Infra(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/infra > >> > >> > >> > >> > >> -- > >> Anton Marchukov > >> Senior Software Engineer - RHEV CI - Red Hat > >> > >> -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV 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 (v1000.824.2#100035)

1 0

[JIRA] (OVIRT-1260) Assign dev role to my Jenkins account
by Gil Shinar (oVirt JIRA) 16 Mar '17

16 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1260?page=com.atlassian.jira.… ] Gil Shinar commented on OVIRT-1260: ----------------------------------- Please try now > Assign dev role to my Jenkins account > ------------------------------------- > > Key: OVIRT-1260 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1260 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shmuel Melamud > Assignee: infra > > Hi! > Can you please assign 'dev role' to my Jenkins account (smelamud)? I > need it to run OST Manual job. > Shmuel -- This message was sent by Atlassian JIRA (v1000.824.2#100035)

1 0

[JIRA] (OVIRT-1259) Create new gerrit project: ovirt-containers
by Anton Marchukov (oVirt JIRA) 16 Mar '17

16 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1259?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-1259: -------------------------------------- Assignee: Evgheni Dereveanchin (was: Anton Marchukov) > Create new gerrit project: ovirt-containers > ------------------------------------------- > > Key: OVIRT-1259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1259 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > Adding infra-support to open a ticket. > On Tue, Mar 14, 2017 at 5:04 PM, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Yes, please do - ovirt-containers , with mirror in github.com/ovirt > > ..important > > > > Thanks. > > > > On Tue, Mar 14, 2017 at 4:26 PM Anton Marchukov <amarchuk(a)redhat.com> > > wrote: > > > >> Hello Yaniv. > >> > >> Renaming projects in gerrit is not possible. Well it is possible through > >> SQL hacks and some DB wrangling following a reindex and thus is far from a > >> standard operation. There is also rename-project plugin that we do not have > >> installed and tested. > >> > >> Instead I can create a new project with the same permissions etc, what do > >> you think? > >> > >> Anton. > >> > >> On Tue, Mar 14, 2017 at 3:18 PM, Yaniv Bronheim <ybronhei(a)redhat.com> > >> wrote: > >> > >> > >> Hi, > >> > >> short version: rename ovirt-container-engine project to ovirt-containers > >> > >> long version: recently we decided to gather all ovirt container under > >> ovirt-containers project instead of splitting it to engine and node. can > >> you please rename the current ovirt-container-engine to ovirt-containers > >> > >> Thanks. > >> -- > >> Yaniv Bronhaim. > >> > >> _______________________________________________ > >> Infra mailing list > >> Infra(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/infra > >> > >> > >> > >> > >> -- > >> Anton Marchukov > >> Senior Software Engineer - RHEV CI - Red Hat > >> > >> -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV 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 (v1000.824.2#100035)

1 0