[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&focusedCommentId=39899#comment-39899 ] Marcin Sobczyk commented on OVIRT-2813: --- Hi, On 10/10/19 6:14 AM, Yuval Turgeman wrote:

[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&focusedCommentId=39898#comment-39898 ] Yuval Turgeman commented on OVIRT-2813: --- You may be running out of loop devices, if that

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

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

[CQ]: 103925,2 (vdsm) failed "ovirt-master" system tests

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

[CQ]: 103706, 4 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests

Change 103706,4 (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

[CQ]: 103725, 6 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests, but isn't the failure root cause

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

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

Change 104004,2 (ovirt-hosted-engine-ha) 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 de

oVirt infra daily report - unstable production jobs - 973

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

[CQ]: 103387, 8 (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 103387,8 (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 tes

[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&focusedCommentId=39897#comment-39897 ] Nir Soffer commented on OVIRT-2813: --- On Wed, Oct 9, 2019 at 11:56 PM Nir Soffer wrote: > I

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

Nir Soffer created OVIRT-2813: - Summary: EL8 builds fail to mount loop device - kernel too old? Key: OVIRT-2813 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2813 Project: oVirt - virtualization made

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

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

[CQ]: 103369, 13 (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 103369,13 (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 te

[CQ]: 103406, 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 103406,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 tes

[CQ]: 103257, 5 (ovirt-guest-agent) failed "ovirt-master" system tests

Change 103257,5 (ovirt-guest-agent) 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

[CQ]: 103983,3 (safelease) failed "ovirt-master" system tests

Change 103983,3 (safelease) 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 t

Re: Please remove 4.2 from your stdci.yaml files

The failure reported here was resolved along with another package that was effected but as the configuration is in the projects themselves and we cannot really go over each bone to check I am afraid we cannot give a list of packages at this time (until it fails). On Wed, Oct 9, 2019 at 3:36 PM San

Re: Please remove 4.2 from your stdci.yaml files

Il giorno ven 20 set 2019 alle ore 12:14 Dafna Ron ha scritto: > Hi, > > We have several unstable jobs which are caused because 4.2 is no longer > available for CQ. > > Please remove 4.2 from your stdci.yaml files to avoid getting unstable > jobs. > have we got a list of packages affected? > >

[CQ]: 103368, 9 (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 103368,9 (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 tes

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

See Changes: [Sandro Bonazzola] ovirt-engine-sdk: drop v1 jobs for master -- Started by timer Running as SYSTEM [EnvInject] - Loading node

[CQ]: 103981, 2 (safelease) failed "ovirt-master" system tests, but isn't the failure root cause

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

[CQ]: 103387, 8 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.3" change queue including change 103387,8 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 103368,9 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testin

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

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

[CQ]: 103369, 13 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.3" change queue including change 103369,13 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 103368,9 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testi

Re: Add Email to github whitelist

Yes, it is working. On Wed, Oct 9, 2019 at 2:05 PM Evgheni Dereveanchin wrote: > Hi Ritesh, > > Sorry for the delay in response, I checked the whitelist and your email is > present there. > Could you please try triggering CI and confirm if everything works for you? > > On Wed, Oct 9, 2019 at 9:1

[CQ]: 103368,9 (ovirt-provider-ovn) failed "ovirt-4.3" system tests

Change 103368,9 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-4.3" 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

[CQ]: 103791,6 (ioprocess) failed "ovirt-master" system tests

Change 103791,6 (ioprocess) 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 t

Re: Add Email to github whitelist

Hi Ritesh, Sorry for the delay in response, I checked the whitelist and your email is present there. Could you please try triggering CI and confirm if everything works for you? On Wed, Oct 9, 2019 at 9:18 AM Ritesh Chikatwar wrote: > Any update on this? > > On Thu, Oct 3, 2019 at 12:49 PM Rites

Re: Add Email to github whitelist

Any update on this? On Thu, Oct 3, 2019 at 12:49 PM Ritesh Chikatwar wrote: > Please add my email id to whitelist which will help to CI jobs to run > whenever a new patch sent by me. > > > Regards > Ritesh Chikatwar > ___ Infra mailing list -- infra@ov