Build: http://jenkins.ovirt.org/job/standard-enqueue/10694/
Build Name: #10694
Build Description: Gerrit: 88275 - ovirt-log-collector (3.6)
Build Status: FAILURE
Gerrit change: https://gerrit.ovirt.org/88275
- title: collector: Remove unused code
- project: ovirt-log-collector
- branch: ovirt-log-c
Change 88250,4 (ovirt-engine-metrics) 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 detai
Change 88250,4 (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
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35892#comment-35892
]
Nir Soffer commented on OVIRT-1770:
---
I never see the slowdown again, but I does not mean the
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgheni Dereveanchin updated OVIRT-1770:
Status: Blocked (was: To Do)
> Build on fedora 26 fails, accessing console log ex
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35889#comment-35889
]
Evgheni Dereveanchin commented on OVIRT-1770:
-
The garbage collection improvement
I left the test so that I can understand why this happens :) I suspected it
was latency but wanted to see if indeed it is.
the failure is a storage behaviour and they do not have a way to query
tasks statuses before re-trying the same action.
I can disable the test until the bug is fixed, however,
On Tue, Feb 27, 2018 at 2:15 PM, Sandro Bonazzola
wrote:
>
>
> 2018-02-22 22:42 GMT+01:00 oVirt Jenkins :
>
>> A system test invoked by the "ovirt-master" change queue including change
>> 87428,2 (vdsm) failed. However, this change seems not to be the root
>> cause for
>> this failure. Change 879
On Tue, Feb 27, 2018 at 2:06 PM, Dafna Ron wrote:
> the upgade suite is using the 4.2 and the 4.1 reposync files and the
> centos repos are there.
> why do you think its not using the ovirt mirrors? am I missing something
> in the reposync?
>
> Please note that the error happens yesterday.
> From
2018-02-22 22:42 GMT+01:00 oVirt Jenkins :
> A system test invoked by the "ovirt-master" change queue including change
> 87428,2 (vdsm) failed. However, this change seems not to be the root cause
> for
> this failure. Change 87944,3 (vdsm) that this change depends on or is
> based on,
> was detect
On Tue, Feb 27, 2018 at 2:08 PM, Dafna Ron wrote:
> this happens randomly when there is a delay of some sorts in the OST run.
>
We have to understand why it happens and if we can't, the test should be
disabled, we can't allow known issues to be failing every once in a while.
If there is an effor
this happens randomly when there is a delay of some sorts in the OST run.
I did not skip since its not failing often.
On Tue, Feb 27, 2018 at 11:40 AM, Eyal Edri wrote:
>
>
> On Tue, Feb 27, 2018 at 1:32 PM, Dafna Ron wrote:
>
>> it is a bug in the test suite which is reported on OST bugzilla.
the upgade suite is using the 4.2 and the 4.1 reposync files and the centos
repos are there.
why do you think its not using the ovirt mirrors? am I missing something in
the reposync?
Please note that the error happens yesterday.
>From what I could see yesterday there was a momentary issue with the
Evgheni,
Do we have a way to detect which slaves are out of space and reprovision
them or increase their size?
On Tue, Feb 27, 2018 at 12:59 PM, Sandro Bonazzola
wrote:
>
>
> 2018-02-26 0:53 GMT+01:00 oVirt Jenkins :
>
>> Change 88094,2 (ovirt-engine) is probably the reason behind recent system
On Tue, Feb 27, 2018 at 1:32 PM, Dafna Ron wrote:
> it is a bug in the test suite which is reported on OST bugzilla.
>
Is it possible to disable the test until we get a fix for it?
>
>
>
> On Tue, Feb 27, 2018 at 10:52 AM, Sandro Bonazzola
> wrote:
>
>>
>>
>> 2018-02-26 13:39 GMT+01:00 oVirt
On Tue, Feb 27, 2018 at 1:34 PM, Dafna Ron wrote:
> yes, I noticed that myself which is why after checking that I can access
> the base rhel7 repo I re-triggered the change.
>
Can you check why the upgrade suite isn't using the oVirt mirrors?
>
>
> On Tue, Feb 27, 2018 at 10:54 AM, Sandro Bona
yes, I noticed that myself which is why after checking that I can access
the base rhel7 repo I re-triggered the change.
On Tue, Feb 27, 2018 at 10:54 AM, Sandro Bonazzola
wrote:
>
>
> 2018-02-26 13:10 GMT+01:00 oVirt Jenkins :
>
>> Change 88165,1 (ovirt-hosted-engine-setup) is probably the reas
it is a bug in the test suite which is reported on OST bugzilla.
On Tue, Feb 27, 2018 at 10:52 AM, Sandro Bonazzola
wrote:
>
>
> 2018-02-26 13:39 GMT+01:00 oVirt Jenkins :
>
>> Change 88046,11 (ovirt-hosted-engine-setup) is probably the reason behind
>> recent system test failures in the "ovir
2018-02-26 0:53 GMT+01:00 oVirt Jenkins :
> Change 88094,2 (ovirt-engine) is probably the reason behind recent system
> test
> failures in the "ovirt-master" change queue and needs to be fixed.
>
>
No, this is caused by multiple failure in jenkins jobs:
http://jenkins.ovirt.org/job/ovirt-engine_m
2018-02-26 13:10 GMT+01:00 oVirt Jenkins :
> Change 88165,1 (ovirt-hosted-engine-setup) is probably the reason behind
> recent
> system test failures in the "ovirt-4.2" change queue and needs to be fixed.
>
No.
The reason behind the failure is a network issue:
*12:13:03* [upgrade-from-prevreleas
2018-02-26 13:39 GMT+01:00 oVirt Jenkins :
> Change 88046,11 (ovirt-hosted-engine-setup) is probably the reason behind
> recent system test failures in the "ovirt-master" change queue and needs
> to be
> fixed.
>
I don't think so. Failure is:
Error: Fault reason is "Operation Failed". Fault deta
21 matches
Mail list logo
