A system test invoked by the "ovirt-master" change queue including change
97572,3 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 96490,17 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing failures
A system test invoked by the "ovirt-master" change queue including change
97521,2 (ovirt-provider-ovn) failed. However, this change seems not to be the
root cause for this failure. Change 97395,9 (ovirt-provider-ovn) that this
change depends on or is based on, was detected as the cause of the testi
Change 96490,17 (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 abou
Change 97395,9 (ovirt-provider-ovn) 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
A system test invoked by the "ovirt-master" change queue including change
97521,2 (ovirt-provider-ovn) failed. However, this change seems not to be the
root cause for this failure. Change 97395,9 (ovirt-provider-ovn) that this
change depends on or is based on, was detected as the cause of the testi
Change 97395,9 (ovirt-provider-ovn) 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
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/476/
Build Number: 476
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/476/
Build Number: 476
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since
Change 97561,2 (ovirt-engine-ui-extensions) 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
Good morning!
Attached is the HTML page with the jenkins status report. You can see it also
here:
-
http://jenkins.ovirt.org/job/system_jenkins-report/727//artifact/exported-artifacts/upstream_report.html
Cheers,
Jenkins
Change 97532,2 (ovirt-appliance) 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 ab
Change 88c6916 (ovirt-ansible-infra) 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 detail
Change 97479,7 (cockpit-ovirt) 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 abou
Change 97437,6 (ovirt-hosted-engine-setup) 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
Failed to run project_setup.sh for:
#3440 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-or
Failed to run project_setup.sh for:
#3440 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-or
A system test invoked by the "ovirt-master" change queue including change
96974fa (ovirt-ansible-hosted-engine-setup) failed. However, this change seems
not to be the root cause for this failure. Change 9267118 (ovirt-ansible-
hosted-engine-setup) that this change depends on or is based on, was det
On Tue, 5 Feb 2019 12:52:21 +0100
Martin Perina wrote:
> On Tue, Feb 5, 2019 at 12:49 PM Barak Korren wrote:
>
> >
> >
> > On Tue, 5 Feb 2019 at 12:59, Sandro Bonazzola wrote:
> >
> >>
> >>
> >> Il giorno mar 5 feb 2019 alle ore 11:54 Tomáš Golembiovský <
> >> tgole...@redhat.com> ha scrit
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38944#comment-38944
]
Dafna Ron commented on OVIRT-2666:
--
Galit merged a fix and upstream is fix.
Closing this as
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dafna Ron updated OVIRT-2666:
-
Resolution: Fixed
Status: Done (was: To Do)
> OST fails with LagoDeployError: ... failed with s
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38943#comment-38943
]
Ehud Yonasi commented on OVIRT-2669:
Closing this ticket, opening in d/s jira.
> CI scri
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ehud Yonasi updated OVIRT-2669:
---
Resolution: Duplicate
Status: Done (was: To Do)
> CI scripts try to modify unrelated bugs
>
On Tue, Feb 5, 2019 at 12:49 PM Barak Korren wrote:
>
>
> On Tue, 5 Feb 2019 at 12:59, Sandro Bonazzola wrote:
>
>>
>>
>> Il giorno mar 5 feb 2019 alle ore 11:54 Tomáš Golembiovský <
>> tgole...@redhat.com> ha scritto:
>>
>>> Hi,
>>>
>>> I would like to rename the GitHub repo ovirt-ansible-v2v-c
On Tue, 5 Feb 2019 at 12:59, Sandro Bonazzola wrote:
>
>
> Il giorno mar 5 feb 2019 alle ore 11:54 Tomáš Golembiovský <
> tgole...@redhat.com> ha scritto:
>
>> Hi,
>>
>> I would like to rename the GitHub repo ovirt-ansible-v2v-conversion-host
>> to v2v-conversion-host. Is there a list of things I
Il giorno mar 5 feb 2019 alle ore 11:54 Tomáš Golembiovský <
tgole...@redhat.com> ha scritto:
> Hi,
>
> I would like to rename the GitHub repo ovirt-ansible-v2v-conversion-host
> to v2v-conversion-host. Is there a list of things I should do before
> or after the operation? Will the automation stil
Failed to run project_setup.sh for:
#3436 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-or
Hi,
I would like to rename the GitHub repo ovirt-ansible-v2v-conversion-host
to v2v-conversion-host. Is there a list of things I should do before
or after the operation? Will the automation still work?
Tomas
--
Tomáš Golembiovský
___
Infra mailin
Failed to run project_setup.sh for:
#3433 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-or
Nir Soffer created OVIRT-2669:
-
Summary: CI scripts try to modify unrelated bugs
Key: OVIRT-2669
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2669
Project: oVirt - virtualization made easy
If a commit message mention another bug, the CI script try to add the patch
to the bug in the commit message, and change the bug to POST.
Mentioning another bug in a commit message is good practice, making it
easier to follow, and avoiding unclear forms like "bug 100" or
"BZ#100",
or even
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38939#comment-38939
]
Ehud Yonasi commented on OVIRT-2668:
Hi [~mwperina],
It was published into master CQ, but
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ehud Yonasi reassigned OVIRT-2668:
--
Assignee: Ehud Yonasi (was: infra)
> WildFly 15 packages got to tested-4.3 repo, but not to
Martin Perina created OVIRT-2668:
Summary: WildFly 15 packages got to tested-4.3 repo, but not to
tested-master repo
Key: OVIRT-2668
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2668
Project: oV
33 matches
Mail list logo
