Build failed in Jenkins: ovirt_4.0_publish-rpms_nightly #50

See -- Started by timer Building on master in workspace [WS-CLEANUP] Deleting project workspace... [workspace] $ /bin/bash

[oVirt Jenkins] ovirt-engine_4.0_upgrade-from-3.6_el7_merged - Build # 177 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/177/ Build Number: 177 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/59502

[oVirt Jenkins] ovirt-engine_4.0_upgrade-from-3.6_el7_merged - Build # 175 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/175/ Build Number: 175 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/59548

[oVirt Jenkins] ovirt-engine_4.0_upgrade-from-4.0_el7_merged - Build # 181 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/181/ Build Number: 181 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/59548

[oVirt Jenkins] ovirt-engine_4.0_upgrade-from-4.0_el7_merged - Build # 183 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/183/ Build Number: 183 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/59502

[oVirt Jenkins] ovirt-engine_4.0_upgrade-from-4.0_el7_merged - Build # 182 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/182/ Build Number: 182 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/59549

[oVirt Jenkins] ovirt-engine_4.0_upgrade-from-3.6_el7_merged - Build # 176 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/176/ Build Number: 176 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/59549

[oVirt Jenkins] ovirt-engine_4.0_upgrade-from-4.0_el7_merged - Build # 180 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-4.0_el7_merged/180/ Build Number: 180 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/59550

[oVirt Jenkins] ovirt-engine_4.0_upgrade-from-3.6_el7_merged - Build # 174 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/174/ Build Number: 174 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/59550

[JIRA] (OVIRT-604) partition and mount SSDs on PHX hosts

[ https://ovirt-jira.atlassian.net/browse/OVIRT-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-604: -- Assignee: Evgheni Dereveanchin (was: infra) > partition and mount SSDs on

Re: PHX updates - hypervisors in Jenkins datacenter

Will do! Logged a Jira task to track progress: https://ovirt-jira.atlassian.net/browse/OVIRT-604 Regards, Evgheni Dereveanchin - Original Message - From: "Eyal Edri" To: "Evgheni Dereveanchin" Cc: "infra" Sent: Tuesday, 21

[JIRA] (OVIRT-604) partition and mount SSDs on PHX hosts

Evgheni Dereveanchin created OVIRT-604: -- Summary: partition and mount SSDs on PHX hosts Key: OVIRT-604 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-604 Project: oVirt - virtualization made

Re: PHX updates - hypervisors in Jenkins datacenter

+1, You can also take advantage of this to install and mount the SSDs we have on 10 of the hypervisors, as preparation for the local disk hook usage. On Tue, Jun 21, 2016 at 6:41 PM, Evgheni Dereveanchin wrote: > Hi Eyal, > > Indeed, all hosts have to have 3.6 level

Re: PHX updates - hypervisors in Jenkins datacenter

Hi Eyal, Indeed, all hosts have to have 3.6 level packages installed before the engine gets upgraded. In this particular case we have some catching up to do on the host OS side of the infra. After host re-deploy is done we'll update VDSM and friends to 3.6, upgrade the Engine and change the

Re: PHX updates - hypervisors in Jenkins datacenter

I think the next step after this will be to upgrade hypervisors to 3.6 while keeping the engine 3.5 with cluster level 3.5. Can you confirm the is the recommended upgrade flow to users as well? On Tue, Jun 21, 2016 at 5:13 PM, Evgheni Dereveanchin wrote: > I'm back to the

[JIRA] (OVIRT-597) failing to log into jenkins.ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nadav Goldin updated OVIRT-597: --- Resolution: Fixed Assignee: Nadav Goldin (was: infra) Status: Done (was: To Do)

[JIRA] (OVIRT-603) [test] please ignore

[ https://ovirt-jira.atlassian.net/browse/OVIRT-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nadav Goldin deleted OVIRT-603: --- > [test] please ignore > > > Key: OVIRT-603 > URL:

[JIRA] (OVIRT-602) test-ticket

[ https://ovirt-jira.atlassian.net/browse/OVIRT-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nadav Goldin reassigned OVIRT-602: -- Assignee: Nadav Goldin (was: infra) > test-ticket > --- > > Key:

[JIRA] (OVIRT-603) [test] please ignore

Nadav Goldin created OVIRT-603: -- Summary: [test] please ignore Key: OVIRT-603 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-603 Project: oVirt - virtualization made easy Issue Type:

[JIRA] (OVIRT-601) another incorrect CI-1

[ https://ovirt-jira.atlassian.net/browse/OVIRT-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-601: --- Assignee: infra > another incorrect CI-1 > -- >

[JIRA] (OVIRT-600) Fwd from danken — false CI-1

[ https://ovirt-jira.atlassian.net/browse/OVIRT-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-600: --- Assignee: infra > Fwd from danken — false CI-1 >

[JIRA] (OVIRT-597) failing to log into jenkins.ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-597: --- Assignee: infra > failing to log into jenkins.ovirt.org >

[JIRA] (OVIRT-599) incorrect CI-1

[ https://ovirt-jira.atlassian.net/browse/OVIRT-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-599: --- Assignee: infra > incorrect CI-1 > -- > >

Re: PHX updates - hypervisors in Jenkins datacenter

I'm back to the office and moving forward with the upgrade. Will now re-provision ovirt-srv01 which is part of the HostedEngine cluster and was the first host of the environment. Now backing up its configs just to be sure. There is 6 VMs still running on F20 hosts. Once there's two EL7 hosts in

Re: [JIRA] (OVIRT-408) migrate mailman from linode to PHX and upgrade to mailman 3

On 21 June 2016 at 12:14, Marc Dequènes (Duck) wrote: > > Maybe freeipa could help building this. I think Misc as more experience > with this; he could probably give some advice. Probably not FreeIPA as it is based around its own LDAP, but maybe something like Keycloak working

Re: [JIRA] (OVIRT-408) migrate mailman from linode to PHX and upgrade to mailman 3

Quack, On 06/17/2016 04:55 PM, Barak Korren wrote: > As long as we allow more then one provider, and also allow for some free > ones like Fedora its not bad at all IMO. And it has the nice benofit of > not having to secure any user credential database on our infra. It's not bad, just better to

Re: Gerrit manual trigger permissions

done. On Tue, Jun 21, 2016 at 10:06 AM, Michal Skrivanek < michal.skriva...@redhat.com> wrote: > > On 21 Jun 2016, at 09:00, Martin Perina wrote: > > Unfortunately no, I've just tried to login again with my username mperina > and same error is raised again: > > mperina

Re: Gerrit manual trigger permissions

> On 21 Jun 2016, at 09:00, Martin Perina wrote: > > Unfortunately no, I've just tried to login again with my username mperina and > same error is raised again: > > mperina is missing the Gerrit/ManualTrigger permission while you’re at it, could you update it for me

Re: Gerrit manual trigger permissions

Unfortunately no, I've just tried to login again with my username mperina and same error is raised again: mperina is missing the Gerrit/ManualTrigger permission Martin On Mon, Jun 20, 2016 at 9:51 PM, Eyal Edri wrote: > You should be good to go. > This was part of