- Infra - oVirt List Archives

[JIRA] (OVIRT-1760) upgrade jenkins.ovirt.org to latest LTS version
by Evgheni Dereveanchin (oVirt JIRA) 13 Nov '17

13 Nov '17

This is a multi-part message in MIME format... ------------=_1510574524-19165-106 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1760?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1760: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > upgrade jenkins.ovirt.org to latest LTS version > ----------------------------------------------- > > Key: OVIRT-1760 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1760 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Jenkins 2.73.3 LTS is out, our instance needs to be updated. > The upgrade will close vulnerabilities found in the recent security advisory: > https://jenkins.io/security/advisory/2017-11-08/ > Plugins, such as github-api and BlueOpean will also be updated. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510574524-19165-106 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1760?page=com.atlassian.jira.… ]</pre> <h3>Evgheni Dereveanchin reassigned OVIRT-1760:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>upgrade jenkins.ovirt.org to latest LTS version</h3> <pre> Key: OVIRT-1760 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1760 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: Evgheni Dereveanchin</pre> <p>Jenkins 2.73.3 LTS is out, our instance needs to be updated. The upgrade will close vulnerabilities found in the recent security advisory: <a href="https://jenkins.io/security/advisory/2017-11-08/">https://jenkins.io/security/advisory/2017-11-08/</a> Plugins, such as github-api and BlueOpean will also be updated.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1510574524-19165-106--

1 0

[JIRA] (OVIRT-1760) upgrade jenkins.ovirt.org to latest LTS version
by Evgheni Dereveanchin (oVirt JIRA) 13 Nov '17

13 Nov '17

Evgheni Dereveanchin created OVIRT-1760: ------------------------------------------- Summary: upgrade jenkins.ovirt.org to latest LTS version Key: OVIRT-1760 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1760 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Jenkins 2.73.3 LTS is out, our instance needs to be updated. The upgrade will close vulnerabilities found in the recent security advisory: https://jenkins.io/security/advisory/2017-11-08/ Plugins, such as github-api and BlueOpean will also be updated. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[CQ]: 83986, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Nov '17

13 Nov '17

A system test invoked by the "ovirt-master" change queue including change 83986,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 83849,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 83849,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83986/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83849/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3791/

1 0

oVirt 4.1.9 will be the last 4.1 release
by Sandro Bonazzola 13 Nov '17

13 Nov '17

Hi, we are now targeting oVirt 4.2.0 GA around December 12th and oVirt 4.1.8 around December 5th. Against tradition that would have set 4.1.8 as last 4.1 release, this round we'll release also oVIrt 4.1.9 being it already in development just before 4.2.0 GA. We suggest to be prepared to upgrade to 4.2 since 4.1 won't receive any further update after 4.1.9 release. -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>

1 0

[CQ]: 83477, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Nov '17

13 Nov '17

A system test invoked by the "ovirt-master" change queue including change 83477,10 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 83849,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 83849,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/83477/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83849/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3788/

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-snapshot_build-artifacts-el7-x86_64 - Build # 70 - Failure!
by jenkins＠jenkins.phx.ovirt.org 13 Nov '17

13 Nov '17

------=_Part_197_1882967440.1510477197099 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-snapshot_build-artifac… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-snapshot_build-artifac… Build Number: 70 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #70 [Yuval Turgeman] automation: view install log in console output ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_197_1882967440.1510477197099--

1 1

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order
by Barak Korren (oVirt JIRA) 13 Nov '17

13 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1759: -------------------------------- Description: Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. Here is en example of such an occurance. The following patches were merged in the order specified below: # https://gerrit.ovirt.org/c/83917 # https://gerrit.ovirt.org/c/83918 # https://gerrit.ovirt.org/c/83919 # https://gerrit.ovirt.org/c/83920 The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) This resulted in CQ 'add' command running in the wrong order: # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) We need to come up with a way to make the system properly preserver order. was: Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. Here is en example of such an occurance. The following patches were merged in the order specified below: # https://gerrit.ovirt.org/c/83917 # https://gerrit.ovirt.org/c/83918 # https://gerrit.ovirt.org/c/83919 # https://gerrit.ovirt.org/c/83920 The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) We need to come up with a way to make the system properly preserver order. > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order
by Barak Korren (oVirt JIRA) 13 Nov '17

13 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1759: -------------------------------- Epic Link: OVIRT-400 > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order
by Barak Korren (oVirt JIRA) 13 Nov '17

13 Nov '17

Barak Korren created OVIRT-1759: ----------------------------------- Summary: Gerrit patches can reach CQ out-of-order Key: OVIRT-1759 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: High Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. Here is en example of such an occurance. The following patches were merged in the order specified below: # https://gerrit.ovirt.org/c/83917 # https://gerrit.ovirt.org/c/83918 # https://gerrit.ovirt.org/c/83919 # https://gerrit.ovirt.org/c/83920 The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 601 - Failure!
by jenkins＠jenkins.phx.ovirt.org 13 Nov '17

13 Nov '17

------=_Part_199_1808796376.1510478321840 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 601 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #601 [Yuval Turgeman] automation: enable vhost_net and tun ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_199_1808796376.1510478321840--

1 1