March 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-1886) Add fcraw support for s390x and ppc64le
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1886?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1886: ---------------------------- Component/s: mock_runner CI Mirrors > Add fcraw support for s390x and ppc64le > --------------------------------------- > > Key: OVIRT-1886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1886 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors, mock_runner > Reporter: sbonazzo > Assignee: infra > > Hi, > pushed https://gerrit.ovirt.org/#/c/87068/ for adding support to fcraw for > s390x ad ppc64le but looks like it won't be enough, opening a ticket as > suggested by Barak. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1886) Add fcraw support for s390x and ppc64le
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1886?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1886: ---------------------------- Issue Type: New Feature (was: By-EMAIL) > Add fcraw support for s390x and ppc64le > --------------------------------------- > > Key: OVIRT-1886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1886 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: sbonazzo > Assignee: infra > > Hi, > pushed https://gerrit.ovirt.org/#/c/87068/ for adding support to fcraw for > s390x ad ppc64le but looks like it won't be enough, opening a ticket as > suggested by Barak. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[CQ]: 88487, 5 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Mar '18

06 Mar '18

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

1 0

[CQ]: 88480, 2 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Mar '18

06 Mar '18

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

1 0

[CQ]: 87990, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Mar '18

06 Mar '18

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

1 0

[CQ]: 88459, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

[CQ]: 88504,1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

[CQ]: 88038, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

[CQ]: 88470, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

hosted-engine ovirt-system-tests
by Yedidyah Bar David 05 Mar '18

05 Mar '18

Hi all, Recently I have been pushing various patches to OST in order to verify specific bugs/fixes I was working on, using them with the "manual" jenkins job but with no immediate intention to get them merged. Main reason is that it's not clear what's the best approach to get such tests merged. Do we want a new suite? How often does it run? How long does it take? Do we have enough resources? etc. Do we have plans re this? Bugs/tickets/etc.? Do we want to do something? Specifically, do we want (eventually) many more suites? This seems unmanageable. A few suites, perhaps (also) using lago snapshots? Didn't try that myself, might be useful and relevant. Some examples: https://gerrit.ovirt.org/79203 https://gerrit.ovirt.org/79215 https://gerrit.ovirt.org/84813 https://gerrit.ovirt.org/88201 https://gerrit.ovirt.org/88234 And current one - this and the next ones in the stack: https://gerrit.ovirt.org/88331 Best regards, -- Didi

3 3