- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 381 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Jan '18

17 Jan '18

------=_Part_115_1311509428.1516085666457 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build Number: 381 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #381 [Yuval Turgeman] automation: view install log in console output ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_115_1311509428.1516085666457--

1 1

[JIRA] (OVIRT-1848) Update Ubuntu images in Glance
by Barak Korren (oVirt JIRA) 17 Jan '18

17 Jan '18

This is a multi-part message in MIME format... ------------=_1516172567-27484-662 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1848?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1848: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Update Ubuntu images in Glance > ------------------------------ > > Key: OVIRT-1848 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1848 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt image repository (Glance) > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Users have reported that the Ubuntu images we host are currently out of date -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076) ------------=_1516172567-27484-662 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1848?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1848:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>Update Ubuntu images in Glance</h3> <pre> Key: OVIRT-1848 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1848 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt image repository (Glance) Reporter: Barak Korren Assignee: Evgheni Dereveanchin</pre> <p>Users have reported that the Ubuntu images we host are currently out of date</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1516172567-27484-662--

1 0

[JIRA] (OVIRT-1848) Update Ubuntu images in Glance
by Barak Korren (oVirt JIRA) 17 Jan '18

17 Jan '18

This is a multi-part message in MIME format... ------------=_1516172551-16017-677 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1848: ----------------------------------- Summary: Update Ubuntu images in Glance Key: OVIRT-1848 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1848 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt image repository (Glance) Reporter: Barak Korren Assignee: infra Users have reported that the Ubuntu images we host are currently out of date -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076) ------------=_1516172551-16017-677 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1848:</h3> <pre> Summary: Update Ubuntu images in Glance Key: OVIRT-1848 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1848 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt image repository (Glance) Reporter: Barak Korren Assignee: infra</pre> <p>Users have reported that the Ubuntu images we host are currently out of date</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1516172551-16017-677--

1 0

[JIRA] (OVIRT-1848) Update Ubuntu images in Glance
by Barak Korren (oVirt JIRA) 17 Jan '18

17 Jan '18

This is a multi-part message in MIME format... ------------=_1516172550-20496-690 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1848?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1848: -------------------------------- Epic Link: OVIRT-403 > Update Ubuntu images in Glance > ------------------------------ > > Key: OVIRT-1848 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1848 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt image repository (Glance) > Reporter: Barak Korren > Assignee: infra > > Users have reported that the Ubuntu images we host are currently out of date -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076) ------------=_1516172550-20496-690 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1848?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1848:</h3> <pre>Epic Link: OVIRT-403</pre> <blockquote><h3>Update Ubuntu images in Glance</h3> <pre> Key: OVIRT-1848 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1848 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt image repository (Glance) Reporter: Barak Korren Assignee: infra</pre> <p>Users have reported that the Ubuntu images we host are currently out of date</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1516172550-20496-690--

1 0

[CQ]: 86256, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Jan '18

17 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86256,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 86114,4 (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 86114,4 (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/86256/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86114/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4903/

1 0

[CQ]: 86088, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Jan '18

16 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86088,5 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 86114,4 (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 86114,4 (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/86088/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86114/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4896/

1 0

[JIRA] (OVIRT-1844) jenkins_master_deploy-configs_merged failing do to missing libraries
by Evgheni Dereveanchin (oVirt JIRA) 16 Jan '18

16 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1844: --------------------------------------------- [~bkorren(a)redhat.com] the slave in this case is the master itself so it never runs STDCI jobs. > jenkins_master_deploy-configs_merged failing do to missing libraries > -------------------------------------------------------------------- > > Key: OVIRT-1844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > Since patches related to OVIRT-1746, mainly https://gerrit.ovirt.org/85158/, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: > http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso… > File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> > from xdg.BaseDirectory import xdg_cache_home > ImportError: No module named xdg.BaseDirectory -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)

1 0

[CQ]: 83355, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Jan '18

16 Jan '18

A system test invoked by the "ovirt-master" change queue including change 83355,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 86114,4 (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 86114,4 (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/83355/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86114/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4888/

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.1 - Build # 156 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 Jan '18

16 Jan '18

------=_Part_111_2018021744.1516073678881 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1= /=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1/1= 56/ Build Number: 156 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #156 [Gal Ben Haim] 4.2: Adding 4.2 pre repo ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_secondary_storage_domains Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during = communication with the Host.]". HTTP response code is 400. -------------------- >> begin captured logging << -------------------- lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_v= ia_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 637= , in add_templates_storage_domain add_generic_nfs_storage_domain(prefix, SD_TEMPLATES_NAME, SD_TEMPLATES_= HOST_NAME, SD_TEMPLATES_PATH, sd_format=3D'v1', sd_type=3D'export') File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 496= , in add_generic_nfs_storage_domain add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mo= unt_path, sd_format, sd_type, nfs_version) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 552= , in add_generic_nfs_storage_domain_4 _add_storage_domain_4(api, p) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 447= , in _add_storage_domain_4 sd =3D sds_service.add(p) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 217= 85, in add return self._internal_add(storage_domain, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232,= in _internal_add return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, = in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 229,= in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132,= in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118,= in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error = during communication with the Host.]". HTTP response code is 400. --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 577= , in add_secondary_storage_domains vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_v= ia_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 637= , in add_templates_storage_domain add_generic_nfs_storage_domain(prefix, SD_TEMPLATES_NAME, SD_TEMPLATES_= HOST_NAME, SD_TEMPLATES_PATH, sd_format=3D'v1', sd_type=3D'export') File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 496= , in add_generic_nfs_storage_domain add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mo= unt_path, sd_format, sd_type, nfs_version) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 552= , in add_generic_nfs_storage_domain_4 _add_storage_domain_4(api, p) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 447= , in _add_storage_domain_4 sd =3D sds_service.add(p) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 217= 85, in add return self._internal_add(storage_domain, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232,= in _internal_add return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, = in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 229,= in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132,= in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118,= in _raise_error raise error 'Fault reason is "Operation Failed". Fault detail is "[Network error during= communication with the Host.]". HTTP response code is 400.\n--------------= ------ >> begin captured logging << --------------------\nlago.utils: ERROR= : Error while running thread\nTraceback (most recent call last):\n File "/= usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue\= n queue.put({\'return\': func()})\n File "/home/jenkins/workspace/ovirt= -system-tests_he-basic-suite-4.1/ovirt-system-tests/he-basic-suite-4.1/test= -scenarios/002_bootstrap.py", line 637, in add_templates_storage_domain\n = add_generic_nfs_storage_domain(prefix, SD_TEMPLATES_NAME, SD_TEMPLATES_HO= ST_NAME, SD_TEMPLATES_PATH, sd_format=3D\'v1\', sd_type=3D\'export\')\n Fi= le "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt-sys= tem-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 496, in= add_generic_nfs_storage_domain\n add_generic_nfs_storage_domain_4(prefi= x, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)= \n File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovi= rt-system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 5= 52, in add_generic_nfs_storage_domain_4\n _add_storage_domain_4(api, p)\= n File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovir= t-system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 44= 7, in _add_storage_domain_4\n sd =3D sds_service.add(p)\n File "/usr/li= b64/python2.7/site-packages/ovirtsdk4/services.py", line 21785, in add\n = return self._internal_add(storage_domain, headers, query, wait)\n File "/= usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232, in _inte= rnal_add\n return future.wait() if wait else future\n File "/usr/lib64/= python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return= self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4= /service.py", line 229, in callback\n self._check_fault(response)\n Fil= e "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _= check_fault\n self._raise_error(response, body)\n File "/usr/lib64/pyth= on2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n r= aise error\nError: Fault reason is "Operation Failed". Fault detail is "[Ne= twork error during communication with the Host.]". HTTP response code is 40= 0.\n--------------------- >> end captured logging << ---------------------' ------=_Part_111_2018021744.1516073678881--

1 1

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1107
by jenkins＠jenkins.phx.ovirt.org 16 Jan '18

16 Jan '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1107/displ…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > 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 711ff7a5b5a5166557225578ac6f1a67f83ce389 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 711ff7a5b5a5166557225578ac6f1a67f83ce389 Commit message: "ovirt-engine-dashboard: add support for 1.2/4.2, drop 1.0/4.0" > git rev-list 711ff7a5b5a5166557225578ac6f1a67f83ce389 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins7337906336857170434.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 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 <module> 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 local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

Subject: [ OST Failure Report ] [ oVirt Master ] [ 15 Jan 2018 ] [ 004_basic_sanity.vm_run ]
by Dafna Ron 16 Jan '18

16 Jan '18

Hi, We had a failure in OST on the upgrade suite. *Link and headline of suspected patches: Reported as the cause: https://gerrit.ovirt.org/#/c/86115/4 - <https://gerrit.ovirt.org/#/c/86115/4>vm: support error_policy='report' for CDROMs*Reported* as the root cause: *https://gerrit.ovirt.org/#/c/86114/4 net tests: Fix vlan creation name length in nettestlib <https://gerrit.ovirt.org/#/c/86114/4> * <https://gerrit.ovirt.org/#/c/86114/4>* *Link to Job:* *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4854/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4854/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4854/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4854/artifact/>(Relevant) error snippet from the log: <error>* *vdsm: *type=file, path= threshold=unset at 0x7f57d8027d40>> watermarkLimit:536870912 (vm:2134) 2018-01-15 13:12:06,126-0500 ERROR (vm/75adb67b) [virt.vm] (vmId='75adb67b-4390-45f7-a677-8d4515cf4a2b') The vm start process failed (vm:917) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 846, in _startUnderlyingVm self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2735, in _run domxml = hooks.before_vm_start(self._buildDomainXML(), File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2191, in _buildDomainXML return self._make_domain_xml() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2236, in _make_domain_xml devices_xml = self._process_devices() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2116, in _process_devices dev_xml = dev.getXML() File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/storage.py", line 595, in getXML diskelem.appendChild(_getDriverXML(self)) File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/storage.py", line 957, in _getDriverXML if (drive['propagateErrors'] == 'on' or File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/storage.py", line 292, in __getitem__ raise KeyError(key) KeyError: 'propagateErrors' 2018-01-15 13:12:06,129-0500 INFO (vm/75adb67b) [virt.vm] (vmId='75adb67b-4390-45f7-a677-8d4515cf4a2b') Changed state to Down: 'propagateErrors' (code=1) (vm:1636) engine: *2018-01-15 13:12:07,203-05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-15) [] Rerun VM '75adb67b-4390-45f7-a677-8d4515cf4a2b'. Called from VDS 'lago-upgrade-from-release-suite-master-host0'2018-01-15 13:12:07,205-05 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (ForkJoinPool-1-worker-15) [] VMs initialization finished for Host: 'lago-upgrade-from-release-suite-master-host0:c98b0719-383b-4656-a28d-03005e2fb862'2018-01-15 13:12:07,256-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-19) [] EVENT_ID: USER_INITIATED_RUN_VM_FAILED(151), Failed to run VM vm0 on Host lago-upgrade-from-release-suite-master-host0.2018-01-15 13:12:07,274-05 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand] (EE-ManagedThreadFactory-engine-Thread-19) [] Lock Acquired to object 'EngineLock:{exclusiveLocks='[75adb67b-4390-45f7-a677-8d4515cf4a2b=VM]', sharedLocks=''}'2018-01-15 13:12:07,294-05 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (EE-ManagedThreadFactory-engine-Thread-19) [] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='75adb67b-4390-45f7-a677-8d4515cf4a2b'}), log id: 41c281dc2018-01-15 13:12:07,294-05 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (EE-ManagedThreadFactory-engine-Thread-19) [] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 41c281dc2018-01-15 13:12:07,300-05 WARN [org.ovirt.engine.core.bll.RunVmOnceCommand] (EE-ManagedThreadFactory-engine-Thread-19) [] Validation of action 'RunVmOnce' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS</error>*

2 2

[CQ]: 86269, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 16 Jan '18

16 Jan '18

Change 86269,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/86269/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4880/

1 0

[vdsm][tag][ovirt-4.1] Vdsm tagged: v4.19.45
by Francesco Romani 16 Jan '18

16 Jan '18

Hi infra, we have a new Vdsm tag on branch ovirt-4.1 for oVirt 4.1.9: tag v4.19.45 Tagger: Francesco Romani <fromani(a)redhat.com> Date: Tue Jan 16 10:41:30 2018 +0100 Vdsm 4.19.45 for oVirt 4.1.9 RC 2 Bests, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc27-x86_64 #164
by jenkins＠jenkins.phx.ovirt.org 16 Jan '18

16 Jan '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc27-x86_64…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc27-x86_64…> > 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 711ff7a5b5a5166557225578ac6f1a67f83ce389 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 711ff7a5b5a5166557225578ac6f1a67f83ce389 Commit message: "ovirt-engine-dashboard: add support for 1.2/4.2, drop 1.0/4.0" > git rev-list 711ff7a5b5a5166557225578ac6f1a67f83ce389 # timeout=10 [system-sync_mirrors-fedora-updates-fc27-x86_64] $ /bin/bash -xe /tmp/jenkins4651134624721509794.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: fedora-updates-fc27 Syncing yum repo fedora-updates-fc27 for arch: x86_64 Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> 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 local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-qemu-ev-release-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-qemu-ev-release-el7' Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 406 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 Jan '18

16 Jan '18

------=_Part_95_363609111.1515998112386 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build Number: 406 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #406 [Daniel Belenky] Introduce stdci_dsl options package [Daniel Belenky] Introduce python API for automation module [Greg Sheremeta] ovirt-engine-dashboard: add support for 1.2/4.2, drop 1.0/4.0 [Ryan Barry] Bump version ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_95_363609111.1515998112386--

1 1

[CQ]: 86265, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Jan '18

16 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86265,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 86114,4 (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 86114,4 (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/86265/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86114/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4868/

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1105
by jenkins＠jenkins.phx.ovirt.org 16 Jan '18

16 Jan '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1105/displ…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > 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 711ff7a5b5a5166557225578ac6f1a67f83ce389 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 711ff7a5b5a5166557225578ac6f1a67f83ce389 Commit message: "ovirt-engine-dashboard: add support for 1.2/4.2, drop 1.0/4.0" > git rev-list 711ff7a5b5a5166557225578ac6f1a67f83ce389 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins5323183052655245716.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 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 <module> 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 local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 86021, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 Jan '18

16 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86021,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 86114,4 (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 86114,4 (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/86021/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86114/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4861/

1 0

[CQ]: 86115, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '18

15 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86115,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 86114,4 (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 86114,4 (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/86115/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86114/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4854/

1 0

[CQ]: 86340, 3 (vdsm) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '18

15 Jan '18

A system test invoked by the "ovirt-4.1" change queue including change 86340,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 85609,7 (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 85609,7 (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/86340/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85609/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1509/

1 0

[CQ]: 86339, 2 (vdsm) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '18

15 Jan '18

A system test invoked by the "ovirt-4.1" change queue including change 86339,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 85609,7 (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 85609,7 (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/86339/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85609/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1508/

1 0

[oVirt Jenkins] standard-enqueue - Build #8883 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Jan '18

15 Jan '18

------=_Part_99_1711724257.1516027632167 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/8883/ Build Name: #8883 Build Description: Gerrit: 86366 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/86366 - title: build: post 3.6.12.3 - project: ovirt-engine - branch: ovirt-engine-3.6 - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_99_1711724257.1516027632167--

1 1

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 672 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 Jan '18

15 Jan '18

------=_Part_88_276030671.1515937288454 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build Number: 672 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #672 [Daniel Belenky] Introduce stdci_dsl options package [Daniel Belenky] Introduce python API for automation module [Greg Sheremeta] ovirt-engine-dashboard: add support for 1.2/4.2, drop 1.0/4.0 [Sandro Bonazzola] automation: check and save unsigned rpms ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_88_276030671.1515937288454--

1 1

[JIRA] (OVIRT-1847) add mzamazal and phoracek to vdsm_stable_maintainers
by eyal edri (oVirt JIRA) 15 Jan '18

15 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1847?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1847: -------------------------------- Assignee: eyal edri (was: infra) > add mzamazal and phoracek to vdsm_stable_maintainers > ---------------------------------------------------- > > Key: OVIRT-1847 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1847 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Gerrit/git > Reporter: danken > Assignee: eyal edri > > As approved on the mailing list http://lists.ovirt.org/pipermail/devel/2018-January/032400.html > please add [~mzamazal(a)redhat.com] and [~phoracek(a)redhat.com] as vdsm stable branch maintainers. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 86114,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 15 Jan '18

15 Jan '18

Change 86114,4 (vdsm) 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/86114/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4842/

1 0

[CQ]: 86204, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '18

15 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86204,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 84883,11 (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 84883,11 (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/86204/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/84883/11 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4835/

1 0

[CQ]: 86198, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '18

15 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86198,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 84883,11 (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 84883,11 (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/86198/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/84883/11 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4829/

1 0

[CQ]: 86154, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '18

15 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86154,5 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 85996,6 (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 85996,6 (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/86154/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85996/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4823/

1 0

[CQ]: 85303, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-master" change queue including change 85303,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 84883,11 (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 84883,11 (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/85303/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/84883/11 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4817/

1 0

[JIRA] (OVIRT-1847) add mzamazal and phoracek to vdsm_stable_maintainers
by danken (oVirt JIRA) 14 Jan '18

14 Jan '18

danken created OVIRT-1847: ----------------------------- Summary: add mzamazal and phoracek to vdsm_stable_maintainers Key: OVIRT-1847 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1847 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git Reporter: danken Assignee: infra As approved on the mailing list http://lists.ovirt.org/pipermail/devel/2018-January/032400.html please add [~mzamazal(a)redhat.com] and [~phoracek(a)redhat.com] as vdsm stable branch maintainers. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 84883,11 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '18

14 Jan '18

Change 84883,11 (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/84883/11 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4810/

1 0

[CQ]: 86289,1 (cockpit-ovirt) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Jan '18

14 Jan '18

Change 86289,1 (cockpit-ovirt) 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/86289/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/234/

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1101
by jenkins＠jenkins.phx.ovirt.org 14 Jan '18

14 Jan '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1101/displ…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > 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 e1c292b6e3a20dcb51c31e307273b589db739ca2 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e1c292b6e3a20dcb51c31e307273b589db739ca2 Commit message: "vdsm: Disable Fedora 26 builds on master" > git rev-list e1c292b6e3a20dcb51c31e307273b589db739ca2 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins366348300979211253.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 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 <module> 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 local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 86287, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86287,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86285,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 86285,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/86287/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86285/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/232/

1 0

[JIRA] (OVIRT-1846) New gerrit project - ovirt-node-ng-image
by eyal edri (oVirt JIRA) 14 Jan '18

14 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1846?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1846: -------------------------------- Assignee: Gal Ben Haim (was: infra) > New gerrit project - ovirt-node-ng-image > ---------------------------------------- > > Key: OVIRT-1846 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1846 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yuval Turgeman > Assignee: Gal Ben Haim > > Hi, > We would like to split the squashfs+installer creation from the current > ovirt-node-ng project, leaving it to build its current rpms only (nodectl, > docs, tools etc) according to [1]. > For this we would like to have a new gerrit project `ovirt-node-ng-image`. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1527120 > Thanks, > Yuval. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1846) New gerrit project - ovirt-node-ng-image
by Barak Korren (oVirt JIRA) 14 Jan '18

14 Jan '18

This is a multi-part message in MIME format... ------------=_1515944717-26563-108 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1846?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1846: ------------------------------------- [~yuvalt(a)redhat.com] see my comment on the bug, I'm not convinced creating a new repo is the best way to achieve what you want in this point in time. > New gerrit project - ovirt-node-ng-image > ---------------------------------------- > > Key: OVIRT-1846 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1846 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yuval Turgeman > Assignee: infra > > Hi, > We would like to split the squashfs+installer creation from the current > ovirt-node-ng project, leaving it to build its current rpms only (nodectl, > docs, tools etc) according to [1]. > For this we would like to have a new gerrit project `ovirt-node-ng-image`. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1527120 > Thanks, > Yuval. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515944717-26563-108 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1846?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1846:</h3> <p>[~yuvalt(a)redhat.com] see my comment on the bug, I'm not convinced creating a new repo is the best way to achieve what you want in this point in time.</p> <blockquote><h3>New gerrit project – ovirt-node-ng-image</h3> <pre> Key: OVIRT-1846 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1846 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yuval Turgeman Assignee: infra</pre> <p>Hi, We would like to split the squashfs+installer creation from the current ovirt-node-ng project, leaving it to build its current rpms only (nodectl, docs, tools etc) according to [1]. For this we would like to have a new gerrit project `ovirt-node-ng-image`. [1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1527120">https://bugzilla.redhat.com/show_bug.cgi?id=1527120</a> Thanks, Yuval.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515944717-26563-108--

1 0

[JIRA] (OVIRT-1680) Adapt STDCI pipelines for use in Gerrit projects
by Daniel Belenky (oVirt JIRA) 14 Jan '18

14 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1680?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1680: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Adapt STDCI pipelines for use in Gerrit projects > ------------------------------------------------ > > Key: OVIRT-1680 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1680 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Daniel Belenky > Labels: gerrit, standard-ci > > So far work on OVIRT-1522 focused on GitHub, and it is now feature-complete. > Now its time to make this work also available for Gerrit projects. > OVIRT-1629 is a blocker for this ticket because the '{{automation.yaml}}' implementation in the current STDCI pipelines does not yet support everything that the existing JJB YAML does. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1846) New gerrit project - ovirt-node-ng-image
by Yuval Turgeman (oVirt JIRA) 14 Jan '18

14 Jan '18

Yuval Turgeman created OVIRT-1846: ------------------------------------- Summary: New gerrit project - ovirt-node-ng-image Key: OVIRT-1846 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1846 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yuval Turgeman Assignee: infra Hi, We would like to split the squashfs+installer creation from the current ovirt-node-ng project, leaving it to build its current rpms only (nodectl, docs, tools etc) according to [1]. For this we would like to have a new gerrit project `ovirt-node-ng-image`. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1527120 Thanks, Yuval. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 86286, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86286,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86285,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 86285,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/86286/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86285/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/229/

1 0

[oVirt Jenkins] standard-enqueue - Build #8823 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 14 Jan '18

14 Jan '18

------=_Part_90_308963627.1515940478521 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/8823/ Build Name: #8823 Build Description: Gerrit: 79842 - ovirt-vmconsole (4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79842 - title: spec: ensure selinux-policy-targeted is installed - project: ovirt-vmconsole - branch: master - author: Francesco Romani <fromani(a)redhat.com> ------=_Part_90_308963627.1515940478521--

1 0

[CQ]: 86285,1 (cockpit-ovirt) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Jan '18

14 Jan '18

Change 86285,1 (cockpit-ovirt) 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/86285/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/226/

1 0

[CQ]: 86182, 1 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '18

14 Jan '18

Change 86182,1 (ovirt-hosted-engine-ha) 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/86182/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4802/

1 0

[CQ]: 86272, 1 (ovirt-log-collector) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86272,1 (ovirt-log-collector) failed. However, this change seems not to be the root cause for this failure. Change 86247,1 (ovirt-log-collector) 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 86247,1 (ovirt-log-collector) 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/86272/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86247/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/222/

1 0

[CQ]: 86255, 1 (ovirt-log-collector) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86255,1 (ovirt-log-collector) failed. However, this change seems not to be the root cause for this failure. Change 86247,1 (ovirt-log-collector) 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 86247,1 (ovirt-log-collector) 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/86255/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86247/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/218/

1 0

[JIRA] (OVIRT-1844) jenkins_master_deploy-configs_merged failing do to missing libraries
by Barak Korren (oVirt JIRA) 14 Jan '18

14 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1844: ------------------------------------- [~eedri] it IS already in '{{global-setup.sh}}' - ths issue is that deploy-configs is not an STDCI job (see linked ticket for fixing that). [~ederevea] given that it is in '{{global-setup.sh}}' how come we found a slave without it installed? > jenkins_master_deploy-configs_merged failing do to missing libraries > -------------------------------------------------------------------- > > Key: OVIRT-1844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > Since patches related to OVIRT-1746, mainly https://gerrit.ovirt.org/85158/, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: > http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso… > File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> > from xdg.BaseDirectory import xdg_cache_home > ImportError: No module named xdg.BaseDirectory -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 86252, 1 (ovirt-log-collector) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86252,1 (ovirt-log-collector) failed. However, this change seems not to be the root cause for this failure. Change 86247,1 (ovirt-log-collector) 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 86247,1 (ovirt-log-collector) 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/86252/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86247/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/214/

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 150 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jan '18

14 Jan '18

------=_Part_70_1033959891.1515812549553 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/150/ Build Number: 150 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #150 [Gal Ben Haim] master: Add host's image to the internal_repo [Nir Soffer] vdsm: Disable Fedora 26 builds on master ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_70_1033959891.1515812549553--

1 2

[JIRA] (OVIRT-1844) jenkins_master_deploy-configs_merged failing do to missing libraries
by eyal edri (oVirt JIRA) 14 Jan '18

14 Jan '18

This is a multi-part message in MIME format... ------------=_1515916522-21230-200 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1844: ---------------------------------- Should we also add it to the global_setup script to be installed? > jenkins_master_deploy-configs_merged failing do to missing libraries > -------------------------------------------------------------------- > > Key: OVIRT-1844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > Since patches related to OVIRT-1746, mainly https://gerrit.ovirt.org/85158/, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: > http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso… > File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> > from xdg.BaseDirectory import xdg_cache_home > ImportError: No module named xdg.BaseDirectory -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515916522-21230-200 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1844:</h3> <p>Should we also add it to the global_setup script to be installed?</p> <blockquote><h3>jenkins_master_deploy-configs_merged failing do to missing libraries</h3> <pre> Key: OVIRT-1844 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: High</pre> <p>Since patches related to OVIRT-1746, mainly <a href="https://gerrit.ovirt.org/85158/">https://gerrit.ovirt.org/85158/</a>, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: <a href="http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso…">http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso…</a></p> <pre> File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> from xdg.BaseDirectory import xdg_cache_home ImportError: No module named xdg.BaseDirectory</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515916522-21230-200--

1 0

[CQ]: 86087, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86087,7 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 85996,6 (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 85996,6 (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/86087/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85996/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4797/

1 0

[JIRA] (OVIRT-1845) Removing build jobs makes change-queue fail with an exception
by Barak Korren (oVirt JIRA) 14 Jan '18

14 Jan '18

This is a multi-part message in MIME format... ------------=_1515912445-32493-213 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1845?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1845: -------------------------------- Assignee: Barak Korren (was: infra) Status: In Progress (was: To Do) > Removing build jobs makes change-queue fail with an exception > -------------------------------------------------------------- > > Key: OVIRT-1845 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1845 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > When changes are added to the change queue, it records the build jobs that build artifacts for changed code. > If the build jobs are removed between the time the change is added to the queue and the time a tested jobs including that change is started, the code checking for completion of the build jobs would fail with an exception looking like the following: > {code} > java.lang.NullPointerException: Cannot invoke method getBuild() on null object > at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) > at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:35) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) > at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:52) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) > at Script1$_all_builds_done_closure4.doCall(Script1.groovy:265) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) > at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) > at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) > at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) > {code} > '{{Script1}}' in this stack trace refers to our '{{change-queue-tester.groovy}}' script. Relevant code section is the following: > {code} > @NonCPS > def all_builds_done(builds) { > return !builds.any { > if(Jenkins.instance.getItem(it.job_name).getBuild(it.build_id).isBuilding()) { > print("${it.job_name} (${it.build_id}) still building") > return true > } > return false > } > } > {code} > The issue it with not checking for '{{null}}' return from the '{{Jenkins.instance.getItem(it.job_name)}}' funcntion call. > We should probably check for '{{null}}' there and just ignore it. Similar check will probably be needed in other places in the code like for example when composing the '{{extra-sources}}' file from the build job URLs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515912445-32493-213 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1845?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1845:</h3> <pre>Assignee: Barak Korren (was: infra) Status: In Progress (was: To Do)</pre> <blockquote><h3>Removing build jobs makes change-queue fail with an exception</h3> <pre> Key: OVIRT-1845 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1845 Project: oVirt - virtualization made easy Issue Type: Bug Components: Change Queue Reporter: Barak Korren Assignee: Barak Korren Priority: Highest</pre> <p>When changes are added to the change queue, it records the build jobs that build artifacts for changed code. If the build jobs are removed between the time the change is added to the queue and the time a tested jobs including that change is started, the code checking for completion of the build jobs would fail with an exception looking like the following: {code} java.lang.NullPointerException: Cannot invoke method getBuild() on null object</p> <pre>at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:35) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:52) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at Script1$_all_builds_done_closure4.doCall(Script1.groovy:265) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)</pre> <p>{code} ‘{{Script1}}’ in this stack trace refers to our ‘{{change-queue-tester.groovy}}’ script. Relevant code section is the following: {code} @NonCPS def all_builds_done(builds) {</p> <pre> return !builds.any { if(Jenkins.instance.getItem(it.job_name).getBuild(it.build_id).isBuilding()) { print("${it.job_name} (${it.build_id}) still building") return true } return false }</pre> <p>} {code} The issue it with not checking for ‘{{null}}’ return from the ‘{{Jenkins.instance.getItem(it.job_name)}}’ funcntion call. We should probably check for ‘{{null}}’ there and just ignore it. Similar check will probably be needed in other places in the code like for example when composing the ‘{{extra-sources}}’ file from the build job URLs.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515912445-32493-213--

1 0