[CQ]: 99792,4 (ioprocess) failed "ovirt-master" system tests

2019-06-28 Thread oVirt Jenkins
Change 99792,4 (ioprocess) 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/99792/4

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


[oVirt Jenkins] ovirt-release_master_build-artifacts-fcraw-x86_64 - Build # 156 - Still Failing!

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

-
Changes Since Last Success:
-
Changes for Build #149
[Eyal Edri] add ct...@redhat.com

[Sandro Bonazzola] fc29: add gluster-6 fedora 29 repo


Changes for Build #150
[Sandro Bonazzola] fc29: add gluster-6 fedora 29 repo


Changes for Build #151
[Sandro Bonazzola] fc29: add gluster-6 fedora 29 repo

[Barak Korren] pusher: Support anonymous_clone_url in push maps

[Barak Korren] usrc: Pix PEP8/PyLint/PyFlakes issues

[Barak Korren] usrc: Use `anonymous_clone_url` from push map

[Barak Korren] pusher: Add push map checking

[Barak Korren] stdci_runner: Force FCRAW jobs on slaves >= FC29

[Barak Korren] mock_runner: Seamless SSH from mock_runner

[Barak Korren] stdci_node: Fix ContextVariableSet.get() issue

[Barak Korren] mock_runner: pass shellcheck

[Barak Korren] check-patch: pass shellcheck

[Barak Korren] mock_runner: Add jenkins env vars


Changes for Build #152
[Sandro Bonazzola] fc29: add gluster-6 fedora 29 repo

[Galit Rosenthal] Remove unused files which uses mock_genconfig

[Galit Rosenthal] Update packages python36, Change cmd python3

[Galit Rosenthal] mock_setup remove mock_genconfig

[Galit Rosenthal] Remove mock_genconfig file and test from check_patch

[Gal Ben Haim] kubevirt: Add jobs for HCO

[Barak Korren] global_setup: Ensure /var/lib/stdci/shared exists


Changes for Build #153
[Sandro Bonazzola] fc29: add gluster-6 fedora 29 repo


Changes for Build #154
[Sandro Bonazzola] fc29: add gluster-6 fedora 29 repo

[Gal Ben Haim] Adding ci-toolbox to the path


Changes for Build #155
[Sandro Bonazzola] fc29: add gluster-6 fedora 29 repo

[Barak Korren] pipeline-loader: checkout functions return data

[Barak Korren] stdci_project: Preserve checkout data

[Barak Korren] standard-stage: Save STDCI info to build params

[Evgheni Dereveanchin] Set baseurl for proxied fedora mock configs


Changes for Build #156
[Sandro Bonazzola] fc29: add gluster-6 fedora 29 repo




-
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/7DHJJ3KKRBD3W2SHIZMY4D4BLYHBGLTX/


oVirt infra daily report - unstable production jobs - 870

2019-06-28 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/870//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins
 
 
 
 RHEVM CI Jenkins Daily Report - 28/06/2019
 
00 Unstable Critical
 
   
   ovirt-appliance_4.2_build-artifacts-el7-x86_64
   
   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-appliance_4.3_build-artifacts-el7-x86_64
   
   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-appliance_master_build-artifacts-el7-x86_64
   
   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-appliance_ovirt-4.2_build-artifacts-el7-x86_64
   
   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-release_master_build-artifacts-fcraw-x86_64
   
   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_hc-basic-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_he-basic-iscsi-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-role-remote-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-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-node-ng-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_master_standard-poll-upstream-sources
   
   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: 

[CQ]: 101190,12 (ovirt-engine) failed "ovirt-master" system tests

2019-06-28 Thread oVirt Jenkins
Change 101190,12 (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/101190/12

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


[Ovirt] [CQ weekly status] [28-06-2019]

2019-06-28 Thread Dafna Ron
This mail is to provide the current status of CQ and allow people to review
status before and after the weekend.
Please refer to below colour map for further information on the meaning of
the colours.

*CQ-4.2*:  GREEN (#1)

Last failure was on 28-06 for mom due to failed test:
002_bootstrap.add_master_storage_domain. this is a known issue which has a
fix which was probably not added to the upgrade suite. I re-triggered the
change to see if it passes


*CQ-4.3*:  GREEN (#2)

Last failure was on 27-06-2019 for project ovirt-web-ui due to test
get_host_device which seemed to be a race. I re-triggered the patch and it
passed.

*CQ-Master:*  GREEN (#1)

Last failure was on 28-06-3019 for project ovirt-node-ng-image on
build-artifacts for fc29
There is a ticket opened https://ovirt-jira.atlassian.net/browse/OVIRT-2747

 Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found
here:

[1]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-queue-tester/

[2]
https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-queue-tester/

[3]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/

Happy week!
Dafna


---
COLOUR MAP

Green = job has been passing successfully

** green for more than 3 days may suggest we need a review of our test
coverage


   1.

   1-3 days   GREEN (#1)
   2.

   4-7 days   GREEN (#2)
   3.

   Over 7 days GREEN (#3)


Yellow = intermittent failures for different projects but no lasting or
current regressions

** intermittent would be a healthy project as we expect a number of
failures during the week

** I will not report any of the solved failures or regressions.


   1.

   Solved job failuresYELLOW (#1)
   2.

   Solved regressions  YELLOW (#2)


Red = job has been failing

** Active Failures. The colour will change based on the amount of time the
project/s has been broken. Only active regressions would be reported.


   1.

   1-3 days  RED (#1)
   2.

   4-7 days  RED (#2)
   3.

   Over 7 days RED (#3)
___
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/DUNGHY4OYXMIKDTXYB36E7PVXWDW3V4E/


[CQ]: 101299,3 (mom) failed "ovirt-4.2" system tests

2019-06-28 Thread oVirt Jenkins
Change 101299,3 (mom) 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://gerrit.ovirt.org/#/c/101299/3

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


[CQ]: 101016, 2 (ovirt-node-ng-image) failed "ovirt-master" system tests

2019-06-28 Thread oVirt Jenkins
Change 101016,2 (ovirt-node-ng-image) 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/101016/2

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


[JIRA] (OVIRT-2747) Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo

2019-06-28 Thread Evgheni Dereveanchin (oVirt JIRA)

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

Evgheni Dereveanchin commented on OVIRT-2747:
-

Looking at the sync job it seems to error out even though it is marked as 
successful:

[https://jenkins.ovirt.org/job/system-sync_mirrors-mock-copr-fc29-x86_64/113/console|https://jenkins.ovirt.org/job/system-sync_mirrors-mock-copr-fc29-x86_64/113/console]



{code}13:00:16 + reposync_out='Could not get metalink 
https://mirrors.fedoraproject.org/metalink?repo=epel-7=x86_64 error was
13:00:16 14: curl#35 - "TCP connection reset by peer"'
13:00:16 + [[ -n Could not get metalink 
https://mirrors.fedoraproject.org/metalink?repo=epel-7=x86_64 error was
13:00:16 14: curl#35 - "TCP connection reset by peer" ]]{code}


Not sure if this behavior causes any kind of repo corruption.

> Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo
> -
>
> Key: OVIRT-2747
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2747
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Evgheni Dereveanchin
>Assignee: infra
>
> I see this error pop out in logs:
> Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo.
> Looks like a corrupted repo so it should either be fixed or removed from the 
> configuration.
> Sample job:
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/7126/consoleFull



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100105)
___
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/2L7X4JJ7N6PTKLWTSMK6RGAYXPKJ3QAS/


[JIRA] (OVIRT-2747) Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo

2019-06-28 Thread Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-2747:
---

 Summary: Failed to synchronize cache for repo 'mock-copr-fc29', 
ignoring this repo
 Key: OVIRT-2747
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2747
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Evgheni Dereveanchin
Assignee: infra


I see this error pop out in logs:

Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo.

Looks like a corrupted repo so it should either be fixed or removed from the 
configuration.

Sample job:
https://jenkins.ovirt.org/job/vdsm_standard-check-patch/7126/consoleFull



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100105)
___
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/GIB2ZBGIUA6V3NRMIUPZA4JG45MB5RV4/