date:20190513

[oVirt Jenkins] ovirt-release_master_build-artifacts-fcraw-x86_64 - Build # 104 - Failure!

2019-05-13 Thread jenkins

Project: 
http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86_64/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86_64/104/
Build Number: 104
Build Status:  Failure
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #104
[Sandro Bonazzola] centos: switch to 4.4 testing repos

[Barak Korren] build_images: Run with STDCI

[Barak Korren] update_images: Add playbook for image updating

[Sandro Bonazzola] ovirt-engine: add fc29 on master

[Barak Korren] mirror_client: Fix race condition in tests




-
Failed Tests:
-
No tests ran.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WYWOWEBKVTUX3C3XHGZIX6BQ24STOCJ7/

oVirt infra daily report - unstable production jobs - 824

2019-05-13 Thread jenkins

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/824//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins

RHEVM CI Jenkins Daily Report - 13/05/2019

00 Unstable Critical

ovirt-system-tests_hc-basic-suite-4.2

This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the
jenkins repo.

ovirt-system-tests_hc-basic-suite-4.3

This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the
jenkins repo.

ovirt-system-tests_he-basic-iscsi-suite-4.2

This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the
jenkins repo.

ovirt-system-tests_network-suite-master

This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the
jenkins repo.

ovirt-system-tests_openshift-on-ovirt-suite-4.2

This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the
jenkins repo.

___
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 Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EHIHR5HJSB6QIZ7S5IO5XDC6HUBCULLA/

[CQ]: 47f3db5 (v2v-conversion-host) failed "ovirt-4.2" system tests

2019-05-13 Thread oVirt Jenkins

Change 47f3db5 (v2v-conversion-host) 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 change see:
https://github.com/oVirt/v2v-conversion-host/commit/47f3db53883f2133b5ba5e7130293754887fbac7

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4339/
___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/IWWOIGB24P6NGWJGCGBKRHG7ASUJYWA6/

[JIRA] (OVIRT-2727) Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer

2019-05-13 Thread Greg Sheremeta (oVirt JIRA)

Greg Sheremeta created OVIRT-2727:
-

 Summary: Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend 
maintainer
 Key: OVIRT-2727
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2727
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Greg Sheremeta
Assignee: infra


Please grant Ales +2 access on ovirt-engine

-- Forwarded message -
From: Greg Sheremeta 
Date: Mon, May 13, 2019 at 2:52 PM
Subject: Re: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer
To: devel , Ales Musil 


Thanks everyone. Ales, congrats, and be careful :)

On Mon, May 13, 2019 at 12:11 PM Tal Nisan  wrote:

> +1
>
> On Thu, May 9, 2019 at 9:37 AM Tomas Jelinek  wrote:
>
>>
>>
>> On Sun, May 5, 2019 at 8:10 PM Daniel Erez  wrote:
>>
>>>
>>>
>>> On Thu, May 2, 2019 at 9:42 PM Greg Sheremeta 
>>> wrote:
>>>
 Hi all,

 I'd like to propose Ales Musil as a frontend maintainer for network
 parts of the admin portal UI. Since joining the team 2 years ago, Ales has
 quickly become very knowledgeable about all of the GWT intricacies of the
 admin portal. I trust his expertise and judgment.

>>>
>> +1 fur sure!
>>
>>
>>>
>>> +1
>>>
>>>

 Best wishes,
 Greg

 --

 Greg Sheremeta

 Senior Software Engineer

 Red Hat 
 
 ___
 Devel mailing list -- de...@ovirt.org
 To unsubscribe send an email to devel-le...@ovirt.org
 Privacy Statement: https://www.ovirt.org/site/privacy-policy/
 oVirt Code of Conduct:
 https://www.ovirt.org/community/about/community-guidelines/
 List Archives:
 https://lists.ovirt.org/archives/list/de...@ovirt.org/message/ML5UVKYABG744KHEBSMMEB26D3RYOWR7/

>>> ___
>>> Devel mailing list -- de...@ovirt.org
>>> To unsubscribe send an email to devel-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/de...@ovirt.org/message/N7WW4AWIZQII56TH7ATXACH5HPN5OFCC/
>>>
>> ___
>> Devel mailing list -- de...@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/de...@ovirt.org/message/QLLIXIVBQ2SKBCZ3E2I3A33K62PW2V6V/
>>
> ___
> Devel mailing list -- de...@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/de...@ovirt.org/message/OWAOTCLUMK7LNZKK2XLJ6ZH5JOK5MK36/
>


-- 

Greg Sheremeta

Senior Software Engineer, Service Delivery

Red Hat 



-- 

Greg Sheremeta

Senior Software Engineer, Service Delivery

Red Hat 




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100101)
___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/XPWGMW6N37JZCZKTYZI7FQBIDKS7QVPY/

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

2019-05-13 Thread jenkins

Failed to run project_setup.sh for:
#2471 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on lfedora1.lf-dev.marist.edu.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/MFNALZRITXR6EXOALXLREBSJWTSL7WB7/

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

2019-05-13 Thread jenkins

Failed to run project_setup.sh for:
#2471 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on lfedora1.lf-dev.marist.edu.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/DQTFGQOQNYWQT32R5VUOI3GSH35AEKAA/

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

2019-05-13 Thread jenkins

Failed to run project_setup.sh for:
#2471 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on lfedora1.lf-dev.marist.edu.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BWY3WTKJH23X3YJF4QOKO7TQRU2RHHV2/

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

2019-05-13 Thread jenkins

Failed to run project_setup.sh for:
#2471 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0089.workers-phx.ovirt.org.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/B7FWUQSQEWQLYAVTCPGUBNLW3XT6BD7U/

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

2019-05-13 Thread jenkins

Failed to run project_setup.sh for:
#2471 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0091.workers-phx.ovirt.org.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5PH475CV42DKINDPDMPKLDTTZUUEGENM/

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

2019-05-13 Thread jenkins

Failed to run project_setup.sh for:
#2471 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0044.workers-phx.ovirt.org.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/AZZ5N6UAZOLBNFHVSVETZ4VHIKUQSRFZ/

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

2019-05-13 Thread jenkins

Failed to run project_setup.sh for:
#2471 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0038.workers-phx.ovirt.org.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ASSPZL3G3OQAPRHUWBMLF4B4U5FXBR37/

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

2019-05-13 Thread jenkins

Failed to run project_setup.sh for:
#2471 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0003.workers-phx.ovirt.org.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OAMQ6ABT2WKFHN6SXC7BA3QOD266IN5F/

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

2019-05-13 Thread jenkins

Failed to run project_setup.sh for:
#2471 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0221.workers-phx.ovirt.org.___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/UEJ6RSAB3B7A3YCKP7ICGLRIL6W3HLBL/

ovrit hyperconverged replicas

2019-05-13 Thread rt . tarantino

Hello

is it possible to have a replica 4 or greater gluster with hyperconverged ovirt?
___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/XMMIQOT4LACYIFZGQWS7SXEDNLPLSIEQ/

[JIRA] (OVIRT-2726) Upgrade hyperkitty to 1.2.2

2019-05-13 Thread Anton Marchukov (oVirt JIRA)


 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Marchukov reassigned OVIRT-2726:
--

Assignee: Marc Dequènes (Duck)  (was: infra)

> Upgrade hyperkitty to 1.2.2
> ---
>
> Key: OVIRT-2726
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2726
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Marc Dequènes (Duck)
>
> We are currently running hyperkitty 1.1.5 (which seems not being released
> by the developers), latest one is 1.2.2.It introduces a few featrue and
> support for newer django.
> -- 
> Sandro Bonazzola
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> Red Hat EMEA 
> sbona...@redhat.com
> 
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100101)

___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PQTKCZD7QQDUSPDADA3MWS6CD6VLWZY6/

[JIRA] (OVIRT-2726) Upgrade hyperkitty to 1.2.2

2019-05-13 Thread sbonazzo (oVirt JIRA)

sbonazzo created OVIRT-2726:
---

 Summary: Upgrade hyperkitty to 1.2.2
 Key: OVIRT-2726
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2726
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra


We are currently running hyperkitty 1.1.5 (which seems not being released
by the developers), latest one is 1.2.2.It introduces a few featrue and
support for newer django.

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com





--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100101)
___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PHUPP5QW2BV6X4TOETCMIK7N4PV3PUQY/

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system

2019-05-13 Thread Eyal Edri (oVirt JIRA)


[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39310#comment-39310
 ] 

Eyal Edri commented on OVIRT-2725:
--

I fixed it yesterday by cleaning up the slave, anyone can do with the commands 
written in the FAQ doc.
What we need to add is a cleanup script that will do it on a regular basis  ( 2 
lines of bash ):

(after you login to the VM) with sudo:

mock -r ./fedora-28-s390x.cfg --shell
rm rfv /hostvar/cache/mock/fedora??s390x*

> Build artifacts failed - not enough free space on file system
> -
>
> Key: OVIRT-2725
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> I had this failure in yum install:
> [2019-05-12T14:54:55.706Z] Error Summary
> [2019-05-12T14:54:55.706Z] -
> [2019-05-12T14:54:55.706Z] Disk Requirements:
> [2019-05-12T14:54:55.706Z]At least 70MB more space needed on the /
> filesystem.
> Build:
> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/247/pipeline
> Trying build again, hopefully will get a slave with more space...
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100101)
___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/27SKSDBRXPXB7455XG37Q42O7E2SBP43/

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system

2019-05-13 Thread Dafna Ron (oVirt JIRA)


[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39309#comment-39309
 ] 

Dafna Ron commented on OVIRT-2725:
--

The build that failed is fc28.x390:
15:52:20  Running on lfedora1.lf-dev.marist.edu in 
/home/ovirt/workspace/standard-manual-runner
Agent lfedora1.lf-dev.marist.edu (lfedora1.lf-dev.marist.edu s390x loaned VM)

[~ederevea] can you please take a look? 

> Build artifacts failed - not enough free space on file system
> -
>
> Key: OVIRT-2725
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> I had this failure in yum install:
> [2019-05-12T14:54:55.706Z] Error Summary
> [2019-05-12T14:54:55.706Z] -
> [2019-05-12T14:54:55.706Z] Disk Requirements:
> [2019-05-12T14:54:55.706Z]At least 70MB more space needed on the /
> filesystem.
> Build:
> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/247/pipeline
> Trying build again, hopefully will get a slave with more space...
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100101)
___
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 Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/IDBU3KJ7QXYNSATY57RBREI2X5PWWAYX/