- Infra - oVirt List Archives

[CQ]: 86982,1 (otopi) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 86982,1 (otopi) 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/86982/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/404/

1 0

[CQ]: 86978, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 69668,7 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 69668,7 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" 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/69668/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5180/

1 0

[CQ]: 86977, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[JIRA] (OVIRT-1872) Jenkins outage 01.02.2018
by Evgheni Dereveanchin (oVirt JIRA) 01 Feb '18

01 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1872?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1872: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Jenkins outage 01.02.2018 > ------------------------- > > Key: OVIRT-1872 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1872 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Jenkins UI was slow and unreachable for several hours today. There were no major issues reported in the log yet CPU usage was very high. Jenkins was restarted to fix the issue, opening a ticket to investigate the cause and fix side effects if any -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)

1 0

[JIRA] (OVIRT-1872) Jenkins outage 01.02.2018
by Evgheni Dereveanchin (oVirt JIRA) 01 Feb '18

01 Feb '18

This is a multi-part message in MIME format... ------------=_1517489276-29025-250 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1872: ------------------------------------------- Summary: Jenkins outage 01.02.2018 Key: OVIRT-1872 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1872 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Evgheni Dereveanchin Assignee: infra Jenkins UI was slow and unreachable for several hours today. There were no major issues reported in the log yet CPU usage was very high. Jenkins was restarted to fix the issue, opening a ticket to investigate the cause and fix side effects if any -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078) ------------=_1517489276-29025-250 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1872:</h3> <pre> Summary: Jenkins outage 01.02.2018 Key: OVIRT-1872 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1872 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Evgheni Dereveanchin Assignee: infra</pre> <p>Jenkins UI was slow and unreachable for several hours today. There were no major issues reported in the log yet CPU usage was very high. Jenkins was restarted to fix the issue, opening a ticket to investigate the cause and fix side effects if any</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)</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> ------------=_1517489276-29025-250--

1 0

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

01 Feb '18

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

1 0

[CQ]: 86967, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

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

01 Feb '18

------=_Part_451_1469550335.1517479434683 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9474/ Build Name: #9474 Build Description: Gerrit: 82649 - ovirt-image-uploader (4.0, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/82649 - title: automation: drop snapshot repos - project: ovirt-image-uploader - branch: ovirt-image-uploader-4.0 - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_451_1469550335.1517479434683--

1 1

[JIRA] (OVIRT-1871) Wrong target milestone check on new 4.2 branches for ovirt-host-deploy
by sbonazzo (oVirt JIRA) 01 Feb '18

01 Feb '18

This is a multi-part message in MIME format... ------------=_1517478412-30235-139 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1871?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1871: ---------------------------- Epic Link: OVIRT-400 > Wrong target milestone check on new 4.2 branches for ovirt-host-deploy > ---------------------------------------------------------------------- > > Key: OVIRT-1871 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git > Reporter: sbonazzo > Assignee: infra > > I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get: > Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) https://gerrit.ovirt.org/#/c/86992/ > I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that. > When fixing this, please also include link to how to do that, I've other projects that will need similar change. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078) ------------=_1517478412-30235-139 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1871?page=com.atlassian.jira.… ]</pre> <h3>sbonazzo updated OVIRT-1871:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Wrong target milestone check on new 4.2 branches for ovirt-host-deploy</h3> <pre> Key: OVIRT-1871 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: sbonazzo Assignee: infra</pre> <p>I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get: Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) <a href="https://gerrit.ovirt.org/#/c/86992/">https://gerrit.ovirt.org/#/c/86992/</a> I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that. When fixing this, please also include link to how to do that, I've other projects that will need similar change.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)</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> ------------=_1517478412-30235-139--

1 0