Re: [CQ]: d8e7156 (ovirt-ansible-repositories) failed "ovirt-master" system tests

jira: https://ovirt-jira.atlassian.net/browse/OVIRT-2399 On Sat, Aug 4, 2018 at 12:23 AM, oVirt Jenkins wrote: > Change d8e7156 (ovirt-ansible-repositories) is probably the reason behind > recent system test failures in the "ovirt-master" change queue and needs > to be > fixed. > > This change

Re: [CQ]: 92674,15 (vdsm) failed "ovirt-master" system tests

new package tagged in centos was missing deps. Sandro fixed the issue with: https://gerrit.ovirt.org/#/c/93476/ jira: https://ovirt-jira.atlassian.net/browse/OVIRT-2399 On Fri, Aug 3, 2018 at 4:16 PM, oVirt Jenkins wrote: > Change 92674,15 (vdsm) is probably the reason behind recent system

Re: [ovirt-devel] Re: who owns ovirt copr?

On 6 August 2018 at 09:43, Sandro Bonazzola wrote: > > > 2018-08-06 7:54 GMT+02:00 Barak Korren : > >> While the search for the credentials can continue, I'd like to ask why is >> copr being used in the 1st place. >> >> Can we switch the build process to STDCI? If you already have a script to >>

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 458 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/458/ Build Number: 458 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success:

[JIRA] (OVIRT-2400) check-patch failed on he-basic-iscsi-master with 'disk_space requirements are not satisfied'

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37722#comment-37722 ] Gal Ben Haim commented on OVIRT-2400: - It checks for free disk space the Jenkins slave, not Lago VMs. >

[JIRA] (OVIRT-2400) check-patch failed on he-basic-iscsi-master with 'disk_space requirements are not satisfied'

Dafna Ron created OVIRT-2400: Summary: check-patch failed on he-basic-iscsi-master with 'disk_space requirements are not satisfied' Key: OVIRT-2400 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2400

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 558 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/558/ Build Number: 558 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

[CQ]: 93310,4 (ioprocess) failed "ovirt-master" system tests

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

Re: [ovirt-devel] Re: who owns ovirt copr?

2018-08-06 7:54 GMT+02:00 Barak Korren : > While the search for the credentials can continue, I'd like to ask why is > copr being used in the 1st place. > > Can we switch the build process to STDCI? If you already have a script to > generate the SRPM for copr, having STDCI then run rpmbuild

[JIRA] (OVIRT-2400) check-patch failed on he-basic-iscsi-master with 'disk_space requirements are not satisfied'

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37721#comment-37721 ] Dafna Ron commented on OVIRT-2400: -- [~gbenh...@redhat.com] https://gerrit.ovirt.org/#/c/93476/ - patch that

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 513 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/513/ Build Number: 513 Build Status: Fixed Triggered By: Started by timer - Changes

[JIRA] (OVIRT-2401) Update SSL cert in staging OpenShift instance

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Belenky updated OVIRT-2401: -- Epic Link: OVIRT-403 > Update SSL cert in staging OpenShift instance >

[JIRA] (OVIRT-2401) Update SSL cert in staging OpenShift instance

Daniel Belenky created OVIRT-2401: - Summary: Update SSL cert in staging OpenShift instance Key: OVIRT-2401 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2401 Project: oVirt - virtualization made

[JIRA] (OVIRT-2401) Update SSL cert in staging OpenShift instance

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Belenky reassigned OVIRT-2401: - Assignee: Evgheni Dereveanchin (was: infra) > Update SSL cert in staging OpenShift

[CQ]: 93257, 3 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause

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

[oVirt Jenkins] ovirt-system-tests_compat-3.6-suite-master - Build # 47 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/47/ Build Number: 47 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 460 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/460/ Build Number: 460 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

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

[CQ]: 93508,1 (vdsm) failed "ovirt-master" system tests

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

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

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

[CQ]: 92691,13 (ovirt-engine) failed "ovirt-master" system tests

Change 92691,13 (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

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 47 - Still Failing!

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/47/ Build Number: 47 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 461 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/461/ Build Number: 461 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_compat-3.6-suite-master - Build # 48 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/48/ Build Number: 48 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[oVirt Jenkins] ovirt-system-tests_compat-4.0-suite-master - Build # 47 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/47/ Build Number: 47 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 6-08-2018 ] [ TEST NAME ]

Hi, We have a failure in CQ on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite. *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/93466/ - core: clean stale image_transfer on upgradeLink to

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

we have a code regression: https://ovirt-jira.atlassian.net/browse/OVIRT-2403 On Mon, Aug 6, 2018 at 3:16 PM, oVirt Jenkins wrote: > Change 93466,2 (ovirt-engine) is probably the reason behind recent system > test > failures in the "ovirt-master" change queue and needs to be fixed. > > This

Re: [ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 6-08-2018 ] [ TEST NAME ]

2018-08-06 14:45 GMT+02:00 Dafna Ron : > Hi, > > We have a failure in CQ on ovirt-master for test > 001_upgrade_engine.test_initialize_engine > on upgrade suite. > > > > > > > > > > *Link and headline of suspected patches: > https://gerrit.ovirt.org/#/c/93466/

[JIRA] (OVIRT-2399) missing deps for openvswitch cause failure in lago vms deployment

Dafna Ron created OVIRT-2399: Summary: missing deps for openvswitch cause failure in lago vms deployment Key: OVIRT-2399 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2399 Project: oVirt -

[JIRA] (OVIRT-2399) missing deps for openvswitch cause failure in lago vms deployment

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron updated OVIRT-2399: - Labels: ost_failures ost_packages (was: ost_code_regression ost_failures ost_packages) > missing deps

[JIRA] (OVIRT-2399) missing deps for openvswitch cause failure in lago vms deployment

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron updated OVIRT-2399: - Description: fixed with this patch: https://gerrit.ovirt.org/#/c/93476/ was: fixed with this patch:

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 45 - Still Failing!

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/45/ Build Number: 45 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[JIRA] (OVIRT-2402) ioprocess failed ovirt-master with 500 error from engine

Dafna Ron created OVIRT-2402: Summary: ioprocess failed ovirt-master with 500 error from engine Key: OVIRT-2402 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2402 Project: oVirt - virtualization made

[JIRA] (OVIRT-2403) failure on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite

Dafna Ron created OVIRT-2403: Summary: failure on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite Key: OVIRT-2403 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2403

[JIRA] (OVIRT-2403) failure on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron updated OVIRT-2403: - Priority: Highest (was: Medium) > failure on ovirt-master for test

Re: [ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 6-08-2018 ] [ TEST NAME ]

I think what failed may be the fix On Mon, Aug 6, 2018 at 3:48 PM, Sandro Bonazzola wrote: > > > 2018-08-06 14:45 GMT+02:00 Dafna Ron : > >> Hi, >> >> We have a failure in CQ on ovirt-master for test >> 001_upgrade_engine.test_initialize_engine on upgrade suite. >> >> >> >> >> >> >> >> >> >>

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 672 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/672/ Build Number: 672 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_compat-3.6-suite-master - Build # 46 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/46/ Build Number: 46 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[JIRA] (OVIRT-2404) CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo

Dafna Ron created OVIRT-2404: Summary: CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo Key: OVIRT-2404 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2404 Project: oVirt

[JIRA] (OVIRT-2404) CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37733#comment-37733 ] Dafna Ron commented on OVIRT-2404: -- [~bkor...@redhat.com][~eyon...@redhat.com] was the cleanup for 4.1

[JIRA] (OVIRT-2404) CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron updated OVIRT-2404: - Description: https://pastebin.com/uMQMjAq5 we are failing since 4.1 tested is missing.

[JIRA] (OVIRT-2404) CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37735#comment-37735 ] Ehud Yonasi commented on OVIRT-2404: Yes, deleted it today. > CQ 4.2 vdsm failing

[JIRA] (OVIRT-2404) CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37736#comment-37736 ] Dafna Ron commented on OVIRT-2404: -- changing tested repo for pre-reposync file so it is not triggered on the

[JIRA] (OVIRT-2404) CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37737#comment-37737 ] Ehud Yonasi commented on OVIRT-2404: I think you should just change the line of the reposync: Adding repo

Re: [ovirt-devel] Re: [ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 6-08-2018 ] [ TEST NAME ]

Daniel please check it ASAP tomorrow, we cannot release the async without being sure the script doesn't fail -- Forwarded message -- From: Sandro Bonazzola Date: Mon, Aug 6, 2018 at 3:48 PM Subject: [ovirt-devel] Re: [ OST Failure Report ] [ oVirt master (ovirt-engine) ] [

[CQ]: 93254, 3 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause

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

[CQ]: 93253,3 (vdsm) failed "ovirt-4.2" system tests

Change 93253,3 (vdsm) 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 about the

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 402 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/402/ Build Number: 402 Build Status: Fixed Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 - Build # 13 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc28-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc28-x86_64/13/ Build Number: 13 Build Status: Still Failing Triggered By: Started by timer

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

Change 93466,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

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 459 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/459/ Build Number: 459 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[JIRA] (OVIRT-2361) Remove 4.1 tested repo

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ehud Yonasi reassigned OVIRT-2361: -- Assignee: Ehud Yonasi (was: infra) > Remove 4.1 tested repo > -- > >

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 46 - Still Failing!

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/46/ Build Number: 46 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[oVirt Jenkins] ovirt-system-tests_compat-4.0-suite-master - Build # 46 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/46/ Build Number: 46 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[CQ]: 93255, 3 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause

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

[oVirt Jenkins] ovirt-system-tests_compat-4.0-suite-master - Build # 45 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/45/ Build Number: 45 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[CQ]: 93256, 3 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause

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