- Infra - oVirt List Archives

[JIRA] (OVIRT-648) install new oVirt in PHX
by Evgheni Dereveanchin (oVirt JIRA) 21 Jul '16

21 Jul '16

Evgheni Dereveanchin created OVIRT-648: ------------------------------------------ Summary: install new oVirt in PHX Key: OVIRT-648 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-648 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra There are several tickets open (OVIRT-291, OVIRT-558, etc) which relate to the current Hosted Engine setup: 1) Engine is 3.5 and needs updating 2) Engine is running on Fedora 19 (EOL) 3) All storage domains are running on the same NFS export 4) Jenkins VMs are running on top of DRBD backed volumes 5) RAID5 is used on storage which is not good for writes As all the components need to be changed it's simpler to rebuild the whole setup altogether, then move critical VMs and rebuild the slaves. This is a tracker case to plan and perform the process. -- This message was sent by Atlassian JIRA (v1000.148.3#100005)

1 0

Base Squid Configuration for Repo Mirroring
by Anton Marchukov 21 Jul '16

21 Jul '16

Hello All. I tried to look some available solutions for transparent (read low maintenance) repository caching and the best thing I have found is the one from Ubuntu available here: https://wiki.ubuntu.com/SquidDebProxy Basically it is fully based on squid with some auto configuration and additional service discovery capabilities. Do not need to use it in full at all, but we can use the config available there as a base point to review and start with: http://bazaar.launchpad.net/~mvo/+junk/squid-deb-proxy/view/head:/squid-deb… I also think we do not need acl to limit it to the domains as we have several repos used and they are added/removed along the way. So we can try with simply file type based acls. Then if we wisely setup our stats collection we should be able to asses how it perform and if any problems identified - try to address them individually. Those are my 2 cents. Anton. -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

2 2

[JIRA] (OVIRT-646) bad job [webadmin: remove tooltip underline from table column headers]
by eyal edri [Administrator] (oVirt JIRA) 21 Jul '16

21 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-646?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-646: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) > bad job [webadmin: remove tooltip underline from table column headers] > ---------------------------------------------------------------------- > > Key: OVIRT-646 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-646 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: Shlomo Ben David > > This job seems to be broken. > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… > """ > [ INFO ] Checking for an update for Setup... > An update for the Setup packages ovirt-engine-setup > ovirt-engine-setup-plugin-websocket-proxy was found. Please update > that package by running: > "yum update ovirt-engine-setup > ovirt-engine-setup-plugin-websocket-proxy" > and then execute Setup again. > [ ERROR ] Failed to execute stage 'Environment customization': Please > update the Setup packages > [ INFO ] Stage: Clean up > Log file is located at > /var/log/ovirt-engine/setup/ovirt-engine-setup-20160721011950-b2qajq.log > [ INFO ] Generating answer file > '/var/lib/ovirt-engine/setup/answers/20160721012010-setup.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > [ ERROR ] Execution of setup failed > + echo '########## SETUP_FAILED' > ########## SETUP_FAILED > + return 1 > + show_error > + [[ SETUP::INSTALLING_ENGINE == \F\I\N\I\S\H\E\D ]] > + echo 'FAILED::SETUP::INSTALLING_ENGINE:: Unrecoverable failure, exitting' > FAILED::SETUP::INSTALLING_ENGINE:: Unrecoverable failure, exitting > Build step 'Execute shell' marked build as failure > Performing Post build task... > Match found for :.* : True > Logical operation result is TRUE > Running script : #!/bin/bash -x > echo "shell-scripts/ovirt-engine_upgrade-engine.cleanup.sh" > # > # Parameters: > # > # version > # > # version to upgrade to > # > """ > ---------- Forwarded message ---------- > From: Jenkins CI <gerrit2(a)gerrit.ovirt.org> > Date: Wed, Jul 20, 2016 at 9:27 PM > Subject: Change in ovirt-engine[master]: webadmin: remove tooltip underline > from table column headers > To: Greg Sheremeta <gshereme(a)redhat.com>, Scott Dickerson < > sdickers(a)redhat.com> > Jenkins CI has posted comments on this change. > Change subject: webadmin: remove tooltip underline from table column headers > ...................................................................... > Patch Set 3: > Build Failed > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… > : FAILURE > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/10… > : SUCCESS > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… > : SUCCESS > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc24-x86_64/1… > : SUCCESS > http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_merged/268/ : > SUCCESS > -- > To view, visit https://gerrit.ovirt.org/61000 > To unsubscribe, visit https://gerrit.ovirt.org/settings > Gerrit-MessageType: comment > Gerrit-Change-Id: Ic1f393ec5f63580f928b8b9eacbe32ad2b04cf10 > Gerrit-PatchSet: 3 > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-Owner: Scott Dickerson <sdickers(a)redhat.com> > Gerrit-Reviewer: Alexander Wels <awels(a)redhat.com> > Gerrit-Reviewer: Greg Sheremeta <gshereme(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Oved Ourfali <oourfali(a)redhat.com> > Gerrit-Reviewer: Scott Dickerson <sdickers(a)redhat.com> > Gerrit-Reviewer: Vojtech Szocs <vszocs(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.148.3#100005)

2 1

[JIRA] (OVIRT-647) ovirt-engine-dashboard_4.0_build-artifacts-f*-x86_64 not exporting src.rpm
by eyal edri [Administrator] (oVirt JIRA) 21 Jul '16

21 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-647?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-647: ----------------------------------------------- Assignee: vszocs (was: infra) Vojtech, let me know if you need help from the infra team, this should be done in the standard ci code, under automation dir. > ovirt-engine-dashboard_4.0_build-artifacts-f*-x86_64 not exporting src.rpm > -------------------------------------------------------------------------- > > Key: OVIRT-647 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-647 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: vszocs > > ovirt-engine-dashboard_4.0_build-artifacts-f*-x86_64 jobs are not exporting > src.rpm > -- > 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.148.3#100005)

1 0

[JIRA] (OVIRT-647) ovirt-engine-dashboard_4.0_build-artifacts-f*-x86_64 not exporting src.rpm
by sbonazzo (oVirt JIRA) 21 Jul '16

21 Jul '16

sbonazzo created OVIRT-647: ------------------------------ Summary: ovirt-engine-dashboard_4.0_build-artifacts-f*-x86_64 not exporting src.rpm Key: OVIRT-647 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-647 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra ovirt-engine-dashboard_4.0_build-artifacts-f*-x86_64 jobs are not exporting src.rpm -- 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.148.3#100005)

1 0

[JIRA] (OVIRT-646) bad job [webadmin: remove tooltip underline from table column headers]
by Greg Sheremeta (oVirt JIRA) 21 Jul '16

21 Jul '16

Greg Sheremeta created OVIRT-646: ------------------------------------ Summary: bad job [webadmin: remove tooltip underline from table column headers] Key: OVIRT-646 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-646 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra This job seems to be broken. http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… """ [ INFO ] Checking for an update for Setup... An update for the Setup packages ovirt-engine-setup ovirt-engine-setup-plugin-websocket-proxy was found. Please update that package by running: "yum update ovirt-engine-setup ovirt-engine-setup-plugin-websocket-proxy" and then execute Setup again. [ ERROR ] Failed to execute stage 'Environment customization': Please update the Setup packages [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160721011950-b2qajq.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160721012010-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed + echo '########## SETUP_FAILED' ########## SETUP_FAILED + return 1 + show_error + [[ SETUP::INSTALLING_ENGINE == \F\I\N\I\S\H\E\D ]] + echo 'FAILED::SETUP::INSTALLING_ENGINE:: Unrecoverable failure, exitting' FAILED::SETUP::INSTALLING_ENGINE:: Unrecoverable failure, exitting Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -x echo "shell-scripts/ovirt-engine_upgrade-engine.cleanup.sh" # # Parameters: # # version # # version to upgrade to # """ ---------- Forwarded message ---------- From: Jenkins CI <gerrit2(a)gerrit.ovirt.org> Date: Wed, Jul 20, 2016 at 9:27 PM Subject: Change in ovirt-engine[master]: webadmin: remove tooltip underline from table column headers To: Greg Sheremeta <gshereme(a)redhat.com>, Scott Dickerson < sdickers(a)redhat.com> Jenkins CI has posted comments on this change. Change subject: webadmin: remove tooltip underline from table column headers ...................................................................... Patch Set 3: Build Failed http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… : FAILURE http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/10… : SUCCESS http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… : SUCCESS http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc24-x86_64/1… : SUCCESS http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_merged/268/ : SUCCESS -- To view, visit https://gerrit.ovirt.org/61000 To unsubscribe, visit https://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ic1f393ec5f63580f928b8b9eacbe32ad2b04cf10 Gerrit-PatchSet: 3 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Scott Dickerson <sdickers(a)redhat.com> Gerrit-Reviewer: Alexander Wels <awels(a)redhat.com> Gerrit-Reviewer: Greg Sheremeta <gshereme(a)redhat.com> Gerrit-Reviewer: Jenkins CI Gerrit-Reviewer: Oved Ourfali <oourfali(a)redhat.com> Gerrit-Reviewer: Scott Dickerson <sdickers(a)redhat.com> Gerrit-Reviewer: Vojtech Szocs <vszocs(a)redhat.com> Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> Gerrit-HasComments: No -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.148.3#100005)

1 0

[oVirt Jenkins] ovirt-engine_master_upgrade-from-4.0_el7_merged - Build # 638 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Jul '16

21 Jul '16

------=_Part_411_1804225994.1469064032608 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… Build Number: 638 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/61000 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #638 [Scott J Dickerson] webadmin: remove tooltip underline from table column headers ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_411_1804225994.1469064032608--

1 0

RHEVM CI Jenkins daily report - 20
by jenkins＠jenkins.phx.ovirt.org 21 Jul '16

21 Jul '16

------=_Part_409_446041513.1469055603607 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/20//artifact/exported-ar… Cheers, Jenkins ------=_Part_409_446041513.1469055603607 Content-Type: application/octet-stream; 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 - 20/07/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-fc22-x…">ovirt-node-ng_ovirt-3.6_build-artifacts-fc22-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-node-plugin-hosted-engine_ovirt-3.6_chec…">ovirt-node-plugin-hosted-engine_ovirt-3.6_check-merged-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/vdsm_3.6_check-merged-fc23-x86_64/">vdsm_3.6_check-merged-fc23-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/vdsm_4.0_check-merged-el7-x86_64/">vdsm_4.0_check-merged-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/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-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/vdsm_master_check-merged-el7-x86_64/">vdsm_master_check-merged-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/vdsm_master_check-merged-fc24-x86_64/">vdsm_master_check-merged-fc24-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> ------=_Part_409_446041513.1469055603607--

1 0

Let's Consider Having Three Separated Environments in Infra
by Anton Marchukov 20 Jul '16

20 Jul '16

Hello All. This is a follow up to the meeting minutes. Just to record my thoughts to consider during the actual design. To make it straight. I think we need to target creation of 3 (yes, three) independent and completely similar setups with as less shared parts as possible. If we choose to go with reliability on service level than we do need 3 because: 1. If we mess up with one environment (e,g, storage will be completely dead there) we will have 2 left working that gives us a reliability still because one of them can fail. So it will move us out of crunch mode into the regular work mode. 2. All consensus based algorithms generally require at least 2N+1 instances unless they utilize some special mode. The lowest is N=1 that is 3 and it would make sense to distribute them into different environments. I know the concern for having even 2 envs was that we will spend more effort to maintain them. But I think the opposite is true. Having 3 is actually less effort to maintain if we make them similar because of: 1. We can do gradual canary update, Same as with failure. You can test update on 1 instance leaving 2 left running that still provides reliability. So upgrade is no longer time constrained and safe. 2. If environments are similar then once we establish the correct playbook for one we can just apply it for second and later for third. So this overhead is not tripled in fact and if automated than it is no additional effort at all. 3. We are more open to test and play with one. We can even destroy it recreate from scratch, etc. Indirectly this will reduce our effort. I think the only real problem with it is the initial step when we should design an ideal hardware and network layout for that. But once it is done it will be easier to go with 3 environments. Also it may be possible to design the plan the way that we start with just one and later convert it into three. Anton. -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

2 2

Building for fc23 fails on yum package install
by Vojtech Szocs 20 Jul '16

20 Jul '16

Hi, we're trying to build Dashboard 1.0.0-1 and for fc23 the build fails: 16:26:03 INFO: installing package(s): ovirt-engine-nodejs ovirt-engine-nodejs-modules 16:26:03 ERROR: Command failed. See logs for output. 16:26:03 # /usr/bin/yum-deprecated --installroot /var/lib/mock/fedora-23-x86_64-84590ba0ae0d50bf8fb4605dac9e1a22-7835/root/ --releasever 23 install ovirt-engine-nodejs ovirt-engine-nodejs-modules --setopt=tsflags=nocontexts 16:26:03 Install packages took 2 seconds http://jenkins.ovirt.org/job/ovirt-engine-dashboard_4.0_check-patch-fc23-x8… Is this an infra issue? I'll try to retrigger the build in the meantime. Thanks, Vojtech

2 2