- Infra - oVirt List Archives

[JIRA] (OVIRT-733) ovirt-node-ng leftover libvirt settings
by Evgheni Dereveanchin (oVirt JIRA) 19 Sep '16

19 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-733?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-733: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > ovirt-node-ng leftover libvirt settings > --------------------------------------- > > Key: OVIRT-733 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-733 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Low > > I was working on node updates and troubleshooting OVIRT-630 when I came across errors like this in the logs on a freshly booted EL7 slave: > {{ > Sep 19 15:10:07 el7-vm16 libvirtd[1239]: libvirt version: 1.2.17, package: 13.el7_2.5 (CentOS BuildSystem <http://bugs.centos.org>, 2016-06-23-14:23:27, worker1.bsys.centos.org) > Sep 19 15:10:07 el7-vm16 libvirtd[1239]: cannot open path '/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng': No such file or directory > Sep 19 15:10:07 el7-vm16 libvirtd[1239]: Failed to autostart storage pool 'ovirt-node-ng': cannot open path '/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng': No such file or directory > }} > Looks like ovirt-node-ng_master_build-artifacts-el7-x86_64 is leaving behind storage pool configurations. Opening this to investigate further, even though I doubt it affects anything at the moment. -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-733) ovirt-node-ng leftover libvirt settings
by Evgheni Dereveanchin (oVirt JIRA) 19 Sep '16

19 Sep '16

Evgheni Dereveanchin created OVIRT-733: ------------------------------------------ Summary: ovirt-node-ng leftover libvirt settings Key: OVIRT-733 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-733 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low I was working on node updates and troubleshooting OVIRT-630 when I came across errors like this in the logs on a freshly booted EL7 slave: {{ Sep 19 15:10:07 el7-vm16 libvirtd[1239]: libvirt version: 1.2.17, package: 13.el7_2.5 (CentOS BuildSystem <http://bugs.centos.org>, 2016-06-23-14:23:27, worker1.bsys.centos.org) Sep 19 15:10:07 el7-vm16 libvirtd[1239]: cannot open path '/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng': No such file or directory Sep 19 15:10:07 el7-vm16 libvirtd[1239]: Failed to autostart storage pool 'ovirt-node-ng': cannot open path '/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng': No such file or directory }} Looks like ovirt-node-ng_master_build-artifacts-el7-x86_64 is leaving behind storage pool configurations. Opening this to investigate further, even though I doubt it affects anything at the moment. -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
by Vojtech Szocs (oVirt JIRA) 19 Sep '16

19 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.p… ] Vojtech Szocs commented on OVIRT-416: ------------------------------------- > So the question is, can we reduce this to 1-2 permutations? if this is just going to nightly / hourly repo then we don't need all these permutations and we'll enjoy a much faster verification on the experimental flow which collects artifacts from build-artifacts jobs. +1 Full GWT build (all browsers & languages) is not needed for oVirt nightly (snapshot) builds. It's only needed for oVirt official (release) builds. > We are now adding the 'build official manual' option to standard CI, so we can keep the 27 permutations there for official builds. Sounds good to me. > [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any > ------------------------------------------------------------------------------------- > > Key: OVIRT-416 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > > Right now most projects just rebuild twice the artifacts, what for some means a big waste of resources, if we could just reuse what was built previously there would be no rebuilding. > Something to take into account is that the distributions that check-merged and build-artifacts run for might not match, so you can be running check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an example), maybe we should not allow different distros on each stage?| -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-732) Build oVirt 4.0.4 RC4
by sbonazzo (oVirt JIRA) 19 Sep '16

19 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-732?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-732: --------------------------- Assignee: sbonazzo (was: infra) Status: In Progress (was: To Do) > Build oVirt 4.0.4 RC4 > --------------------- > > Key: OVIRT-732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-732 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: sbonazzo > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-732) Build oVirt 4.0.4 RC4
by sbonazzo (oVirt JIRA) 19 Sep '16

19 Sep '16

sbonazzo created OVIRT-732: ------------------------------ Summary: Build oVirt 4.0.4 RC4 Key: OVIRT-732 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-732 Project: oVirt - virtualization made easy Issue Type: Task Components: Repositories Mgmt Reporter: sbonazzo Assignee: infra Priority: Highest -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-732) Build oVirt 4.0.4 RC4
by sbonazzo (oVirt JIRA) 19 Sep '16

19 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-732?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-732: --------------------------- Epic Link: OVIRT-411 > Build oVirt 4.0.4 RC4 > --------------------- > > Key: OVIRT-732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-732 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

oVirt 4.0.4 RC4 merge / branch / tag / bugzilla reminder
by Sandro Bonazzola 19 Sep '16

19 Sep '16

All stable branch maintainers, please make sure to - merge all relevant open bugs until Tuesday morning 11:00 AM TLV time. For each package that need to be built (i.e oVirt product) please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.4.4, tr: 4.0.4.4) A list of bugs that require attention is here: - https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016>

1 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
by sbonazzo (oVirt JIRA) 19 Sep '16

19 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] sbonazzo commented on OVIRT-226: -------------------------------- [~eedri] this is handed by QE, see referenced bugzilla. > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: sbonazzo > Assignee: infra > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

oVirt infra daily report - unstable production jobs - 81
by jenkins＠jenkins.phx.ovirt.org 19 Sep '16

19 Sep '16

------=_Part_260_564244070.1474239608272 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/81//artifact/exported-ar… Cheers, Jenkins ------=_Part_260_564244070.1474239608272 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 - 18/09/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/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_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/fabric-ovirt_master_check-merged-fc23-x86_64/">fabric-ovirt_master_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/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-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-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-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-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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/repos_master_check-closure_fc24_merged/">repos_master_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/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> ------=_Part_260_564244070.1474239608272--

1 0

[JIRA] (OVIRT-726) increase max number of concurrent builds
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-726?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-726: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > increase max number of concurrent builds > ---------------------------------------- > > Key: OVIRT-726 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-726 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > I saw the build queue rise to ~200 tasks today due to these two jobs configured for running only 6 builds in parallel: > ovirt-engine_master_upgrade-from-4.0_el7_created > ovirt-engine_master_upgrade-from-master_el7_created > I bumped the default limit to 10 in https://gerrit.ovirt.org/61319/ but engine-upgrade job override this setting 6: > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/yaml/temp… > there's more places where various limits are set - I think we should review them and even remove if possible as the number of slaves is going to increase. > git grep max-total > jobs/confs/projects/defaults.yaml: max-total: 3 > jobs/confs/projects/defaults.yaml: max-total: 3 > jobs/confs/projects/ovirt/publish-rpms-nightly-3.6.yaml: max-total: 3 > jobs/confs/projects/ovirt/publish-rpms-nightly-4.0.yaml: max-total: 3 > jobs/confs/projects/ovirt/publish-rpms-nightly-master.yaml: max-total: 3 > jobs/confs/yaml/templates/engine-upgrade.yaml: max-total: 6 > jobs/confs/yaml/templates/find-bugs.yaml: max-total: 3 > jobs/confs/yaml/templates/install-rpm-sanity.yaml: max-total: 3 > jobs/confs/yaml/templates/ovirt-node-job-templates.yaml: max-total: 3 > jobs/confs/yaml/templates/standard-stage.yaml: max-total: 10 > jobs/confs/yaml/templates/standard-stage.yaml: max-total: 1 -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0