[oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 15 - Failure!

2017-09-14 Thread jenkins 
Project: 
http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64/15/
Build Number: 15
Build Status:  Failure
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #15
[Sandro Bonazzola] ovirt-image-uploader: add master builders

[Daniel Belenky] Add meaningful prefix to new/old xml dirs

[Sandro Bonazzola] ovirt-optimizer: drop from master / 4.2

[Ryan Barry] Increase the release for 4.2 development




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : system-sync_mirrors-glusterfs-3.10-el7-x86_64 #257

2017-09-14 Thread jenkins 
See 


___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : system-sync_mirrors-centos-opstools-testing-el7-x86_64 #724

2017-09-14 Thread jenkins 
See 


___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.1 - Build # 31 - Still Failing!

2017-09-14 Thread jenkins 
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1/ 
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1/31/
Build Number: 31
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #29
[Eyal Edri] add kvm_common repo to .repos files

[Yedidyah Bar David] Add ovirt-host 3.6

[Sandro Bonazzola] ovirt-live: drop from master

[Sandro Bonazzola] ovirt-engine-sdk-java: add fc25 for master consumption


Changes for Build #30
[Eyal Edri] drop obselete ovirt-4.0 virt repo from reposync

[Sandro Bonazzola] ovirt-image-uploader: add master builders

[Daniel Belenky] Add meaningful prefix to new/old xml dirs

[Sandro Bonazzola] ovirt-optimizer: drop from master / 4.2


Changes for Build #31
[Yaniv Kaul] Fix reposync for master




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 35 - Still Failing!

2017-09-14 Thread jenkins 
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ 
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/35/
Build Number: 35
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #34
[Eyal Edri] drop obselete ovirt-4.0 virt repo from reposync

[Sandro Bonazzola] ovirt-image-uploader: add master builders

[Daniel Belenky] Add meaningful prefix to new/old xml dirs

[Sandro Bonazzola] ovirt-optimizer: drop from master / 4.2


Changes for Build #35
[Yaniv Kaul] Fix reposync for master




-
Failed Tests:
-
1 tests failed.
FAILED:  002_bootstrap.py.junit.xml.[empty]

Error Message:


Stack Trace:
Test report file 
/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-master/exported-artifacts/002_bootstrap.py.junit.xml
 was length 0___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 29 - Fixed!

2017-09-14 Thread jenkins 
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/ 
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/29/
Build Number: 29
Build Status:  Fixed
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #28
[Eyal Edri] add kvm_common repo to .repos files

[Yedidyah Bar David] Add ovirt-host 3.6

[Sandro Bonazzola] ovirt-live: drop from master

[Sandro Bonazzola] ovirt-engine-sdk-java: add fc25 for master consumption


Changes for Build #29
[Yaniv Kaul] Fix reposync for master

[Sandro Bonazzola] ovirt-image-uploader: add master builders

[Daniel Belenky] Add meaningful prefix to new/old xml dirs

[Sandro Bonazzola] ovirt-optimizer: drop from master / 4.2




-
Failed Tests:
-
All tests passed___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64 - Build # 12 - Failure!

2017-09-14 Thread jenkins 
Project: 
http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64/12/
Build Number: 12
Build Status:  Failure
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #12
[Sandro Bonazzola] ovirt-image-uploader: add master builders

[Daniel Belenky] Add meaningful prefix to new/old xml dirs

[Sandro Bonazzola] ovirt-optimizer: drop from master / 4.2

[Yuval Turgeman] Build to meet NIST partitioning requirements




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

2017-09-14 Thread jenkins 
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/30/
Build Number: 30
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #15
[Ondra Machacek] Download latest module_utils ovirt.py file

[Barak Korren] Make ovirt-ansible jobs not deploy to tested


Changes for Build #16
[Ondra Machacek] Download latest module_utils ovirt.py file


Changes for Build #17
[Ondra Machacek] Download latest module_utils ovirt.py file


Changes for Build #18
[Ondra Machacek] Download latest module_utils ovirt.py file

[Daniel Belenky] Run infra-docs_check-patch and check-merged on el7

[Daniel Belenky] try to build container if related files were changed

[Gil Shinar] Suppress git ls-remote output to stderr

[Yuval Turgeman] Add 4.2 jobs for imgbased, node-ng and appliance

[Daniel Belenky] Fix bugs in mock_runner secrets binding

[Daniel Belenky] Prevent post merge Jobs from voting in Gerrit

[Gil Shinar] suppress git fetch output in upstream source collector

[Daniel Belenky] Add env inject to ost template

[Daniel Belenky] Move gerrit-trigger-ci-label inject to be first


Changes for Build #19
[Barak Korren] Ensure glusterfs-rdma package is synced by OST

[Sandro Bonazzola] ovirt-release: add 4.2 branch


Changes for Build #20
[Simone Tiraboschi] el7: add scl-rh repo on x86_64


Changes for Build #21
[Your Name] Change migration network IP address range.

[Daniel Belenky] Fix race condition in docker cleanup

[Barak Korren] Remove old ovirt-ansible jobs


Changes for Build #22
[Dominik Holler] Ping vm0

[Barak Korren] Added pipeline-std-ci jobs for GitHub PRs

[Barak Korren] Add support for building on demand from GitHub PRs

[Sandro Bonazzola] cockpit-ovirt: add 4.2 branch


Changes for Build #23
[Dominik Holler] Ping vm0

[Barak Korren] Keep CQ builds for 14 days


Changes for Build #24
[Your Name] 004_basic_sanity: add vm network vnic to vm


Changes for Build #25
[Dominik Holler] Parallelize booting of VMs


Changes for Build #26
[Yaniv Kaul] Add APIv4 based test to add an iSCSI based storage domain


Changes for Build #27
[Gal Ben Haim] Remove template files from suites that use Jinja2

[Daniel Belenky] Remove find bugs jobs


Changes for Build #28
[Gal Ben Haim] Remove template files from suites that use Jinja2


Changes for Build #29
[Eyal Edri] add kvm_common repo to .repos files

[Yedidyah Bar David] Add ovirt-host 3.6

[Sandro Bonazzola] ovirt-live: drop from master

[Sandro Bonazzola] ovirt-engine-sdk-java: add fc25 for master consumption


Changes for Build #30
[Yaniv Kaul] Fix reposync for master

[Sandro Bonazzola] ovirt-image-uploader: add master builders

[Daniel Belenky] Add meaningful prefix to new/old xml dirs

[Sandro Bonazzola] ovirt-optimizer: drop from master / 4.2




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

oVirt infra daily report - unstable production jobs - 444

2017-09-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/444//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins
 
 
 
 RHEVM CI Jenkins Daily Report - 14/09/2017
 
00 Unstable Critical
 
   
   ovirt-master_change-queue-tester
   
   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.1
   
   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-suite-4.1
   
   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-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.

   
   
   
   system-sync_mirrors-centos-opstools-testing-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.

   
   
   
   system-sync_mirrors-glusterfs-3.10-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.

   
   ___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] standard-enqueue - Build #4821 - FAILURE!

2017-09-14 Thread jenkins 
Build: http://jenkins.ovirt.org/job/standard-enqueue/4821/
Build Name: #4821
Build Description: Gerrit: 81776 - ovirt-log-collector (master)
Build Status: FAILURE
Gerrit change: https://gerrit.ovirt.org/81776
- title: inventory: add validations to paths in produceReport
- project: ovirt-log-collector
- branch: master
- author: Douglas Schilling Landgraf ___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: system-sync_mirrors-centos-opstools-testing-el7-x86_64 #723

2017-09-14 Thread jenkins 
See 


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

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
 > git --version # timeout=10
 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git 
 > +refs/changes/13/75913/5:patch --prune
 > git rev-parse origin/patch^{commit} # timeout=10
 > git rev-parse patch^{commit} # timeout=10
Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch)
Commit message: "Exclude big packages from mirrors"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f
 > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10
[system-sync_mirrors-centos-opstools-testing-el7-x86_64] $ /bin/bash -xe 
/tmp/jenkins3447363888531231110.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-opstools-testing-el7 
x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
  File "/usr/bin/reposync", line 343, in 
main()
  File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in 
doRepoSetup
return self._getRepos(thisrepo, True)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in 
_getRepos
self._repos.doSetup(thisrepo)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in 
retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in 
_commonLoadRepoXML
if self._latestRepoXML(local):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in 
_latestRepoXML
repomd = self.metalink_data.repomd
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in 
metalink_data = property(fget=lambda self: self._getMetalink(),
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 912, in 
_getMetalink
self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename)
  File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__
raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename
yum.metalink.MetaLinkRepoErrorParseFail: File 
/home/jenkins/mirrors_cache/fedora-updates-fc26/metalink.xml is not XML
Build step 'Execute shell' marked build as failure
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: system-sync_mirrors-glusterfs-3.10-el7-x86_64 #256

2017-09-14 Thread jenkins 
See 


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

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
 > git --version # timeout=10
 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git 
 > +refs/heads/*:refs/remotes/origin/* --prune
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 437ddb52411fa9a9de95b54f816f37c521c8b043 (origin/master)
Commit message: "ovirt-optimizer: drop from master / 4.2"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 437ddb52411fa9a9de95b54f816f37c521c8b043
 > git rev-list 437ddb52411fa9a9de95b54f816f37c521c8b043 # timeout=10
[system-sync_mirrors-glusterfs-3.10-el7-x86_64] $ /bin/bash -xe 
/tmp/jenkins2406805753746648424.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-3.10-el7 x86_64 
jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
  File "/usr/bin/reposync", line 343, in 
main()
  File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in 
doRepoSetup
return self._getRepos(thisrepo, True)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in 
_getRepos
self._repos.doSetup(thisrepo)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in 
retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in 
_commonLoadRepoXML
if self._latestRepoXML(local):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in 
_latestRepoXML
repomd = self.metalink_data.repomd
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in 
metalink_data = property(fget=lambda self: self._getMetalink(),
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 912, in 
_getMetalink
self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename)
  File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__
raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename
yum.metalink.MetaLinkRepoErrorParseFail: File 
/home/jenkins/mirrors_cache/fedora-base-fc24/metalink.xml is not XML
Build step 'Execute shell' marked build as failure
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81646,1 (cockpit-ovirt) failed "ovirt-master" system tests

2017-09-14 Thread oVirt Jenkins 
Change 81646,1 (cockpit-ovirt) 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/81646/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2659/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81747, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81747,2 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80388,45 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80388,45 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81747/2

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80388/45

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2651/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 79831, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
79831,5 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80388,45 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80388,45 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/79831/5

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80388/45

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2647/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

2017-09-14 Thread oVirt Jenkins 
Change 81745,1 (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 further details about the change see:
https://gerrit.ovirt.org/#/c/81745/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2643/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81719, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81719,3 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 80993,19 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80993,19 (ovirt-engine) is
fixed and this change is updated to refer to or rebased on the fixed version,
or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81719/3

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80993/19

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2639/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81648, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81648,5 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80388,45 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80388,45 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81648/5

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80388/45

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2631/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81604, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81604,4 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 80993,19 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80993,19 (ovirt-engine) is
fixed and this change is updated to refer to or rebased on the fixed version,
or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81604/4

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80993/19

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2626/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81085, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81085,3 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80388,45 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80388,45 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81085/3

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80388/45

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2621/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81630, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81630,5 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80388,45 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80388,45 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81630/5

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80388/45

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2616/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81718, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81718,2 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 80993,19 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80993,19 (ovirt-engine) is
fixed and this change is updated to refer to or rebased on the fixed version,
or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81718/2

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80993/19

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2611/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 80548, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
80548,12 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 80993,19 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80993,19 (ovirt-engine) is
fixed and this change is updated to refer to or rebased on the fixed version,
or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/80548/12

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80993/19

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2606/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81726, 1 (ovirt-log-collector) failed "ovirt-master" system tests

2017-09-14 Thread oVirt Jenkins 
Change 81726,1 (ovirt-log-collector) 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/81726/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2601/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 80453, 20 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
80453,20 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80388,45 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80388,45 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/80453/20

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80388/45

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2596/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 79868, 18 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
79868,18 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80388,45 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80388,45 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/79868/18

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80388/45

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2591/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 79867, 11 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
79867,11 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80388,45 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80388,45 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/79867/11

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80388/45

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2586/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 79866, 10 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
79866,10 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80388,45 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80388,45 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/79866/10

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80388/45

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2581/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81658, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81658,8 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 80993,19 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80993,19 (ovirt-engine) is
fixed and this change is updated to refer to or rebased on the fixed version,
or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81658/8

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80993/19

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2576/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 278 - Failure!

2017-09-14 Thread jenkins 
Project: 
http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/278/
Build Number: 278
Build Status:  Failure
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #278
[Sandro Bonazzola] ovirt-engine-sdk-java: add fc25 for master consumption

[Sandro Bonazzola] ovirt-image-uploader: add master builders

[Daniel Belenky] Add meaningful prefix to new/old xml dirs

[Sandro Bonazzola] ovirt-optimizer: drop from master / 4.2

[Yuval Turgeman] build: use mirrorlist for dependent repos




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81711,1 (ovirt-engine-api-model) failed. However, this change seems not to be
the root cause for this failure. Change 81677,1 (ovirt-engine-api-model) that
this change depends on or is based on, was detected as the cause of the testing
failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 81677,1 (ovirt-engine-api-
model) is fixed and this change is updated to refer to or rebased on the fixed
version, or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81711/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/81677/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2566/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread Barak Korren (oVirt JIRA) 

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

Barak Korren updated OVIRT-1649:

Component/s: (was: oVirt CI)
  Epic Link:   (was: OVIRT-400)

> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: danken
>Assignee: infra
>Priority: Low
>  Labels: change-queue
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread Barak Korren (oVirt JIRA) 

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

Barak Korren reassigned OVIRT-1649:
---

Assignee: eyal edri  (was: infra)

> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: danken
>Assignee: eyal edri
>Priority: Low
>  Labels: infra-owner
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread Barak Korren (oVirt JIRA) 

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

Barak Korren commented on OVIRT-1649:
-

{quote}
in "component" I meant ovirt-project. (engine/vdsm/node/...)
{quote}

This already shows up. Both in the subject line and in the message body.

> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: danken
>Assignee: infra
>Priority: Low
>  Labels: change-queue
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81710,1 (ovirt-engine-api-model) failed. However, this change seems not to be
the root cause for this failure. Change 81677,1 (ovirt-engine-api-model) that
this change depends on or is based on, was detected as the cause of the testing
failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 81677,1 (ovirt-engine-api-
model) is fixed and this change is updated to refer to or rebased on the fixed
version, or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81710/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/81677/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2561/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread danken (oVirt JIRA) 

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

danken commented on OVIRT-1649:
---

in "component" I meant ovirt-project. (engine/vdsm/node/...)

> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: danken
>Assignee: infra
>Priority: Low
>  Labels: change-queue
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread Barak Korren (oVirt JIRA) 

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

Barak Korren commented on OVIRT-1649:
-

{quote}
Yes - I've asked to have the patch summary line, and its component.
{quote}

I'm probably not going to implement this, it will become redundant once CQ 
messages are posted to Gerrit and requires some extensive code changes to keep 
this information so it is available in time for reporting.

BTW not sure what you mean by "component".

> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: danken
>Assignee: infra
>Priority: Low
>  Labels: change-queue
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread Barak Korren (oVirt JIRA) 

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

Barak Korren updated OVIRT-1649:

Labels: change-queue  (was: )

> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: danken
>Assignee: infra
>Priority: Low
>  Labels: change-queue
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread Barak Korren (oVirt JIRA) 

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

Barak Korren updated OVIRT-1649:

Component/s: oVirt CI
  Epic Link: OVIRT-400
 Issue Type: Improvement  (was: By-EMAIL)
   Priority: Low  (was: Medium)

> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: danken
>Assignee: infra
>Priority: Low
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread Barak Korren (oVirt JIRA) 

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

Barak Korren updated OVIRT-1649:

Epic Link: OVIRT-400

> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>  Components: oVirt CI
>Reporter: danken
>Assignee: infra
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.1 - Build # 30 - Still Failing!

2017-09-14 Thread jenkins 
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1/ 
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1/30/
Build Number: 30
Build Status:  Still Failing
Triggered By: Started by user Eyal Edri

-
Changes Since Last Success:
-
Changes for Build #29
[Eyal Edri] add kvm_common repo to .repos files

[Yedidyah Bar David] Add ovirt-host 3.6

[Sandro Bonazzola] ovirt-live: drop from master

[Sandro Bonazzola] ovirt-engine-sdk-java: add fc25 for master consumption


Changes for Build #30
[Eyal Edri] drop obselete ovirt-4.0 virt repo from reposync

[Sandro Bonazzola] ovirt-image-uploader: add master builders

[Daniel Belenky] Add meaningful prefix to new/old xml dirs

[Sandro Bonazzola] ovirt-optimizer: drop from master / 4.2




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1650) upgrade CentOS slaves to 7.4

2017-09-14 Thread Evgheni Dereveanchin (oVirt JIRA) 
Evgheni Dereveanchin created OVIRT-1650:
---

 Summary: upgrade CentOS slaves to 7.4
 Key: OVIRT-1650
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1650
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: Evgheni Dereveanchin
Assignee: infra
Priority: High


CentOS 7.4 is out and internal mirrors are in sync. We should start upgrading 
to this version to ensure CI works properly with new VDSM patches expecting 
updated versions of libvirt.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1650) upgrade CentOS slaves to 7.4

2017-09-14 Thread Evgheni Dereveanchin (oVirt JIRA) 

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

Evgheni Dereveanchin reassigned OVIRT-1650:
---

Assignee: Evgheni Dereveanchin  (was: infra)

> upgrade CentOS slaves to 7.4
> 
>
> Key: OVIRT-1650
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1650
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Evgheni Dereveanchin
>Assignee: Evgheni Dereveanchin
>Priority: High
>
> CentOS 7.4 is out and internal mirrors are in sync. We should start upgrading 
> to this version to ensure CI works properly with new VDSM patches expecting 
> updated versions of libvirt.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81709,1 (ovirt-engine-api-model) failed. However, this change seems not to be
the root cause for this failure. Change 81677,1 (ovirt-engine-api-model) that
this change depends on or is based on, was detected as the cause of the testing
failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 81677,1 (ovirt-engine-api-
model) is fixed and this change is updated to refer to or rebased on the fixed
version, or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81709/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/81677/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2556/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : system-sync_mirrors-epel-el7-x86_64 #704

2017-09-14 Thread jenkins 
See 


___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread danken (oVirt JIRA) 

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

danken commented on OVIRT-1649:
---

On Thu, Sep 14, 2017 at 3:17 PM, eyal edri (oVirt JIRA) <


Yes - I've asked to have the patch summary line, and its component.

On Thu, Sep 14, 2017 at 3:11 PM, danken (oVirt JIRA) <


> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread Dan Kenigsberg 
On Thu, Sep 14, 2017 at 3:17 PM, eyal edri (oVirt JIRA) <
j...@ovirt-jira.atlassian.net> wrote:

> [ 
> https://ovirt-jira.atlassian.net/browse/OVIRT-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=34913#comment-34913
>  ]
>
> eyal edri commented on OVIRT-1649:
>
> We are planning to start commenting directly in Gerrit on the relevant
> offending patch soon, we were waiting to see how CQ behaves and sending
> emails to infra only until now. However, it looks like it's quite accurate,
> so we might consider doing it sooner, though we might also want to wait
> until we gate also OS changes before during that.
>
> Nevertheless, I guess we can in the meantime include the patch owner in
> the ‘to’ email when sending a report. Any comments on the current summary?
> is there something missing in it other than the patch owner?
>

Yes - I've asked to have the patch summary line, and its component.

On Thu, Sep 14, 2017 at 3:11 PM, danken (oVirt JIRA) <
>
> —
>
> Eyal edri
>
> ASSOCIATE MANAGER
>
> RHV DevOps
>
> EMEA VIRTUALIZATION R
>
> Red Hat EMEA   TRIED.
> TESTED. TRUSTED.  phone: +972-9-7692018
> <+972%209-769-2018> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
> Include summary, owner and component of suspected patch in OST Failure
> Report
>
>  Key: OVIRT-1649
>  URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
>  Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
> Reporter: danken
> Assignee: infra
>
> $subject would make it easier and quicker to check if the suspicion is
> correct.
>
> — This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread Eyal Edri 
We are planning to start commenting directly in Gerrit on the relevant
offending patch soon, we were waiting to see how CQ behaves and sending
emails to infra only until now.
However, it looks like it's quite accurate, so we might consider doing it
sooner, though we might also want to wait until we gate also OS changes
before during that.

Nevertheless, I guess we can in the meantime include the patch owner in the
'to' email when sending a report.
Any comments on the current summary? is there something missing in it other
than the patch owner?



On Thu, Sep 14, 2017 at 3:11 PM, danken (oVirt JIRA) <
j...@ovirt-jira.atlassian.net> wrote:

> danken created OVIRT-1649:
>
>Summary: Include summary, owner and component of suspected patch in OST 
> Failure Report
>Key: OVIRT-1649
>URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
>Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
>   Reporter: danken
>   Assignee: infra
>
> $subject would make it easier and quicker to check if the suspicion is
> correct.
>
> — This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 

Eyal edri


ASSOCIATE MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81758, 1 (cockpit-ovirt) failed "ovirt-4.1" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-4.1" change queue including change 81758,1
(cockpit-ovirt) failed. However, this change seems not to be the root cause for
this failure. Change 81755,1 (cockpit-ovirt) that this change depends on or is
based on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 81755,1 (cockpit-ovirt) is
fixed and this change is updated to refer to or rebased on the fixed version,
or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81758/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/81755/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1000/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread eyal edri (oVirt JIRA) 

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

eyal edri commented on OVIRT-1649:
--

We are planning to start commenting directly in Gerrit on the relevant
offending patch soon, we were waiting to see how CQ behaves and sending
emails to infra only until now.
However, it looks like it's quite accurate, so we might consider doing it
sooner, though we might also want to wait until we gate also OS changes
before during that.

Nevertheless, I guess we can in the meantime include the patch owner in the
'to' email when sending a report.
Any comments on the current summary? is there something missing in it other
than the patch owner?



On Thu, Sep 14, 2017 at 3:11 PM, danken (oVirt JIRA) <



-- 

Eyal edri


ASSOCIATE MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)


> Include summary, owner and component of suspected patch in OST Failure Report
> -
>
> Key: OVIRT-1649
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> $subject would make it easier and quicker to check if the suspicion is 
> correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81756, 1 (cockpit-ovirt) failed "ovirt-4.1" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-4.1" change queue including change 81756,1
(cockpit-ovirt) failed. However, this change seems not to be the root cause for
this failure. Change 81755,1 (cockpit-ovirt) that this change depends on or is
based on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 81755,1 (cockpit-ovirt) is
fixed and this change is updated to refer to or rebased on the fixed version,
or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81756/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/81755/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/999/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81755,1 (cockpit-ovirt) failed "ovirt-4.1" system tests

2017-09-14 Thread oVirt Jenkins 
Change 81755,1 (cockpit-ovirt) is probably the reason behind recent system test
failures in the "ovirt-4.1" 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/81755/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/998/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1649) Include summary, owner and component of suspected patch in OST Failure Report

2017-09-14 Thread danken (oVirt JIRA) 
danken created OVIRT-1649:
-

 Summary: Include summary, owner and component of suspected patch 
in OST Failure Report
 Key: OVIRT-1649
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1649
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: danken
Assignee: infra


$subject would make it easier and quicker to check if the suspicion is correct.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81396, 9 (ovirt-engine-api-model) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81396,9 (ovirt-engine-api-model) failed. However, this change seems not to be
the root cause for this failure. Change 81677,1 (ovirt-engine-api-model) that
this change depends on or is based on, was detected as the cause of the testing
failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 81677,1 (ovirt-engine-api-
model) is fixed and this change is updated to refer to or rebased on the fixed
version, or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81396/9

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/81677/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2551/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-11 ]

2017-09-14 Thread Eyal Edri 
It might be related to patch merged yesterday to fix where we are taking
qemu-kvm-rhev from, which now comes from kvm commons.

Maybe CQ or the mirrors are not updated?
I'll try to look at it when I'm back next to a computer.


On Sep 14, 2017 12:45, "Dusan Fodor"  wrote:


Link to suspected patch:
https://gerrit.ovirt.org/#/c/80993/19

Link to job:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2498/

Link to all logs:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-
tester/2498/artifact/exported-artifacts/basic-suit-master-
el7/mock_logs/mocker-epel-7-x86_64.el7.init/

Error snippet from log:



DEBUG util.py:533:  Executing command: ['/usr/bin/yum', '--installroot',
'/var/lib/mock/epel-7-x86_64-01b5c106167c9b71f022fe64bb4fa43a-167519/root/',
'--releasever', '7', 'install', '@buildsys-build', 'grubby', 'lago',
'lago-ovirt', 'ovirt-engine-sdk-python', 'python-netaddr',
'python-ovirt-engine-sdk4', '--setopt=tsflags=nocontexts'] with env
{'LANG': 'en_US.UTF-8', 'LD_PRELOAD':
'/var/tmp/tmp.mock.RxN7kZ/$LIB/nosync.so',
'TERM': 'vt100', 'SHELL': '/bin/bash', 'LC_MESSAGES': 'C.UTF-8',
'STD_CI_STAGE': 'basic_suite_master', 'http_proxy': '
http://proxy01.phx.ovirt.org:3128', 'STD_CI_YUMREPOS': '', 'STD_CI_DISTRO':
'el7', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf
"\\033]0;\\007"', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin',
'HOME': '/builddir', 'PS1': ' \\s-\\v\\$ '} and shell False
DEBUG util.py:450:  Failed to set locale, defaulting to C
DEBUG util.py:450:  Error: Package: python-lago-0.41.0-1.el7.centos.noarch
(lago)
DEBUG util.py:450: Requires: qemu-kvm-rhev >= 2.1.2
DEBUG util.py:450:  Error: Package: python-lago-0.41.0-1.el7.centos.noarch
(lago)
DEBUG util.py:450: Requires: qemu-img-rhev >= 2.1.2




___
Devel mailing list
de...@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81564, 7 (ovirt-engine-api-model) failed "ovirt-master" system tests, but isn't the failure root cause

2017-09-14 Thread oVirt Jenkins 
A system test invoked by the "ovirt-master" change queue including change
81564,7 (ovirt-engine-api-model) failed. However, this change seems not to be
the root cause for this failure. Change 81677,1 (ovirt-engine-api-model) that
this change depends on or is based on, was detected as the cause of the testing
failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 81677,1 (ovirt-engine-api-
model) is fixed and this change is updated to refer to or rebased on the fixed
version, or this change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/81564/7

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/81677/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2546/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #712

2017-09-14 Thread jenkins 
See 


___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1648) jenkins_check_yaml.sh should give prefix for it's tempdirs

2017-09-14 Thread Daniel Belenky (oVirt JIRA) 

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

Daniel Belenky reassigned OVIRT-1648:
-

Assignee: Daniel Belenky  (was: infra)

> jenkins_check_yaml.sh should give prefix for it's tempdirs
> --
>
> Key: OVIRT-1648
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1648
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> Since jenkins_check_yaml.sh doesn't give a prefix to the temp dirs it 
> generates, we can't know if a change is referring to new xmls or old ones.
> The solution should be adding prefixes to the tempdir.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1648) jenkins_check_yaml.sh should give prefix for it's tempdirs

2017-09-14 Thread Daniel Belenky (oVirt JIRA) 

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

Daniel Belenky updated OVIRT-1648:
--
Epic Link: OVIRT-400

> jenkins_check_yaml.sh should give prefix for it's tempdirs
> --
>
> Key: OVIRT-1648
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1648
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> Since jenkins_check_yaml.sh doesn't give a prefix to the temp dirs it 
> generates, we can't know if a change is referring to new xmls or old ones.
> The solution should be adding prefixes to the tempdir.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1648) jenkins_check_yaml.sh should give prefix for it's tempdirs

2017-09-14 Thread Daniel Belenky (oVirt JIRA) 
Daniel Belenky created OVIRT-1648:
-

 Summary: jenkins_check_yaml.sh should give prefix for it's tempdirs
 Key: OVIRT-1648
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1648
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: Daniel Belenky
Assignee: infra


Since jenkins_check_yaml.sh doesn't give a prefix to the temp dirs it 
generates, we can't know if a change is referring to new xmls or old ones.
The solution should be adding prefixes to the tempdir.



--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 81677, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests

2017-09-14 Thread oVirt Jenkins 
Change 81677,1 (ovirt-engine-api-model) 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/81677/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2542/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra