[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 75 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/75/ Build Number: 75 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 235 - Failure!

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

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #1554

See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 8 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 275 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 453 - Fixed!

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

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

Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-06-2018 ] [ 002_bootstrap.update_default_cluster ]

Yes I do On Tue, Jun 5, 2018 at 7:20 PM, Martin Perina wrote: > > > On Tue, Jun 5, 2018 at 5:08 PM, Dafna Ron wrote: > >> Eli, Martin, >> Any updates? >> > > ​Eli, do you think that https://gerrit.ovirt.org/91968​ fixes also this > OST failure? > > >> >> On Tue, Jun 5, 2018 at 12:15 PM, Dafna

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 74 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/74/ Build Number: 74 Build Status: Still Failing Triggered By: Started by timer - Changes Since

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

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 234 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/234/ Build Number: 234 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success:

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1553

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

Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-06-2018 ] [ 002_bootstrap.update_default_cluster ]

On Tue, Jun 5, 2018 at 5:08 PM, Dafna Ron wrote: > Eli, Martin, > Any updates? > ​Eli, do you think that https://gerrit.ovirt.org/91968​ fixes also this OST failure? > > On Tue, Jun 5, 2018 at 12:15 PM, Dafna Ron wrote: > >> >> >> >> >> *Hi, We have a failure in ovirt-engine on master on

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 7 - Still Failing!

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

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

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 274 - Still Failing!

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

[JIRA] (OVIRT-2141) dwh fails on prepare_migration_attachments_ipv4

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron updated OVIRT-2141: - Issue Type: Bug (was: Task) > dwh fails on prepare_migration_attachments_ipv4 >

[JIRA] (OVIRT-2141) dwh fails on prepare_migration_attachments_ipv4

Dafna Ron created OVIRT-2141: Summary: dwh fails on prepare_migration_attachments_ipv4 Key: OVIRT-2141 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2141 Project: oVirt - virtualization made easy

Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-06-2018 ] [ 002_bootstrap.update_default_cluster ]

Eli, Martin, Any updates? On Tue, Jun 5, 2018 at 12:15 PM, Dafna Ron wrote: > > > > > *Hi, We have a failure in ovirt-engine on master on update cluster because > of "cpu not found" CQ reported the below as the most possible cause for the > failure. I looked at the other changes that ran and I

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin updated OVIRT-2140: Issue Type: Improvement (was: Bug) > enforce SSL on resources.ovirt.org >

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org

Evgheni Dereveanchin created OVIRT-2140: --- Summary: enforce SSL on resources.ovirt.org Key: OVIRT-2140 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 Project: oVirt - virtualization made

[JIRA] (OVIRT-2139) enforce SSL on jenkins.ovirt.org

Evgheni Dereveanchin created OVIRT-2139: --- Summary: enforce SSL on jenkins.ovirt.org Key: OVIRT-2139 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2139 Project: oVirt - virtualization made

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 452 - Failure!

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

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

[CQ]: 91956,1 (ovirt-dwh) failed "ovirt-4.2" system tests

Change 91956,1 (ovirt-dwh) 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-node-ng-suite-master - Build # 73 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/73/ Build Number: 73 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[JIRA] (OVIRT-2092) standard-enqueue 4.2 not running

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron updated OVIRT-2092: - Resolution: Fixed Status: Done (was: To Do) > standard-enqueue 4.2 not running >

[JIRA] (OVIRT-2137) default updated cluster test fails - ACTION_TYPE_FAILED_CPU_NOT_FOUND

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron reassigned OVIRT-2137: Assignee: Dafna Ron (was: infra) > default updated cluster test fails -

[JIRA] (OVIRT-2138) Revert "open external repos for master until centos 7.5 calms down"

Dafna Ron created OVIRT-2138: Summary: Revert "open external repos for master until centos 7.5 calms down" Key: OVIRT-2138 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2138 Project: oVirt -

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-06-2018 ] [ 002_bootstrap.update_default_cluster ]

*Hi, We have a failure in ovirt-engine on master on update cluster because of "cpu not found" CQ reported the below as the most possible cause for the failure. I looked at the other changes that ran and I don't think any of them would be the cause of failure. * *Can you please have a look at

[JIRA] (OVIRT-2137) default updated cluster test fails - ACTION_TYPE_FAILED_CPU_NOT_FOUND

Dafna Ron created OVIRT-2137: Summary: default updated cluster test fails - ACTION_TYPE_FAILED_CPU_NOT_FOUND Key: OVIRT-2137 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2137 Project: oVirt -

[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren reassigned OVIRT-2136: --- Assignee: Barak Korren (was: infra) > Fwd: [ovirt-devel] Re: Propose Milan Zamazal as

[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2136: Component/s: Gerrit/git > Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer >

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=36872#comment-36872 ] Barak Korren commented on OVIRT-2078: - This is beginning to look like an epic - at least the Gerrit and CI

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=36871#comment-36871 ] Barak Korren commented on OVIRT-1834: - {quote} I know that signal handling in Jenkins is a difficult task.

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 233 - Still Failing!

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

[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer

danken created OVIRT-2136: - Summary: Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer Key: OVIRT-2136 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2136 Project: oVirt - virtualization

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=36870#comment-36870 ] Gal Ben Haim commented on OVIRT-1834: - I don't see any valid solution from OST side. [~bkor...@redhat.com]

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

[JIRA] (OVIRT-2076) name clash on vdsm module at host-deploy

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=36867#comment-36867 ] Dafna Ron commented on OVIRT-2076: -- Both passed on CQ and the vdsm build was fixed. > name clash on vdsm

[JIRA] (OVIRT-2076) name clash on vdsm module at host-deploy

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron updated OVIRT-2076: - Resolution: Fixed Status: Done (was: To Do) > name clash on vdsm module at host-deploy >

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1552

See Changes: [Sandro Bonazzola] ovirt-engine: exclude fc28 on 4.2.3 branch [Sandro Bonazzola] ovirt-release: switch to fc28 [Gal Ben Haim] OST: pin HC suites to "ovirt-srv05.phx.ovirt.org"

[JIRA] (OVIRT-2135) On failure we collect the logs from the VMs twice

Gal Ben Haim created OVIRT-2135: --- Summary: On failure we collect the logs from the VMs twice Key: OVIRT-2135 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2135 Project: oVirt - virtualization made

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 6 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 273 - Still Failing!

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

[CQ]: 82632,1 (py2exe-py2.7) failed "ovirt-master" system tests

Change 82632,1 (py2exe-py2.7) 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]: 82632,1 (py2exe-py2.7) failed "ovirt-4.2" system tests

Change 82632,1 (py2exe-py2.7) 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