July 2017 - Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 392
by jenkins＠jenkins.phx.ovirt.org 24 Jul '17

24 Jul '17

------=_Part_273_1517028123.1500850802632 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/392//artifact/exported-a… Cheers, Jenkins ------=_Part_273_1517028123.1500850802632 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 - 23/07/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_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_he-system-tests/">ovirt_master_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> ------=_Part_273_1517028123.1500850802632--

1 0

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

23 Jul '17

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

1 1

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by danken (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] danken commented on OVIRT-1549: ------------------------------- They do release RPMs as part of RDO https://trunk.rdoproject.org/centos7-master/current/ but not per patch. If ovirt-infra does not have resources to have this per patch, we can start with a nightly run. ovsdbapp said that they can wait 40 minutes for our vote. > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1157) Re-factor the standard-CI triggers file
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1157?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1157: ----------------------------------- Assignee: Barak Korren (was: infra) > Re-factor the standard-CI triggers file > --------------------------------------- > > Key: OVIRT-1157 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1157 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: standard-ci > > The {{/jobs/confs/yaml/triggers/standard.yaml}} file contains A LOT of needless code duplication. We need to re-factor it with templates and YAML inheritance. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1549: ------------------------------------- If they don't release RPMs, how are our users supposed to consume this? The point of OST is to emulate what the user does, so 1st decide what the user does... Also WRT CI-1 on Gerrit, OST was never designed to do this, it takes far too long and far too many resources to be reasonable to run for every patch set. This is why we keep the process semi-automatic even for oVirt's own repos... > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by danken (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] danken commented on OVIRT-1549: ------------------------------- Sorry for missing the link to gerrit: https://review.openstack.org/#/q/project:openstack/ovsdbapp * I believe they build RPMs daily from merged code, but... * I don't think they currently release them officially * I want ovsdbapp to get a CI-1 if they break OST. I think that means "tracking the project at the source level". I believe that ovsdbapp would not mind adding automation/build-artefacts.sh if this is required > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1549: ------------------------------------- Without going into too much detail yet, the instruction you posted seem to refer to Gerrit projects, while the project you linked to is on GitHub? Is that project actually maintained in Gerrit? If so, where? Some more questions: * Does the project build RPMs? * Are those RPMs officially released somewhere? * Do we really want to track the project at the source level? If so, will the maintainers be willing to add an 'automation' directory and the related scripts? > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 298 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jul '17

23 Jul '17

------=_Part_245_434408739.1500696006298 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build Number: 298 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #298 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_245_434408739.1500696006298--

1 2

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by danken (oVirt JIRA) 23 Jul '17

23 Jul '17

danken created OVIRT-1549: ----------------------------- Summary: run OST as a third-party tester for OpenStack's ovsdbapp Key: OVIRT-1549 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: infra https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0

[JIRA] (OVIRT-1548) Better STD-CI for GitHub
by Barak Korren (oVirt JIRA) 23 Jul '17

23 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1548?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1548: ----------------------------------- Assignee: Barak Korren (was: infra) > Better STD-CI for GitHub > ------------------------ > > Key: OVIRT-1548 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1548 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > Labels: github, standard-ci > > We currently have some support for crating STD-CI jobs for projects running on GitHub. There are however, several issues with it: > * The job templates you use for GitHub are different then the ones you use for Gerrit: > ** Job names need to contain '\-github-' > ** In Gerrit you need a separate 'project' entry for the 'build-artifacts' jobs, in GitHub you need a separate one for 'check-patch'. > ** SCM checkout details are specified in the 'project' entry as opposed to a separate SCM file (We might want to adopt this for Gerrit). > * The 'check-patch' jobs do not have full STC-CI. They don't run the post-build steps. > * The triggering scheme is strange: > ** All jobs trigger when certain messages are posted in the PR comments. > ** Nothing is triggered automatically (As opposed to Gerrit where CI runs as soon as a patchset is submitted) > ** Nothing triggers when a PR is merged (As opposed to with Gerrit where 'check-merged' and 'build-artifacts' are triggered on merge). > * The white-listing scheme is different: > ** The 'jenkins-whiltelist' file does not effect theses jobs at all. > ** GitHub project/organisation membership determines white-listing > ** white-listing is determined by who added the comment to run CI, not who authored the patch. > Some of these issues and differences had already been tracked in other tickets. This ticket is for concentrating all related work. Other related tickets will be linked to it as blockers. -- This message was sent by Atlassian JIRA (v1000.1131.0#100055)

1 0