date:20190514

[CQ]: 98774,3 (ovirt-engine) failed "ovirt-master" system tests

2019-05-14 Thread oVirt Jenkins

Change 98774,3 (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 about the change see:
https://gerrit.ovirt.org/#/c/98774/3

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14114/
___
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/JI54EMG7S636KN2TYLRPMQIJWZUAUCQH/

[CQ]: 99967,1 (ovirt-engine) failed "ovirt-4.3" system tests

2019-05-14 Thread oVirt Jenkins

Change 99967,1 (ovirt-engine) is probably the reason behind recent system test
failures in the "ovirt-4.3" 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://gerrit.ovirt.org/#/c/99967/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/873/
___
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/BDZMZ2GXK73TZFTL2R4A4MCLWKDWFSFA/

Re: [CQ]: 99967,1 (ovirt-engine) failed "ovirt-4.3" system tests

2019-05-14 Thread Dafna Ron

This is due to build-artifacts of fc28

seems like mock cannot find the environment yaml.

WARN: Unable to find environment.yaml file
automation/build-artifacts.environment.yaml or
automation/build-artifacts.environment.yaml.fc28, skipping
environment.yaml
 
==
Initializing chroot
 

   mock \
 

   --old-chroot \
 

   
--configdir="/home/jenkins/workspace/ovirt-engine_4.3_build-artifacts-fc28-x86_64/ovirt-engine"
\
 

   --root="mocker-fedora-28-x86_64.fc28" \
 

   --resultdir="/tmp/mock_logs.jnU7afAD/init" \
 

   --init
 

 File 
"/home/jenkins/workspace/ovirt-engine_4.3_build-artifacts-fc28-x86_64/ovirt-engine/mocker-fedora-28-x86_64.fc28.cfg",
line 79, in 
 

   from mirror_client import mirrors_from_uri, \
 

 
ModuleNotFoundError:
No module named 'yaml'
 

 
ERROR:
Error in configuration
 
Init
took 1 seconds
 

 
@@
 
@@
Tue May 14 08:08:13 UTC 2019 automation/build-artifacts.sh chroot
finished
 
@@
 took 2 seconds
 
@@
 rc = 1
 
@@
 
==
Scrubbing chroot
 

   mock \

Re: [CQ]: 98774,3 (ovirt-engine) failed "ovirt-master" system tests

2019-05-14 Thread Dafna Ron

this is a failure to build fc29 because mock could not find yaml

WARN: Unable to find environment.yaml file
automation/build-artifacts.environment.yaml or
automation/build-artifacts.environment.yaml.fc29, skipping
environment.yaml
 
==
Initializing chroot
 

   mock \
 

   --old-chroot \
 

   
--configdir="/home/jenkins/workspace/ovirt-engine_master_build-artifacts-fc29-x86_64/ovirt-engine"
\
 

   --root="mocker-fedora-29-x86_64.fc29" \
 

   --resultdir="/tmp/mock_logs.raYNKEdF/init" \
 

   --init
 

 File 
"/home/jenkins/workspace/ovirt-engine_master_build-artifacts-fc29-x86_64/ovirt-engine/mocker-fedora-29-x86_64.fc29.cfg",
line 77, in 
 

   from mirror_client import mirrors_from_uri, \
 

 
ModuleNotFoundError:
No module named 'yaml'
 

 
ERROR:
Error in configuration
 
Init
took 1 seconds
 

 
@@
 
@@
Tue May 14 07:38:37 UTC 2019 automation/build-artifacts.sh chroot
finished
 
@@
 took 2 seconds
 
@@
 rc = 1
 
@@
 
==
Scrubbing chroot

Re: [CQ]: 98774,3 (ovirt-engine) failed "ovirt-master" system tests

2019-05-14 Thread Barak Korren

Yeah, its my mock upgrade patch causing some issues - if you see this,
downgrade mock on the slave with yum and rerun the build

On Tue, 14 May 2019 at 12:29, Dafna Ron  wrote:

> this is a failure to build fc29 because mock could not find yaml
>
> WARN: Unable to find environment.yaml file 
> automation/build-artifacts.environment.yaml or 
> automation/build-artifacts.environment.yaml.fc29, skipping environment.yaml
>  
> ==
>  Initializing chroot
>  
> 
> mock \
>  
> 
> --old-chroot \
>  
> 
> 
> --configdir="/home/jenkins/workspace/ovirt-engine_master_build-artifacts-fc29-x86_64/ovirt-engine"
>  \
>  
> 
> --root="mocker-fedora-29-x86_64.fc29" \
>  
> 
> --resultdir="/tmp/mock_logs.raYNKEdF/init" \
>  
> 
> --init
>  
> 
>   File 
> "/home/jenkins/workspace/ovirt-engine_master_build-artifacts-fc29-x86_64/ovirt-engine/mocker-fedora-29-x86_64.fc29.cfg",
>  line 77, in 
>  
> 
> from mirror_client import mirrors_from_uri, \
>  
> 
>  
> ModuleNotFoundError:
>  No module named 'yaml'
>  
> 
>  
> ERROR:
>  Error in configuration
>  
> Init
>  took 1 seconds
>  
> 
>  
> @@
>  
> @@
>  Tue May 14 07:38:37 UTC 2019 automation/build-artifacts.sh chroot finished
>  
> @@
>   took 2 seconds
>  
> @@
>   rc = 1
>  
> @@
>  
>

Re: [CQ]: 98774,3 (ovirt-engine) failed "ovirt-master" system tests

2019-05-14 Thread Dafna Ron

Adding Galit

On Tue, May 14, 2019 at 10:32 AM Barak Korren  wrote:

> Yeah, its my mock upgrade patch causing some issues - if you see this,
> downgrade mock on the slave with yum and rerun the build
>
> On Tue, 14 May 2019 at 12:29, Dafna Ron  wrote:
>
>> this is a failure to build fc29 because mock could not find yaml
>>
>> WARN: Unable to find environment.yaml file 
>> automation/build-artifacts.environment.yaml or 
>> automation/build-artifacts.environment.yaml.fc29, skipping environment.yaml
>>  
>> ==
>>  Initializing chroot
>>  
>> 
>> mock \
>>  
>> 
>> --old-chroot \
>>  
>> 
>> 
>> --configdir="/home/jenkins/workspace/ovirt-engine_master_build-artifacts-fc29-x86_64/ovirt-engine"
>>  \
>>  
>> 
>> --root="mocker-fedora-29-x86_64.fc29" \
>>  
>> 
>> --resultdir="/tmp/mock_logs.raYNKEdF/init" \
>>  
>> 
>> --init
>>  
>> 
>>   File 
>> "/home/jenkins/workspace/ovirt-engine_master_build-artifacts-fc29-x86_64/ovirt-engine/mocker-fedora-29-x86_64.fc29.cfg",
>>  line 77, in 
>>  
>> 
>> from mirror_client import mirrors_from_uri, \
>>  
>> 
>>  
>> ModuleNotFoundError:
>>  No module named 'yaml'
>>  
>> 
>>  
>> ERROR:
>>  Error in configuration
>>  
>> Init
>>  took 1 seconds
>>  
>> 
>>  
>> @@
>>  
>> @@
>>  Tue May 14 07:38:37 UTC 2019 automation/build-artifacts.sh chroot finished
>>  
>> @@
>>   took 2 seconds
>>  
>> @@
>>   rc = 1
>>  
>>

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

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


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

Anton Marchukov updated OVIRT-2725:
---
Issue Type: Task  (was: By-EMAIL)

> 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: Task
>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#100102)
___
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/SSJZOQIEHEKWAO2H3T2HMS5UOH2SFEKS/

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

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


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

Anton Marchukov commented on OVIRT-2725:


[~szidmi] can you check if this something you can help with? [~ederevea] FYI.

> 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#100102)
___
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/V5KVTFZI63Y7L5HTVADAARHU6XUG6ZXK/

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

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


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

Anton Marchukov commented on OVIRT-2725:


Per [~eyon...@redhat.com] there is a cleanup but it fails without sudo, so if 
we can arrange sudo access for Jenkins then it the cleanup should work.

> 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: Task
>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#100102)
___
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/F7JV3J6CSYL5M5GKH3AE5RZFAY3DXABE/

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

2019-05-14 Thread Barak Korren (oVirt JIRA)


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

Barak Korren commented on OVIRT-2725:
-

We can't have sudo access on the s390x node - its not owned by us.

> 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: Task
>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#100102)
___
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/HR4SEHBUEVD3TKFFB2G3XJAJ3R7EN54O/

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

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


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

Eyal Edri commented on OVIRT-2725:
--

Sudo isn't needed for the cleanup, you just need to login to the VM, which is 
done from the jump host, so no need for sudo.

> 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: Task
>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#100102)
___
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/2KFRESWSAMO7KGFGLQIWCQHAMVT5MDSD/

[CQ]: 99736,5 (safelease) failed "ovirt-master" system tests

2019-05-14 Thread oVirt Jenkins

Change 99736,5 (safelease) 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 about the change see:
https://gerrit.ovirt.org/#/c/99736/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14120/
___
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/WWRUAD4SZ2QWEOHZ6BOSKQZAVBVCQSMF/

[CQ]: 99979,1 (cockpit-ovirt) failed "ovirt-4.3" system tests

2019-05-14 Thread oVirt Jenkins

Change 99979,1 (cockpit-ovirt) is probably the reason behind recent system test
failures in the "ovirt-4.3" 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://gerrit.ovirt.org/#/c/99979/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/874/
___
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/MCXAHX3JATOCSCKP2MEV4USVS776FZIC/

Re: [CQ]: 99979,1 (cockpit-ovirt) failed "ovirt-4.3" system tests

2019-05-14 Thread Dafna Ron

this was already fixed in later builds.
https://gerrit.ovirt.org/#/c/99981/ was successfully built
http://jenkins.ovirt.org/job/cockpit-ovirt_4.3_build-artifacts-el7-x86_64/50/

On Tue, May 14, 2019 at 2:13 PM oVirt Jenkins  wrote:

> Change 99979,1 (cockpit-ovirt) is probably the reason behind recent system
> test
> failures in the "ovirt-4.3" 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://gerrit.ovirt.org/#/c/99979/1
>
> For failed test results see:
> http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/874/
> ___
> 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/MCXAHX3JATOCSCKP2MEV4USVS776FZIC/
>
___
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/ZGF44CLDV56TGX24ISQJUHEWYUTWQMD2/

oVirt infra daily report - unstable production jobs - 825

2019-05-14 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/825//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins

RHEVM CI Jenkins Daily Report - 14/05/2019

00 Unstable Critical

ovirt-system-tests_hc-basic-suite-4.3