[JIRA] (OVIRT-2225) 001_upgrade_engine.test_initialize_engine failed due to missing ovirt-host-deploy pacakge

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37192#comment-37192 ] Barak Korren commented on OVIRT-2225: - so basically this is an ovirt-engine regression and the specfile

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

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

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

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

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

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

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 262 - Failure!

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/262/ Build Number: 262 Build Status: Failure Triggered By: Started by timer - Changes

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

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

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

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

Change 92271,11 (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

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 419 - Failure!

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

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 319 - Failure!

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

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

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

Fwd: [CQ]: 92305,5 (ovirt-engine) failed "ovirt-master" system tests

ovirt-host-deploy is now provided by python2-ovirt-host-deploy. https://gerrit.ovirt.org/92405 https://ovirt-jira.atlassian.net/browse/OVIRT-2225 -- Forwarded message -- From: oVirt Jenkins Date: Wed, Jun 20, 2018 at 3:33 PM Subject: [CQ]: 92305,5 (ovirt-engine) failed

[JIRA] (OVIRT-2225) 001_upgrade_engine.test_initialize_engine failed due to missing ovirt-host-deploy pacakge

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37190#comment-37190 ] Dafna Ron commented on OVIRT-2225: -- ovirt-host-deploy is provided by python2-ovirt-host-deploy

[JIRA] (OVIRT-2225) 001_upgrade_engine.test_initialize_engine failed due to missing ovirt-host-deploy pacakge

Dafna Ron created OVIRT-2225: Summary: 001_upgrade_engine.test_initialize_engine failed due to missing ovirt-host-deploy pacakge Key: OVIRT-2225 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2225

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

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

[CQ]: 92305,5 (ovirt-engine) failed "ovirt-master" system tests

Change 92305,5 (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

[JIRA] (OVIRT-2219) update minitar version in infra-puppet Gemfile.lock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2219: --- Assignee: Evgheni Dereveanchin (was: infra) > update minitar version in

[JIRA] (OVIRT-2219) update minitar version in infra-puppet Gemfile.lock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin updated OVIRT-2219: Issue Type: Sub-task (was: Task) Parent: OVIRT-476 > update minitar

[JIRA] (OVIRT-2223) upgrade CentOS CI slaves

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2223: --- Assignee: Evgheni Dereveanchin (was: infra) > upgrade CentOS CI slaves >

[JIRA] (OVIRT-2223) upgrade CentOS CI slaves

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin updated OVIRT-2223: Issue Type: Sub-task (was: Task) Parent: OVIRT-2045 > upgrade CentOS CI

[JIRA] (OVIRT-2223) upgrade CentOS CI slaves

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37185#comment-37185 ] Evgheni Dereveanchin commented on OVIRT-2223: - As most of our slaves are VMs it's probably easiest

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 118 - Failure!

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/118/ Build Number: 118 Build Status: Failure Triggered By: Started by timer - Changes Since Last

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

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

[JIRA] (OVIRT-2224) standard-enqueue issues warning about projects with V2 jobs

Barak Korren created OVIRT-2224: --- Summary: standard-enqueue issues warning about projects with V2 jobs Key: OVIRT-2224 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2224 Project: oVirt -

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

Re: Push rights to vdsm

No worries, glad it works for you. Don't hesitate to reach out to infra again if you have any issues. On Wed, Jun 20, 2018 at 1:29 PM Tomasz Barański wrote: > Eyal, > > I didn't set `username` in gerrit. Seems to have missed this step. > > It works now, sorry to bother you. > > Tomo > > On

Re: Push rights to vdsm

Eyal, I didn't set `username` in gerrit. Seems to have missed this step. It works now, sorry to bother you. Tomo On 20.06.2018 12:03, Eyal Edri wrote: Any registered user have push rights to new patches, did you follow the guidelines on how to contribute to and oVirt project?

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

[JIRA] (OVIRT-2223) upgrade CentOS CI slaves

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37183#comment-37183 ] eyal edri commented on OVIRT-2223: -- Any way we can automate this upgrade? are we using an Ansible playbook

Re: [JIRA] (OVIRT-2223) upgrade CentOS CI slaves

Any way we can automate this upgrade? are we using an Ansible playbook for it? On Wed, Jun 20, 2018 at 1:02 PM Evgheni Dereveanchin (oVirt JIRA) < j...@ovirt-jira.atlassian.net> wrote: > Evgheni Dereveanchin created OVIRT-2223: > --- > >

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 307 - Failure!

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

Re: Push rights to vdsm

Any registered user have push rights to new patches, did you follow the guidelines on how to contribute to and oVirt project? https://ovirt.org/develop/dev-process/working-with-gerrit/ On Wed, Jun 20, 2018 at 1:00 PM Tomasz Barański wrote: > Hello, > > As a new Red Hatter, I need push right to

[JIRA] (OVIRT-2223) upgrade CentOS CI slaves

Evgheni Dereveanchin created OVIRT-2223: --- Summary: upgrade CentOS CI slaves Key: OVIRT-2223 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2223 Project: oVirt - virtualization made easy

Push rights to vdsm

Hello, As a new Red Hatter, I need push right to `vdsm` project in oVirt's gerrit. Thank you Tomasz ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement:

[JIRA] (OVIRT-2222) Package retention policy for tested repo

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

[JIRA] (OVIRT-2216) Cannot find a valid baseurl for repo: base/7/x86_64

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dafna Ron reassigned OVIRT-2216: Assignee: Dafna Ron (was: infra) > Cannot find a valid baseurl for repo: base/7/x86_64 >

[JIRA] (OVIRT-2222) Package retention policy for tested repo

Ehud Yonasi created OVIRT-: -- Summary: Package retention policy for tested repo Key: OVIRT- URL: https://ovirt-jira.atlassian.net/browse/OVIRT- Project: oVirt - virtualization made easy

[JIRA] (OVIRT-2222) Package retention policy for tested repo

[ https://ovirt-jira.atlassian.net/browse/OVIRT-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ehud Yonasi updated OVIRT-: --- Epic Link: OVIRT-1744 > Package retention policy for tested repo >

[JIRA] (OVIRT-2216) Cannot find a valid baseurl for repo: base/7/x86_64

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37178#comment-37178 ] eyal edri commented on OVIRT-2216: -- [~gbenh...@redhat.com] [~dron] please check if this is an issue on open

[JIRA] (OVIRT-2216) Cannot find a valid baseurl for repo: base/7/x86_64

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37177#comment-37177 ] Evgheni Dereveanchin commented on OVIRT-2216: - > Cannot find a valid baseurl for repo:

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

See Changes: [Daniel Belenky] Install python-six during global-setup [Barak Korren] Make mock_runner use curl instead of wget [Barak Korren] Fix proxied configuration for FC27 and

[JIRA] (OVIRT-2164) Migrate repoman to STDCI v2

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emil Natan reassigned OVIRT-2164: - Assignee: Emil Natan (was: infra) > Migrate repoman to STDCI v2 > ---

[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37174#comment-37174 ] Barak Korren edited comment on OVIRT-2175 at 6/20/18 7:51 AM: -- We need to map out

[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37174#comment-37174 ] Barak Korren commented on OVIRT-2175: - We need to map out the projects first - that will take some time...

[JIRA] (OVIRT-1832) Vdsm make install on fc27 fails with "package vdsm-... is disabled"

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37173#comment-37173 ] Barak Korren commented on OVIRT-1832: - Is this still relevant given that the fc27 job for vdsm master was

[JIRA] (OVIRT-1832) Vdsm make install on fc27 fails with "package vdsm-... is disabled"

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri updated OVIRT-1832: - Sprint: (was: oVirt Sprint 1) > Vdsm make install on fc27 fails with "package vdsm-... is disabled" >

[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37172#comment-37172 ] eyal edri commented on OVIRT-2175: -- I agree, let's start tracking which projects are on V1 and schedule dates

[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37171#comment-37171 ] Daniel Belenky commented on OVIRT-2175: --- We need to add more tasks with more projects that we find

Re: [CQ]: 92362, 1 (ovirt-jboss-modules-maven-plugin) failed "ovirt-master" system tests

On 20 June 2018 at 09:51, Sandro Bonazzola wrote: > > > 2018-06-19 16:40 GMT+02:00 Emil Natan : > >> Hi, >> >> You added dnf to automation/check-merged.packages, but it does not >> actually install yum. You can either install package dnf-yum which provides >> link yum->dnf or install package

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 372 - Failure!

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/372/ Build Number: 372 Build Status: Failure Triggered By: Started by timer -

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 497 - Still Failing!

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

Re: [CQ]: 92362, 1 (ovirt-jboss-modules-maven-plugin) failed "ovirt-master" system tests

2018-06-19 16:40 GMT+02:00 Emil Natan : > Hi, > > You added dnf to automation/check-merged.packages, but it does not > actually install yum. You can either install package dnf-yum which provides > link yum->dnf or install package yum. > Hi, thanks for having reported check-merged.sh is failing

[JIRA] (OVIRT-2180) Missing packages when trying to create reposync-config ovirt-master on Fedora 28

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37170#comment-37170 ] sbonazzo commented on OVIRT-2180: - We already dropped fluentd support on Fedora 28, you can go ahead. >

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37169#comment-37169 ] Barak Korren commented on OVIRT-2201: - {quote} * get the general CI health of a release (master vs 4.2)

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37168#comment-37168 ] sbonazzo commented on OVIRT-2201: - {quote}"As an oVirt developer, I want to see the build status for the HEAD