- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 216 - Failure!
by jenkins＠jenkins.phx.ovirt.org 13 May '16

13 May '16

------=_Part_257_323440134.1463125914290 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build Number: 216 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57387 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #216 [Vinzenz Feenstra] Add Red Hat Atomic as an operating system ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_257_323440134.1463125914290--

1 0

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 221 - Failure!
by jenkins＠jenkins.phx.ovirt.org 13 May '16

13 May '16

------=_Part_255_891470098.1463125444006 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… Build Number: 221 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57387 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #221 [Vinzenz Feenstra] Add Red Hat Atomic as an operating system ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_255_891470098.1463125444006--

1 0

ovirt-srv11
by Nadav Goldin 13 May '16

13 May '16

Hi, ovirt-srv11 host is in an empty cluster called 'Production_CentOS', its quite a strong machine with 251GB of ram, currently it has no VMs and as far as I can tell isn't used at all. I want to move it to the 'Jenkins_CentOS' cluster in order to add more VMs and later upgrade the older clusters to el7(if we have enough slaves in the Jenkins_CentOS cluster, we could just take the VMs down in the Jenkins cluster and upgrade). this is unrelated to the new hosts ovirt-srv17-26. I'm not sure why it was put there, so posting here if anyone objects or I'm missing something Thanks Nadav.

4 11

CI cleanup failure
by Nir Soffer 11 May '16

11 May '16

This ioprocess build failed with ci related issue: http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-el7-x86_64/1/ 12:18:34 + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) 12:18:34 ++ mount 12:18:34 ++ awk '{print $3}' 12:18:34 ++ grep /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b 12:18:34 + [[ -n /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc ]] 12:18:34 + echo 'Found mounted dirs inside the chroot /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b.' 'Trying to umount.' 12:18:34 Found mounted dirs inside the chroot /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b. Trying to umount. 12:18:34 + for mount in '"${mounts[@]}"' 12:18:34 + sudo umount /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc 12:18:34 umount: /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc: target is busy. 12:18:34 (In some cases useful info about processes that use 12:18:34 the device is found by lsof(8) or fuser(1)) 12:18:34 + echo 'ERROR: Failed to umount /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc.' 12:18:34 ERROR: Failed to umount /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc. We should check why the mountpoint is busy, but a quick fix may be using the --lazy option: umount --lazy /mountpoint Nir

2 3

restricting check patch/merged parallel jobs
by Eyal Edri 11 May '16

11 May '16

Is there any reason we're limiting the amount of check patch & check merged jobs to run only 3 in parallel? Each jobs runs in mock and on its own VM, anything presenting us from removing this limitation so we won't have idle slaves while other jobs are in the queue? We can increase it at least to a higher level if we won't one specific job to take over all slaves and starve other jobs, but i think ovirt-engine jobs are probably the biggest consumer of ci, so the threshold should be updated. -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

4 8

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 206 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 May '16

11 May '16

------=_Part_243_1737338687.1462968895367 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build Number: 206 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57190 ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_243_1737338687.1462968895367--

1 0

CI testes are failing , please check
by Eli Mesika 11 May '16

11 May '16

Hi CI tests are failing For example : https://gerrit.ovirt.org/#/c/53790/ Please handle ASAP Thanks Eli

2 3

Re: [ovirt-devel] Doing a mock ovirt-engine build for epel7 on fedora 23 hangs
by Eyal Edri 11 May '16

11 May '16

Adding infra, i think its a known issue which we hit on ci as well On May 10, 2016 12:53 PM, "Roman Mohr" <rmohr(a)redhat.com> wrote: > Hi, > > My mock rpm builds hang on the line > > Downloading: > > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2.8… > > Does anyone else have similar issues when building inside mock for > epel7 on a fedora 23 machine?\ > > Best Regards, > Roman > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > > >

2 1

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 179 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 May '16

11 May '16

------=_Part_235_341865771.1462904980080 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… Build Number: 179 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/56531 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #179 [Shahar Havivi] Engine: KVM v2v - no need to ask for ovf for KVM vms ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_235_341865771.1462904980080--

2 2

[JIRA] (OVIRT-307) [gerrit][policy] re-enable -1/-verfiy policy for created patches
by eyal edri [Administrator] (oVirt JIRA) 11 May '16

11 May '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-307?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-307: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) not sure if still relevant, but as part of the new tasks for new hooks, worth reviewing existing hooks and checking which one gives -1 and which only warnings. > [gerrit][policy] re-enable -1/-verfiy policy for created patches > ---------------------------------------------------------------- > > Key: OVIRT-307 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-307 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > Jenkins CI has been much more stable during the past weeks. > we want to make it even better. > we can do that by re-enabling gerrit enforcement for stable 'created' jobs gradually in order to prevent any production 'merged' job being broken. > some criteria/guidelines: > \\- start only with 'master' jobs (1-2 a week) > \\- make sure the relevant maintainer/group is aware > \\- make sure the team leader/manager has permissions to remove \-1 > (we'll remove this option at one point or minimize it to specific > people, like stable branch maintainers) > \\- change should be done via yaml > \\- communicate change on devel and infra lists > list of stable jobs can be found via the jenkins api/history. -- This message was sent by Atlassian JIRA (v1000.5.2#72002)

1 0