[CQ]: 103933, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 103933,6 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 103779,3 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change

[CQ]: 103760, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 103760,5 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 103779,3 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #245

See -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in

[CQ]: 103759, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 103759,5 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 103779,3 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change

[CQ]: 103779,3 (vdsm) failed "ovirt-master" system tests

Change 103779,3 (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

oVirt infra daily report - unstable production jobs - 974

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/974//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #244

See -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in

[CQ]: cfe8e00 (v2v-conversion-host) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change cfe8e00 (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change 6797e49 (v2v-conversion-host) that this change depends on or is based on, was detected as the cause of the

[CQ]: 103038, 5 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 103038,5 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 103930,1 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the

[CQ]: 103553,5 (ovirt-engine) failed "ovirt-master" system tests

Change 103553,5 (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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #856 kubernetes-nmstate [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

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #243

See Changes: [Sandro Bonazzola] pipelines: add cockpit-ovirt [Sandro Bonazzola] cockpit-ovirt: drop master v1 jobs -- Started by timer

[CQ]: 103959, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 103959,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103929,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[JIRA] (OVIRT-2812) move Douglas' rhvanalyzer repo under oVirt

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2812: - Resolution: Fixed Status: Done (was: To Do) > move Douglas' rhvanalyzer repo under oVirt >

[CQ]: 103929,2 (ovirt-engine) failed "ovirt-master" system tests

Change 103929,2 (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

[JIRA] (OVIRT-2812) move Douglas' rhvanalyzer repo under oVirt

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39900#comment-39900 ] Eyal Edri commented on OVIRT-2812: -- Done, added Michal as admin for the repo. > move Douglas' rhvanalyzer

Re: [JIRA] (OVIRT-2812) move Douglas' rhvanalyzer repo under oVirt

Done, added Michal as admin for the repo. On Tue, Oct 8, 2019 at 6:08 PM Douglas Landgraf (oVirt JIRA) < j...@ovirt-jira.atlassian.net> wrote: > > [ > https://ovirt-jira.atlassian.net/browse/OVIRT-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39894#comment-39894

[JIRA] (OVIRT-2813) EL8 builds fail to mount loop device - kernel too old?

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39899#comment-39899 ] Marcin Sobczyk commented on OVIRT-2813: --- Hi, On 10/10/19 6:14 AM, Yuval Turgeman wrote: > You may be