Build failed in Jenkins: system-sync_mirrors-centos-updates-7.6-el7-x86_64 #486

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

[CQ]: 107832, 2 (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 107832,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 107550,6 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change

Re: [ovirt-users] Mirror oVirt content

There is this document, but as the notice on it states, at least some parts of it are outdated: https://www.ovirt.org/develop/infra/repository-mirrors.html Forwarding this to the infra team, hopefully someone there will contact you soon. On Wed, 1 Apr 2020 at 22:52, wrote: > Hello oVirt

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 396 - Still Failing!

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/396/ Build Number: 396 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] cleanup-gated-dummy-master - Build #103 - FAILURE!

Build: https://jenkins.ovirt.org/job/cleanup-gated-dummy-master/103/ Build Name: #103 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an

[CQ]: 107798, 1 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause

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

oVirt infra daily report - unstable production jobs - 1148

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1148//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

Build failed in Jenkins: system-sync_mirrors-centos-updates-7.6-el7-x86_64 #485

See Changes: [Shlomi] Added mirror cleanup functionality [Evgheni Dereveanchin] Modules support for mirror_mgr.sh -- Started by timer

[CQ]: 107759, 1 (ovirt-engine-ui-extensions) failed "ovirt-master" system tests

Change 107759,1 (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

[CQ]: 107555, 5 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause

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

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #272 - FAILURE!

Build: https://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/272/ Build Name: #272 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an

Re: CI fails on fc

Hi Steven, Thanks for notifying us. At the time of running the CI test, those rpms were probably missing from our mirrors. However, they have been re-downloaded, and thus your test should no longer fail with the same error. Please try running it again. On Wed, Apr 1, 2020 at 6:58 PM Steven

Build failed in Jenkins: system-sync_mirrors-epel-s390x-el7-s390x #239

See Changes: -- [...truncated 2.62 MB...] 8:texlive-lshort-french-doc-svn23332.5.01fr_0-23.el7.noarch: [Errno 256] No more mirrors to try.

Build failed in Jenkins: system-sync_mirrors-epel-s390x-el7-s390x #238

See Changes: [Shlomi] Fixed hardcoded link for fedora-base-fc29 [Sandro Bonazzola] Drop failovermethod key in mock config. [Gal Ben Haim] Add a symlink to usrc_updater.py [Gal Ben Haim]

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

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

[JIRA] (OVIRT-2893) [FIRING:1] LowPercentageOfAvailDiskSpace (amd64 linux rootfs rootfs shift-n11.phx.ovirt.org kubernetes-nodes-exporter shift-n11.phx.ovirt.org / true primary vm ci)

Alertmanager_Bot created OVIRT-2893: --- Summary: [FIRING:1] LowPercentageOfAvailDiskSpace (amd64 linux rootfs rootfs shift-n11.phx.ovirt.org kubernetes-nodes-exporter shift-n11.phx.ovirt.org / true primary vm ci) Key: OVIRT-2893

CI fails on fc

Dear Infra Team, I have a CI test that is failing only for FC [1] in the log [2] the failures is on accessing the rpm files [3]. EL does succeed. Please advise accordingly. [1] https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/5090/artifact/ci_build_summary.html [2]

[JIRA] (OVIRT-2892) [FIRING:6] LowPercentageOfAvailDiskSpace (amd64 linux rootfs rootfs kubernetes-nodes-exporter / true primary ci)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alertmanager_Bot updated OVIRT-2892: Resolution: Fixed Status: Done (was: To Do) This alert was sent for testing

[JIRA] (OVIRT-2892) [FIRING:6] LowPercentageOfAvailDiskSpace (amd64 linux rootfs rootfs kubernetes-nodes-exporter / true primary ci)

Alertmanager_Bot created OVIRT-2892: --- Summary: [FIRING:6] LowPercentageOfAvailDiskSpace (amd64 linux rootfs rootfs kubernetes-nodes-exporter / true primary ci) Key: OVIRT-2892 URL:

[JIRA] (OVIRT-2890) Test ticket - Alertmanager_Bot

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin updated OVIRT-2890: Resolution: Cannot Reproduce Status: Done (was: To Do) test issue,

[JIRA] (OVIRT-2891) [FIRING:1] TestAlert

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin updated OVIRT-2891: Resolution: Cannot Reproduce Status: Done (was: To Do) test issue,

[JIRA] (OVIRT-2891) [FIRING:1] TestAlert

Alertmanager_Bot created OVIRT-2891: --- Summary: [FIRING:1] TestAlert Key: OVIRT-2891 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2891 Project: oVirt - virtualization made easy Issue

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

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

[CQ]: 106118,28 (jenkins) failed "dummy-master" system tests

Change 106118,28 (jenkins) is probably the reason behind recent system test failures in the "dummy-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

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #271 - FAILURE!

Build: https://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/271/ Build Name: #271 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an

[CQ]: 107789, 1 (java-client-kubevirt) failed "ovirt-master" system tests, but isn't the failure root cause

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

Re: [JIRA] (OVIRT-2890) Test ticket - Alertmanager_Bot

Nice. It does create them! On Wed, Apr 1, 2020 at 1:36 PM Alertmanager_Bot (oVirt JIRA) < j...@ovirt-jira.atlassian.net> wrote: > Alertmanager_Bot created OVIRT-2890: > --- > > Summary: Test ticket - Alertmanager_Bot > Key:

[JIRA] (OVIRT-2890) Test ticket - Alertmanager_Bot

Alertmanager_Bot created OVIRT-2890: --- Summary: Test ticket - Alertmanager_Bot Key: OVIRT-2890 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2890 Project: oVirt - virtualization made easy

[CQ]: 107962, 5 (ovirt-lldp-labeler) 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 107962,5 (ovirt-lldp-labeler) failed. However, this change seems not to be the root cause for this failure. Change 107964,2 (ovirt-lldp-labeler) that this change depends on or is based on, was detected as the cause of the

[CQ]: 107968, 8 (ovirt-lldp-labeler) 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 107968,8 (ovirt-lldp-labeler) failed. However, this change seems not to be the root cause for this failure. Change 107964,2 (ovirt-lldp-labeler) that this change depends on or is based on, was detected as the cause of the

[CQ]: 107961, 5 (ovirt-lldp-labeler) 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 107961,5 (ovirt-lldp-labeler) failed. However, this change seems not to be the root cause for this failure. Change 107964,2 (ovirt-lldp-labeler) that this change depends on or is based on, was detected as the cause of the

[CQ]: 107960, 5 (ovirt-lldp-labeler) 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 107960,5 (ovirt-lldp-labeler) failed. However, this change seems not to be the root cause for this failure. Change 107964,2 (ovirt-lldp-labeler) that this change depends on or is based on, was detected as the cause of the

[CQ]: 107964,2 (ovirt-lldp-labeler) failed "ovirt-4.3" system tests

Change 107964,2 (ovirt-lldp-labeler) 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

[CQ]: 107727, 4 (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 107727,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 107550,6 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change