February 2018 - Infra - oVirt List Archives

[CQ]: 87231, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87231,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87116,5 (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 87116,5 (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/87231/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5336/

1 0

oVirt infra weekly meeting notes 07.02.2018
by Evgheni Dereveanchin 07 Feb '18

07 Feb '18

Hi everyone, Please find the topics of this week's infra meeting below: - New security advisory for Jenkins, patch updated OVIRT-1858 <https://ovirt-jira.atlassian.net/browse/OVIRT-1858> - Enable REST API for Gerrit OVIRT-1889 <https://ovirt-jira.atlassian.net/browse/OVIRT-1889> - ManageIQ deployed on Staging OVIRT-1803 <https://ovirt-jira.atlassian.net/browse/OVIRT-1803> - Request to deploy beaker OVIRT-1881 <https://ovirt-jira.atlassian.net/browse/OVIRT-1881> -- Regards, Evgheni Dereveanchin

1 0

[CQ]: 87258, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87258,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (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 87244,1 (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/87258/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/592/

1 0

[oVirt CI] standard-enqueue - Build #9777 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 07 Feb '18

07 Feb '18

------=_Part_131_307129312.1518017524322 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9777/ Build Name: #9777 Build Description: Gerrit: 69504 - ovirt-engine-cli (3.6, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/69504 - title: cli: Fix SDK dependency - project: ovirt-engine-cli - branch: cli_3.6 - author: Juan Hernandez <juan.hernandez(a)redhat.com> ------=_Part_131_307129312.1518017524322--

1 0

[CQ]: 82234,1 (vcredist-x86) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

Change 82234,1 (vcredist-x86) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/82234/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/590/

1 0

[CQ]: 86867, 3 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 86867,3 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) 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 86692,1 (ovirt-engine-api- model) 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/86867/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86692/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/588/

1 0

[CQ]: 87244,1 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

Change 87244,1 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/585/

1 0

[JIRA] (OVIRT-1888) can_sudo function has to accept multiple positional parameters
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1518013245-10002-297 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1888?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1888: ---------------------------------- Assignee: Daniel Belenky (was: infra) Status: In Progress (was: To Do) > can_sudo function has to accept multiple positional parameters > -------------------------------------------------------------- > > Key: OVIRT-1888 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1888 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Currently, can_sudo function in global_setup and slave_cleanup is accepting only one param but in it's calls sometimes we pass more than one param to check for permissions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518013245-10002-297 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1888?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1888:</h3> <pre>Assignee: Daniel Belenky (was: infra) Status: In Progress (was: To Do)</pre> <blockquote><h3>can_sudo function has to accept multiple positional parameters</h3> <pre> Key: OVIRT-1888 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1888 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Daniel Belenky Assignee: Daniel Belenky</pre> <p>Currently, can_sudo function in global_setup and slave_cleanup is accepting only one param but in it's calls sometimes we pass more than one param to check for permissions.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1518013245-10002-297--

1 0

[JIRA] (OVIRT-1890) Kill all lago processes during slave cleanup
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1890?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1890: ---------------------------------- Assignee: Daniel Belenky (was: infra) Status: In Progress (was: To Do) > Kill all lago processes during slave cleanup > -------------------------------------------- > > Key: OVIRT-1890 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1890 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Lago, oVirt CI > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Sometimes we end up having stale lago processes after builds are being aborted. > Until we'll find a permanent solution (such as a new runner for CI), we should add an ugly cleanup function to our slave cleanup to ensure lago is being killed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1890) Kill all lago processes during slave cleanup
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1518013160-31541-247 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1890?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1890: ---------------------------------- Epic Link: OVIRT-400 > Kill all lago processes during slave cleanup > -------------------------------------------- > > Key: OVIRT-1890 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1890 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Lago, oVirt CI > Reporter: Daniel Belenky > Assignee: infra > > Sometimes we end up having stale lago processes after builds are being aborted. > Until we'll find a permanent solution (such as a new runner for CI), we should add an ugly cleanup function to our slave cleanup to ensure lago is being killed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518013160-31541-247 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1890?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1890:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Kill all lago processes during slave cleanup</h3> <pre> Key: OVIRT-1890 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1890 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Lago, oVirt CI Reporter: Daniel Belenky Assignee: infra</pre> <p>Sometimes we end up having stale lago processes after builds are being aborted. Until we'll find a permanent solution (such as a new runner for CI), we should add an ugly cleanup function to our slave cleanup to ensure lago is being killed.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1518013160-31541-247--

1 0