Re: OST manual jobs are pending indefinitely[0]

We're simply out of hosts, Roy reported this in OVIRT-2297 [1] so any forther tracking will be done there. [1]: https://ovirt-jira.atlassian.net/browse/OVIRT-2297 On 8 July 2018 at 18:51, Leon Goldberg wrote: > A lot of the below: > > (pending—Jenkins doesn’t have label integ-tests;

OST manual jobs are pending indefinitely[0]

A lot of the below: (pending—Jenkins doesn’t have label integ-tests; lfedora1.lf-dev.marist.edu doesn’t have label integ-tests; mirrors.phx.ovirt.org doesn’t have label integ-tests; ovirt-srv17.phx.ovirt.org is offline;

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37385#comment-37385 ] Gal Ben Haim commented on OVIRT-2264: - Looks like a race. Probably, there are still running tasks from

[JIRA] (OVIRT-2296) add me as default reviewer on ovirt-engine

Greg Sheremeta created OVIRT-2296: - Summary: add me as default reviewer on ovirt-engine Key: OVIRT-2296 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2296 Project: oVirt - virtualization made

[JIRA] (OVIRT-2297) Out of integ-tests nodes to run ost on

Roy Golan created OVIRT-2297: Summary: Out of integ-tests nodes to run ost on Key: OVIRT-2297 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2297 Project: oVirt - virtualization made easy

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 357 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/357/ Build Number: 357 Build Status: Still Failing Triggered By: Started by timer -

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 109 - 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/109/ Build Number: 109 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 173 - 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/173/ Build Number: 173 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 316 - 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/316/ Build Number: 316 Build Status: Fixed Triggered By: Started by timer - Changes

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

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 428 - Still Failing!

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

oVirt infra daily report - unstable production jobs - 515

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

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 554 - 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/554/ Build Number: 554 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 358 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/358/ Build Number: 358 Build Status: Still Failing Triggered By: Started by timer -

Jenkins build is back to normal : system-sync_mirrors-centos-updates-el7-x86_64 #1735

See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement:

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 110 - 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/110/ Build Number: 110 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 335 - 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/335/ Build Number: 335 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 174 - 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/174/ Build Number: 174 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 427 - Still Failing!

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

[JIRA] (OVIRT-2282) use SSH keys from gerrit for infra users

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37382#comment-37382 ] Ehud Yonasi commented on OVIRT-2282: I think we should use ansible playbook to run the script 1) use

Re: [CQ]: 92823,2 (vdsm) failed "ovirt-4.2" system tests

Passed CQ run: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-queue/7070/ http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2590/ On Sun, Jul 8, 2018 at 9:14 AM Daniel Belenky wrote: > I'm sorry, this is not a testing failure it's a build failure. (I'm >

[JIRA] (OVIRT-2288) typo in jenkins

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37377#comment-37377 ] Barak Korren commented on OVIRT-2288: - [~dbele...@redhat.com] I think your re-factroing work is going to

[JIRA] (OVIRT-2288) typo in jenkins

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren reassigned OVIRT-2288: --- Assignee: Daniel Belenky (was: infra) > typo in jenkins > --- > >

[JIRA] (OVIRT-2288) typo in jenkins

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2288: Issue Type: Bug (was: By-EMAIL) > typo in jenkins > --- > > Key:

[JIRA] (OVIRT-2288) typo in jenkins

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2288: Priority: Low (was: Medium) > typo in jenkins > --- > > Key:

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

This failure is due to my tests. There's no need to re-add this change as it already passed CQ. On Sun, Jul 8, 2018 at 8:16 AM oVirt Jenkins wrote: > Change 92694,2 (vdsm) is probably the reason behind recent system test > failures > in the "ovirt-master" change queue and needs to be fixed. > >

[JIRA] (OVIRT-2282) use SSH keys from gerrit for infra users

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37380#comment-37380 ] Barak Korren commented on OVIRT-2282: - As discussed in an infra meeting the approach I think we should

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 356 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/356/ Build Number: 356 Build Status: Still Failing Triggered By: Started by timer -

[ CQ Failure Report ] [ RHV Master - ds vdsm ] [ 07-07-2018 ] [ post-004_basic_sanity.py ]

Link to suspected patches: https://gerrit.ovirt.org/#/c/92694/ Link to the job: https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv-master_change-queue-tester/50/ Link to all logs: https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv-master_change-queue-tester/50/

[CQ]: 92829,2 (ovirt-engine-metrics) failed "ovirt-4.2" system tests

Change 92829,2 (ovirt-engine-metrics) 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

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 108 - 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/108/ Build Number: 108 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

Re: [CQ]: 92823,2 (vdsm) failed "ovirt-4.2" system tests

I'm sorry, this is not a testing failure it's a build failure. (I'm testing on master not 4.2) On Sun, Jul 8, 2018 at 8:24 AM Daniel Belenky wrote: > Please ignore. Testing again.. > > On Sun, Jul 8, 2018 at 8:22 AM oVirt Jenkins wrote: > >> Change 92823,2 (vdsm) is probably the reason behind

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37378#comment-37378 ] Barak Korren commented on OVIRT-2287: - On 6 July 2018 at 11:57, Sandro Bonazzola wrote: > >

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 426 - Still Failing!

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

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 315 - Still Failing!

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

[JIRA] (OVIRT-2282) use SSH keys from gerrit for infra users

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37384#comment-37384 ] Barak Korren commented on OVIRT-2282: - {quote} just my set of thoughts, if we have an automation

[JIRA] (OVIRT-2282) use SSH keys from gerrit for infra users

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37384#comment-37384 ] Barak Korren edited comment on OVIRT-2282 at 7/8/18 11:50 AM: -- {quote} just my

[JIRA] (OVIRT-2134) Investigate why HC suites fail on slaves with *-IBRS CPU

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gal Ben Haim reassigned OVIRT-2134: --- Assignee: Gal Ben Haim (was: infra) > Investigate why HC suites fail on slaves with

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 106 - Fixed!

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

Change in stdci-staging[master]: Dummy change to test nod allocation

>From Barak Korren : Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/169 ) Change subject: Dummy change to test nod allocation .. Patch Set 1: ci test please -- To view, visit

[CQ]: 92869,2 (ovirt-engine) failed "ovirt-4.2" system tests

Change 92869,2 (ovirt-engine) 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

[JIRA] (OVIRT-2291) Migrate all tests to use engine SDK V4

Gal Ben Haim created OVIRT-2291: --- Summary: Migrate all tests to use engine SDK V4 Key: OVIRT-2291 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2291 Project: oVirt - virtualization made easy

[JIRA] (OVIRT-2293) basic-suite-master: migrate 004_basic_sanity.run_vms to use engine SDK V4

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gal Ben Haim updated OVIRT-2293: Epic Link: OVIRT-2291 > basic-suite-master: migrate 004_basic_sanity.run_vms to use engine SDK V4

[JIRA] (OVIRT-2293) basic-suite-master: migrate 004_basic_sanity.run_vms to use engine SDK V4

Gal Ben Haim created OVIRT-2293: --- Summary: basic-suite-master: migrate 004_basic_sanity.run_vms to use engine SDK V4 Key: OVIRT-2293 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2293 Project:

[JIRA] (OVIRT-2292) Open a ticket for each test that should be migrated to use engine SDK V4

Gal Ben Haim created OVIRT-2292: --- Summary: Open a ticket for each test that should be migrated to use engine SDK V4 Key: OVIRT-2292 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2292 Project:

[JIRA] (OVIRT-2292) Open a ticket for each test that should be migrated to use engine SDK V4

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gal Ben Haim updated OVIRT-2292: Epic Link: OVIRT-2291 > Open a ticket for each test that should be migrated to use engine SDK V4

[JIRA] (OVIRT-2295) HE symlinks for deployment scrips

Galit Rosenthal created OVIRT-2295: -- Summary: HE symlinks for deployment scrips Key: OVIRT-2295 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2295 Project: oVirt - virtualization made easy

[JIRA] (OVIRT-2294) HC symlinks to deployment scripts

Galit Rosenthal created OVIRT-2294: -- Summary: HC symlinks to deployment scripts Key: OVIRT-2294 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2294 Project: oVirt - virtualization made easy

Change in stdci-staging[master]: Dummy change to test nod allocation

>From Barak Korren : Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/169 ) Change subject: Dummy change to test nod allocation .. Patch Set 1: ci test please -- To view, visit

Change in stdci-staging[master]: Dummy change to test nod allocation

>From Barak Korren : Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/169 ) Change subject: Dummy change to test nod allocation .. Patch Set 1: ci test please -- To view, visit

Change in stdci-staging[master]: Dummy change to test nod allocation

>From Barak Korren : Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/169 ) Change subject: Dummy change to test nod allocation .. Patch Set 1: ci test please -- To view, visit

Change in stdci-staging[master]: Dummy change to test nod allocation

>From Barak Korren : Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/169 ) Change subject: Dummy change to test nod allocation .. Patch Set 1: ci test please -- To view, visit

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 553 - 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/553/ Build Number: 553 Build Status: Failure Triggered By: Started by timer - Changes Since Last

Re: [CQ]: 92829,2 (ovirt-engine-metrics) failed "ovirt-4.2" system tests

Passed CQ run. http://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-4.2_change-queue-tester/detail/ovirt-4.2_change-queue-tester/2593/pipeline On Sun, Jul 8, 2018 at 11:39 AM oVirt Jenkins wrote: > Change 92829,2 (ovirt-engine-metrics) is probably the reason behind recent > system test

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gal Ben Haim reassigned OVIRT-2259: --- Assignee: Gal Ben Haim (was: infra) > fc28: Failed to add ovirt-host: "The key algorithm

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

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