- Infra - oVirt List Archives

[CQ]: 93739,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 15 Aug '18

15 Aug '18

Change 93739,3 (ovirt-engine) 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/93739/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9122/

1 0

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 268 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 Aug '18

15 Aug '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/268/ Build Number: 268 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #268 [Gal Ben Haim] HE: Added Local Maintenance Tests [Barak Korren] mock_runner: don`t store logs in source checkout ----------------- Failed Tests: ----------------- No tests ran.

1 18

[oVirt CI] standard-enqueue - Build #15742 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Aug '18

15 Aug '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/15742/ Build Name: #15742 Build Description: Gerrit: 93764 - ovirt-engine (4.2.5) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/93764 - title: build: post ovirt-engine-4.2.5.4 - project: ovirt-engine - branch: ovirt-engine-4.2.5.z - author: Martin Peřina <mperina(a)redhat.com>

1 1

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 202 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 Aug '18

15 Aug '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/20… Build Number: 202 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #202 [Gal Ben Haim] HE: Added Local Maintenance Tests [Barak Korren] mock_runner: don`t store logs in source checkout ----------------- Failed Tests: ----------------- No tests ran.

1 18

[JIRA] (OVIRT-2438) upgrade jenkins.ovirt.org to 2.121.3 LTS
by Evgheni Dereveanchin (oVirt JIRA) 15 Aug '18

15 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2438?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2438: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > upgrade jenkins.ovirt.org to 2.121.3 LTS > ---------------------------------------- > > Key: OVIRT-2438 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2438 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > A new LTS release is scheduled for today fixing security issues. This is the tracker issue for the upgrade which will also include plugin security fixes -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2438) upgrade jenkins.ovirt.org to 2.121.3 LTS
by Evgheni Dereveanchin (oVirt JIRA) 15 Aug '18

15 Aug '18

Evgheni Dereveanchin created OVIRT-2438: ------------------------------------------- Summary: upgrade jenkins.ovirt.org to 2.121.3 LTS Key: OVIRT-2438 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2438 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra A new LTS release is scheduled for today fixing security issues. This is the tracker issue for the upgrade which will also include plugin security fixes -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2437) patch fails CQ but not submitted to CQ message appears
by Dafna Ron (oVirt JIRA) 15 Aug '18

15 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2437?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2437: ---------------------------------- [~bkorren(a)redhat.com] [~dbelenky(a)redhat.com] I opened a ticket for documentation (so that this issue is explained) when you have a few min, can you please explain this? > patch fails CQ but not submitted to CQ message appears > ------------------------------------------------------ > > Key: OVIRT-2437 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2437 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > we have an alert for a patch that failed CQ but when I look at the patch I see the "This change was not submitted to any change queues" message. > I am also not seeing any build-artifacts job for the patch. > I see that the message continues with: > "If your project uses STDCI V2 and you have release branches configured, you may disregard this message." > However, if the package had not failed, is there any way for me to know that it is actually submitted to CQ? > example patch: https://gerrit.ovirt.org/#/c/93528/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2437) patch fails CQ but not submitted to CQ message appears
by Dafna Ron (oVirt JIRA) 15 Aug '18

15 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2437?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2437: ----------------------------- Labels: ost_failures (was: ) > patch fails CQ but not submitted to CQ message appears > ------------------------------------------------------ > > Key: OVIRT-2437 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2437 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > we have an alert for a patch that failed CQ but when I look at the patch I see the "This change was not submitted to any change queues" message. > I am also not seeing any build-artifacts job for the patch. > I see that the message continues with: > "If your project uses STDCI V2 and you have release branches configured, you may disregard this message." > However, if the package had not failed, is there any way for me to know that it is actually submitted to CQ? > example patch: https://gerrit.ovirt.org/#/c/93528/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2437) patch fails CQ but not submitted to CQ message appears
by Dafna Ron (oVirt JIRA) 15 Aug '18

15 Aug '18

Dafna Ron created OVIRT-2437: -------------------------------- Summary: patch fails CQ but not submitted to CQ message appears Key: OVIRT-2437 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2437 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra we have an alert for a patch that failed CQ but when I look at the patch I see the "This change was not submitted to any change queues" message. I am also not seeing any build-artifacts job for the patch. I see that the message continues with: "If your project uses STDCI V2 and you have release branches configured, you may disregard this message." However, if the package had not failed, is there any way for me to know that it is actually submitted to CQ? example patch: https://gerrit.ovirt.org/#/c/93528/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 411 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 Aug '18

15 Aug '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 411 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #411 [Gal Ben Haim] HE: Added Local Maintenance Tests [Barak Korren] mock_runner: don`t store logs in source checkout ----------------- Failed Tests: ----------------- No tests ran.

1 18