September 2016 - Infra - oVirt List Archives

[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

[JIRA] (OVIRT-729) Jenkins leaves behind connections in ESTABLISHED state
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-729?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-729: -------------------------------------------- Epic Link: OVIRT-403 > Jenkins leaves behind connections in ESTABLISHED state > ------------------------------------------------------ > > Key: OVIRT-729 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-729 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > Throughout the last days I noticed several times when a slave got non-responsive and after rebooting it never recovered until being removed/re-added to Jenkins. > Further investigation on el7-vm06.phx.ovirt.org revealed that on Jenkins the connection is still marked as "ESTABLISHED" hours after the slave crashed and rebooted: > {quote} > tcp6 0 0 66.187.230.92:33374 66.187.230.77:22 ESTABLISHED 14625/java > {quote} > Due to this new SSH connections are not opened and Jenkins can't reconnect to the slave. > I didn't see this behavior before, maybe it is related to the latest security upgrade of jenkins. -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-725) install secondary MX server
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-725?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-725: -------------------------------------------- Epic Link: OVIRT-403 > install secondary MX server > --------------------------- > > Key: OVIRT-725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-725 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Mailing lists (Mailman) > Reporter: Evgheni Dereveanchin > Assignee: infra > > We currently just have a single MX record and mail server. For better reliability it's a good idea to set up a secondary MX that would act as a relay. This can help during primary MX maintenance as mail will be accumulated on the secondary MX and flushed to the primary once that comes up. -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-516) Yamlize jenkins-old.ovirt.org jobs
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-516?page=com.atlassian.jira.p… ] eyal edri [Administrator] closed OVIRT-516. ------------------------------------------- > Yamlize jenkins-old.ovirt.org jobs > ---------------------------------- > > Key: OVIRT-516 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-516 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Reporter: Nadav Goldin > Assignee: infra > Labels: jenkins, jobs > Fix For: OVIRT-INFRA-JUN-2016 > > > This ticket is for tracking none-yamlized jobs we have left in http://jenkins-old.ovirt.org and should be yamlized. > h5. Confirmed needed(and should be enabled in jenkins-old) > # manual build jobs ( we need to think if these are needed, if so, they should probably use a common yaml template ) > mom_any_create-rpms_manual > ovirt-dwh_any_create-rpms_manual > ovirt-engine-cli_any_create-rpms_manual > ovirt-host-deploy_any_create-rpms_manual > ovirt-iso-uploader_any_create-rpms_manual > ovirt-reports_any_create-rpms_manual > ovirt-setup-lib_any_create-rpms_manual > ovirt-vmconsole_any_create-rpms_manual > vdsm-jsonrpc-java_any_create-rpms_manual > vdsm_any_create-rpms_manual > ovirt-log-collector_any_create-rpms_manual > ovirt-hosted-engine-ha_any_create-rpms_manual > ovirt-hosted-engine-setup_any_create-rpms_manual > ovirt-image-uploader_any_create-rpms_manual > ovirt-engine-extension-aaa-ldap_any_create-rpms_manual > ovirt-engine-extension-aaa-misc_any_create-rpms_manual > ovirt-engine-extension-logger-log4j_any_create-rpms_manual > otopi_any_create-rpms_manual > # repo closure > repos_master_check-closure_merged > repos_3.6_check-closure_merged > spagobi_repo_merged (not sure if needed) > # should be moved to STD CI > ovirt-live_3.6-create-iso > ovirt-live_master-create-iso > vdsm_master_verify-error-codes_merged -> should be in vdsm check-patch/merge (std ci) > infra-puppet_production_check-puppet-manifests_gerrit > # in progress of moving to STD CI, should keep enabled on old jenkins until done > ovirt-engine_3.6_dao-unit-tests_created > ovirt-engine_3.6_dao-unit-tests_merged > ovirt-engine_master_dao-unit-tests_created > ovirt-engine_master_dao-unit-tests_merged > ovirt-engine_master_find-bugs_gerrit > ovirt-engine_master_find-bugs_merged > ovirt-engine_master_find-bugs_gerrit > ovirt-engine_3.6_find-bugs_gerrit > ovirt-engine_3.6_find-bugs_merged > # general jobs > ovirt-engine_master_coverity-analysis_merged > system_update_puppet ( should be part of STD CI for puppet repo?) > system_restart-gerrit-service > h5. Still unmapped jobs > ovirt-appliance_for-testing_build-artifacts-el7-x86_64 > ovirt-setup-lib_unit-tests > qemu-kvm-rhev_create-rpms_el6 > validate_open_sources_licenses_ovirt > h5. Jobs that can be deleted after putting rpms in static-repo > vhostmd_create-rpms_el6 > vhostmd_create-rpms_el7 -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0