February 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-1896) Fwd: repoman error
by Anton Marchukov (oVirt JIRA) 15 Feb '18

15 Feb '18

This is a multi-part message in MIME format... ------------=_1518685718-19759-233 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Anton Marchukov created OVIRT-1896: -------------------------------------- Summary: Fwd: repoman error Key: OVIRT-1896 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1896 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra Opening a ticket. Might be server utilization problem, deficiency in repoman or both. ---------- Forwarded message --------- From: Lev Veyde <lveyde(a)redhat.com> Date: Wed, 14 Feb 2018 at 22:18 Subject: repoman error To: Sandro Bonazzola <sbonazzo(a)redhat.com>, Anton Marchukov < amarchuk(a)redhat.com> Hi guys, got the following error while was trying to add the new packages into the ovirt-4.2 repo: 2018-02-14 17:28:43,792::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm 2018-02-14 17:33:55,267::ERROR::root::Failed to sign Traceback (most recent call last): File "/bin/repoman", line 10, in <module> sys.exit(main()) File "/usr/lib/python2.7/site-packages/repoman/cmd.py", line 460, in main exit_code = do_add(args, config, repo) File "/usr/lib/python2.7/site-packages/repoman/cmd.py", line 360, in do_add repo.save() File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 42, in _func return func(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 201, in save store.save() File "/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py", line 263, in save self._save(**args) File "/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py", line 305, in _save self.sign_rpms() File "/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py", line 524, in sign_rpms pkg.sign(key_path=self.sign_key, passwd=self.sign_passphrase) File "/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/RPM.py", line 272, in sign raise exc pexpect.TIMEOUT: Timeout exceeded in read_nonblocking(). <pexpect.spawn object at 0x566e810> version: 2.3 ($Revision: 399 $) command: /bin/rpmsign args: ['/bin/rpmsign', '--resign', '-D', '_signature gpg', '-D', u'_gpg_name oVirt <infra(a)ovirt.org>', '-D', '__gpg /usr/bin/gpg', '/var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm'] searcher: searcher_re: 0: re.compile("pass phrase: ") 1: re.compile("passphrase: ") 2: re.compile("Passphrase: ") buffer (last 100 chars): before (last 100 chars): after: <class 'pexpect.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 8648 child_fd: 3 closed: False timeout: 600 delimiter: <class 'pexpect.EOF'> logfile: None logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 It looks this due to too small timeout value, as the following seems to work fine: [root@resources02 pub]# /bin/rpmsign --resign -D _signature gpg -D _gpg_name oVirt <infra(a)ovirt.org> -D __gpg /usr/bin/gpg /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm -bash: infra(a)ovirt.org: No such file or directory [root@resources02 pub]# /bin/rpmsign --resign -D '_signature gpg' -D '_gpg_name oVirt <infra(a)ovirt.org>' -D '__gpg /usr/bin/gpg' /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm Enter pass phrase: Pass phrase is good. /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm: However running it several times gave me some weird results - I increased the timeout to 15 minutes in the beginning, and it was still failing dropping out after what seemed to be like only 3.5 to 5 minutes. Quite weird stuff. At the end I increased the timeout to 20 minutes and it seemed to make the trick, not sure that it's not random though (even though it failed many times before). Noted another issue - it looks like the files to sign appear several times in case one runs the repoman again after failed run: 2018-02-14 19:50:45,937::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-nodectl-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 19:50:47,602::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/SRPMS/ovirt-engine-appliance-4.2-20180214.1.el7.centos.src.rpm 2018-02-14 19:57:42,360::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-engine-appliance-4.2-20180214.1.el7.centos.noarch.rpm 2018-02-14 20:05:45,487::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-engine-appliance-4.2-20180214.1.el7.centos.noarch.rpm 2018-02-14 20:15:21,869::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/SRPMS/ovirt-engine-appliance-4.2-20180214.1.el7.centos.src.rpm 2018-02-14 20:27:20,663::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/fc25/noarch/ovirt-engine-appliance-4.2-20180214.1.fc25.noarch.rpm 2018-02-14 20:39:49,348::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm 2018-02-14 20:47:29,586::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-tools-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 20:47:31,821::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-tools-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 20:47:32,581::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-docs-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 20:47:33,736::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-docs-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 20:47:34,806::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/SRPMS/ovirt-node-ng-4.2.0-0.20180214.0.el7.src.rpm 2018-02-14 20:58:44,292::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/SRPMS/ovirt-node-ng-4.2.0-0.20180214.0.el7.src.rpm We probably should use a set instead of list there. Sent a patch to increase the timeout: https://gerrit.ovirt.org/#/c/87694/ (Initially I thought that the issue is due to changed password prompt of the rpmsign, which appeared not to be the case. Despite this, the patch also rearranges the possible password prompts to a per line list to be future proof). Thanks in advance, -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518685718-19759-233 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Anton Marchukov created OVIRT-1896:</h3> <pre> Summary: Fwd: repoman error Key: OVIRT-1896 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1896 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra</pre> <p>Opening a ticket.</p> <p>Might be server utilization problem, deficiency in repoman or both.</p> <p>---------- Forwarded message --------- From: Lev Veyde <lveyde(a)redhat.com> Date: Wed, 14 Feb 2018 at 22:18 Subject: repoman error To: Sandro Bonazzola <sbonazzo(a)redhat.com>, Anton Marchukov < amarchuk(a)redhat.com></p> <p>Hi guys,</p> <p>got the following error while was trying to add the new packages into the ovirt-4.2 repo:</p> <p>2018-02-14 17:28:43,792::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm 2018-02-14 17:33:55,267::ERROR::root::Failed to sign Traceback (most recent call last):</p> <pre>File "/bin/repoman", line 10, in <module> sys.exit(main()) File "/usr/lib/python2.7/site-packages/repoman/cmd.py", line 460, in main exit_code = do_add(args, config, repo) File "/usr/lib/python2.7/site-packages/repoman/cmd.py", line 360, in</pre> <p>do_add</p> <pre> repo.save() File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 42,</pre> <p>in _func</p> <pre> return func(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 201,</pre> <p>in save</p> <pre> store.save() File</pre> <p>“/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py”, line 263, in save</p> <pre> self._save(**args) File</pre> <p>“/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py”, line 305, in _save</p> <pre> self.sign_rpms() File</pre> <p>“/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py”, line 524, in sign_rpms</p> <pre> pkg.sign(key_path=self.sign_key, passwd=self.sign_passphrase) File "/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/RPM.py",</pre> <p>line 272, in sign</p> <pre>raise exc</pre> <p>pexpect.TIMEOUT: Timeout exceeded in read_nonblocking(). <pexpect.spawn object at 0x566e810> version: 2.3 ($Revision: 399 $) command: /bin/rpmsign args: ['/bin/rpmsign', ‘--resign’, ‘-D’, ‘_signature gpg’, ‘-D’, u'_gpg_name oVirt <infra(a)ovirt.org>', ‘-D’, ‘__gpg /usr/bin/gpg’, ‘/var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm’] searcher: searcher_re:</p> <pre>0: re.compile("pass phrase: ") 1: re.compile("passphrase: ") 2: re.compile("Passphrase: ")</pre> <p>buffer (last 100 chars): before (last 100 chars): after: <class 'pexpect.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 8648 child_fd: 3 closed: False timeout: 600 delimiter: <class 'pexpect.EOF'> logfile: None logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1</p> <p>It looks this due to too small timeout value, as the following seems to work fine:</p> <p>[root@resources02 pub]# /bin/rpmsign --resign -D _signature gpg -D _gpg_name oVirt <infra(a)ovirt.org> -D __gpg /usr/bin/gpg /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm -bash: infra(a)ovirt.org: No such file or directory [root@resources02 pub]# /bin/rpmsign --resign -D ‘_signature gpg’ -D ‘_gpg_name oVirt <infra(a)ovirt.org>’ -D ‘__gpg /usr/bin/gpg’ /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm Enter pass phrase: Pass phrase is good. /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm:</p> <p>However running it several times gave me some weird results – I increased the timeout to 15 minutes in the beginning, and it was still failing dropping out after what seemed to be like only 3.5 to 5 minutes. Quite weird stuff.</p> <p>At the end I increased the timeout to 20 minutes and it seemed to make the trick, not sure that it's not random though (even though it failed many times before).</p> <p>Noted another issue – it looks like the files to sign appear several times in case one runs the repoman again after failed run:</p> <p>2018-02-14 19:50:45,937::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-nodectl-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 19:50:47,602::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/SRPMS/ovirt-engine-appliance-4.2-20180214.1.el7.centos.src.rpm 2018-02-14 19:57:42,360::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-engine-appliance-4.2-20180214.1.el7.centos.noarch.rpm 2018-02-14 20:05:45,487::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-engine-appliance-4.2-20180214.1.el7.centos.noarch.rpm 2018-02-14 20:15:21,869::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/SRPMS/ovirt-engine-appliance-4.2-20180214.1.el7.centos.src.rpm 2018-02-14 20:27:20,663::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/fc25/noarch/ovirt-engine-appliance-4.2-20180214.1.fc25.noarch.rpm 2018-02-14 20:39:49,348::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch.rpm 2018-02-14 20:47:29,586::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-tools-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 20:47:31,821::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-tools-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 20:47:32,581::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-docs-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 20:47:33,736::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/noarch/ovirt-node-ng-docs-4.2.0-0.20180214.0.el7.noarch.rpm 2018-02-14 20:47:34,806::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/SRPMS/ovirt-node-ng-4.2.0-0.20180214.0.el7.src.rpm 2018-02-14 20:58:44,292::INFO::root::SIGNING: /var/www/html/pub/ovirt-4.2/rpm/el7/SRPMS/ovirt-node-ng-4.2.0-0.20180214.0.el7.src.rpm</p> <p>We probably should use a set instead of list there.</p> <p>Sent a patch to increase the timeout: <a href="https://gerrit.ovirt.org/#/c/87694/">https://gerrit.ovirt.org/#/c/87694/</a></p> <p>(Initially I thought that the issue is due to changed password prompt of the rpmsign, which appeared not to be the case. Despite this, the patch also rearranges the possible password prompts to a per line list to be future proof).</p> <h3>Thanks in advance,</h3> <p>Lev Veyde</p> <p>Software Engineer, RHCE | RHCVA | MCITP</p> <p>Red Hat Israel</p> <p><<a href="https://www.redhat.com/">https://www.redhat.com</a>></p> <p>lev(a)redhat.com | lveyde(a)redhat.com <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>> — Anton Marchukov Team Lead – Release Management – RHV DevOps – Red Hat</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</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> ------------=_1518685718-19759-233--

1 0

[ OST Failure Report ] [ oVirt 4.2 +Master (ovirt-engine-metrics) ] [ 14-02-2018 ] [ 003_00_metrics_bootstrap.metrics_and_log_collector ]
by Dafna Ron 15 Feb '18

15 Feb '18

Hi, Test 003_00_metrics_bootstrap.metrics_and_log_collector failed on basic suite. The only error I could find was in lago log about failing to configure metrics. *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/87489/7 <https://gerrit.ovirt.org/#/c/87489/7> - ansible: update ovirt-metrics-store-setup roleLink to Job:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/775/ <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/775/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/775/artifact <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/775/artifact>(Relevant) error snippet from the log: <error>* 018-02-13 17:06:38,250::utils.py::_ret_via_queue::60::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_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/003_00_metrics_bootstrap.py", line 54, in configure_metrics ' Exit code is %s' % result.code File "/usr/lib/python2.7/site-packages/nose/tools/trivial.py", line 29, in eq_ raise AssertionError(msg or "%r != %r" % (a, b)) AssertionError: Configuring ovirt machines for metrics failed. Exit code is 2

2 1

[CQ]: 87594, 1 (ovirt-engine-sdk-java) failed "ovirt-master" system tests
by oVirt Jenkins 15 Feb '18

15 Feb '18

Change 87594,1 (ovirt-engine-sdk-java) 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/87594/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5655/

2 1

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

15 Feb '18

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

1 0

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

15 Feb '18

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

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 223 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 Feb '18

15 Feb '18

------=_Part_244_386982124.1518651902701 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build Number: 223 Build Status: Failure Triggered By: Started by user Lev Veyde ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #223 [Sandro Bonazzola] ovirt-engine-api-explorer: re-align [Barak Korren] Use usrc.py in check-patch.sh [Yuval Turgeman] node-setup: added retries to `ssh nodectl check` ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_244_386982124.1518651902701--

1 1

[oVirt Jenkins] ovirt-appliance_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 66 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 Feb '18

15 Feb '18

------=_Part_246_398414682.1518652765278 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifacts-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifacts-… Build Number: 66 Build Status: Failure Triggered By: Started by user Lev Veyde ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #66 [Dan Kenigsberg] add Miguel Martin to whitelist [Sandro Bonazzola] ovirt-engine-phantomjs: dropped [Sandro Bonazzola] ovirt-host: drop s390x fcraw jobs [Sandro Bonazzola] ovirt-engine-api-explorer: re-align [Barak Korren] Use usrc.py in check-patch.sh [Yuval Turgeman] Resolve network issues in kickstart ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_246_398414682.1518652765278--

1 1

[CQ]: 87709, 1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Feb '18

15 Feb '18

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

1 0

[CQ]: 87708, 1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Feb '18

15 Feb '18

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

1 0

[CQ]: 87489, 7 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 15 Feb '18

15 Feb '18

Change 87489,7 (ovirt-engine-metrics) 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/87489/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5665/

1 0

[CQ]: 87706, 4 (ovirt-engine-metrics) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Feb '18

15 Feb '18

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

1 0

[CQ]: 87430, 15 (ovirt-engine-metrics) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Feb '18

14 Feb '18

Change 87430,15 (ovirt-engine-metrics) 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/87430/15 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/802/

1 0

[CQ]: 87702, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '18

14 Feb '18

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

1 0

[CQ]: 87701, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '18

14 Feb '18

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

1 0

[CQ]: 87697, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '18

14 Feb '18

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

1 0

[CQ]: 87700, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '18

14 Feb '18

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

1 0

[CQ]: 83327,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 Feb '18

14 Feb '18

Change 83327,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83327/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5660/

1 0

[CQ]: 87699, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '18

14 Feb '18

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

1 0

[CQ]: 87698, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-4.1" system tests
by oVirt Jenkins 14 Feb '18

14 Feb '18

Change 87698,1 (ovirt-engine-extension-aaa-jdbc) 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/87698/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1630/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1275
by jenkins＠jenkins.phx.ovirt.org 14 Feb '18

14 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-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-centos-updates-el7-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 633e9a8b0cddbe18f68cd295f21a60e6675558be (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 633e9a8b0cddbe18f68cd295f21a60e6675558be Commit message: "ovirt-host: drop s390x fcraw jobs" > git rev-list 633e9a8b0cddbe18f68cd295f21a60e6675558be # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins682311454484382209.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-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 <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 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1452, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 906, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-base-fcraw/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

oVirt infra weekly meeting notes 14.02.2018
by Evgheni Dereveanchin 14 Feb '18

14 Feb '18

Hi everyone, Please find the topics of this week's infra meeting below: PHX DC: - oVirt 4.2.1 is out - infra update due - ManageIQ re-deployed using Ansible: https://staging-manageiq.phx.ovirt.org/ - Monitoring alerts for resources - slowness due to release - oVirt volume provisioning for OpenShift, staging-shift runs on local storage DCs AI: - Link ManageIQ to OpenShift - Add ManageIQ to Puppet - done - Document user management and check if external auth is possible: http://manageiq.org/docs/reference/latest/auth/saml -- Regards, Evgheni Dereveanchin

1 0

Would like to become infra volunteer for ovirt project
by Sahil Joseph 14 Feb '18

14 Feb '18

Hi everyone, This is Sahil I would like to volunteer to manage infra for ovirt project. Can any one mentor me and tell me where to start. Regards Sahil

2 1

[CQ]: 87594, 1 (ovirt-engine-sdk-java) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Feb '18

14 Feb '18

Change 87594,1 (ovirt-engine-sdk-java) 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/87594/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/791/

1 0

Do the CI support creating a github releases + assets?
by Roy Golan 14 Feb '18

14 Feb '18

I'm currently rolling my own makefile to create a release, with a binary file as assets. Does standard CI have something to publish artifacts in GH releases?

2 3

[oVirt CI] standard-enqueue - Build #10125 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 14 Feb '18

14 Feb '18

------=_Part_234_1331611098.1518608050920 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/10125/ Build Name: #10125 Build Description: Gerrit: 87594 - ovirt-engine-sdk-java (3.6, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/87594 - title: packaging: add support for newest fedoras - project: ovirt-engine-sdk-java - branch: sdk_3.6 - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_234_1331611098.1518608050920--

1 0

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

14 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1196/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 633e9a8b0cddbe18f68cd295f21a60e6675558be (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 633e9a8b0cddbe18f68cd295f21a60e6675558be Commit message: "ovirt-host: drop s390x fcraw jobs" > git rev-list 633e9a8b0cddbe18f68cd295f21a60e6675558be # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins5013792939690223846.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

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA) 14 Feb '18

14 Feb '18

This is a multi-part message in MIME format... ------------=_1518592373-16157-109 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1895: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518592373-16157-109 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1895:</h3> <pre>Resolution: Duplicate Status: Done (was: To Do)</pre> <blockquote><h3>CI votes not forwarded on commit message change</h3> <pre> Key: OVIRT-1895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: Yedidyah Bar David Assignee: infra</pre> <p>Hi all, If a change goes through this flow:</p> <ol><li><p>Push an update N</p></li> <li><p>CI triggers check-patch for N</p></li> <li><p>Push another update N+1 that changes only commit message</p></li> <li><p>CI marks +1 N</p></li></ol> <p>Then we have logic to not trigger CI for N+1 (with the assumption that a change to commit message should not affect the result), but also do not mark +1 N+1, leaving the patch unmarked. We should either forward the +1, when giving it, to all consecutive future patchsets that only changed the commit message, or give up on the optimization and always trigger CI. As an example, see: <a href="https://gerrit.ovirt.org/87515">https://gerrit.ovirt.org/87515</a> Best regards, — Didi</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</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> ------------=_1518592373-16157-109--

1 0

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA) 14 Feb '18

14 Feb '18

This is a multi-part message in MIME format... ------------=_1518592365-27516-116 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1895: -------------------------------- Component/s: Gerrit/git Epic Link: OVIRT-400 Issue Type: Bug (was: By-EMAIL) > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518592365-27516-116 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1895:</h3> <pre>Component/s: Gerrit/git Epic Link: OVIRT-400 Issue Type: Bug (was: By-EMAIL)</pre> <blockquote><h3>CI votes not forwarded on commit message change</h3> <pre> Key: OVIRT-1895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: Yedidyah Bar David Assignee: infra</pre> <p>Hi all, If a change goes through this flow:</p> <ol><li><p>Push an update N</p></li> <li><p>CI triggers check-patch for N</p></li> <li><p>Push another update N+1 that changes only commit message</p></li> <li><p>CI marks +1 N</p></li></ol> <p>Then we have logic to not trigger CI for N+1 (with the assumption that a change to commit message should not affect the result), but also do not mark +1 N+1, leaving the patch unmarked. We should either forward the +1, when giving it, to all consecutive future patchsets that only changed the commit message, or give up on the optimization and always trigger CI. As an example, see: <a href="https://gerrit.ovirt.org/87515">https://gerrit.ovirt.org/87515</a> Best regards, — Didi</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</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> ------------=_1518592365-27516-116--

1 0

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA) 14 Feb '18

14 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1895: -------------------------------- Epic Link: OVIRT-400 > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA) 14 Feb '18

14 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1895: ------------------------------------- [~didi(a)redhat.com] this had been reported many times in the past including by you in OVIRT-1627. See OVIRT-1639 for a tracker for solving this. Closing this ticket as a duplicate > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 190 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Feb '18

14 Feb '18

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/190/ Build Number: 190 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #190 [Dominik Holler] Use ansible to access ovirt-provider-ovn [Sandro Bonazzola] ovirt-dwh: drop fc27 on 4.2 ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 87289, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

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

1 0

[CQ]: 87284, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

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

1 0

[CQ]: 87489, 7 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 13 Feb '18

13 Feb '18

Change 87489,7 (ovirt-engine-metrics) 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/87489/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5639/

1 0

[CQ]: 87489,7 (ovirt-engine-metrics) failed "ovirt-4.2" system tests
by oVirt Jenkins 13 Feb '18

13 Feb '18

Change 87489,7 (ovirt-engine-metrics) 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/87489/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/775/

1 0

[CQ]: 87544, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

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

1 0

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Daniel Belenky (oVirt JIRA) 13 Feb '18

13 Feb '18

This is a multi-part message in MIME format... ------------=_1518516975-15615-100 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1895: --------------------------------------- It's a known bug that's coming from the Gerrit Trigger Plugin, the current solution is not to push commit message changes if you have CI tests running. > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518516975-15615-100 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky commented on OVIRT-1895:</h3> <p>It's a known bug that's coming from the Gerrit Trigger Plugin, the current solution is not to push commit message changes if you have CI tests running.</p> <blockquote><h3>CI votes not forwarded on commit message change</h3> <pre> Key: OVIRT-1895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> <p>Hi all, If a change goes through this flow:</p> <ol><li><p>Push an update N</p></li> <li><p>CI triggers check-patch for N</p></li> <li><p>Push another update N+1 that changes only commit message</p></li> <li><p>CI marks +1 N</p></li></ol> <p>Then we have logic to not trigger CI for N+1 (with the assumption that a change to commit message should not affect the result), but also do not mark +1 N+1, leaving the patch unmarked. We should either forward the +1, when giving it, to all consecutive future patchsets that only changed the commit message, or give up on the optimization and always trigger CI. As an example, see: <a href="https://gerrit.ovirt.org/87515">https://gerrit.ovirt.org/87515</a> Best regards, — Didi</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</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> ------------=_1518516975-15615-100--

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 220 - Failure!
by jenkins＠jenkins.phx.ovirt.org 13 Feb '18

13 Feb '18

------=_Part_203_56058073.1518425929826 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build Number: 220 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #220 [Yuval Turgeman] node-setup: added retries to `ssh nodectl check` ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_203_56058073.1518425929826--

1 1

[CQ]: 42386f6 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 42386f6 (ovirt-ansible-cluster-upgrade) failed. However, this change seems not to be the root cause for this failure. Change a11d8a2 (ovirt-ansible-cluster-upgrade) 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 a11d8a2 (ovirt-ansible-cluster- upgrade) 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://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/42386f62ae2b7… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/a11d8a267cc9e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/765/

1 0

[CQ]: 87509, 3 (ovirt-engine-metrics) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

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

1 0

[CQ]: 87466, 3 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

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

1 0

[CQ]: 87517,1 (ovirt-dwh) failed "ovirt-4.2" system tests
by oVirt Jenkins 13 Feb '18

13 Feb '18

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

1 0

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Yedidyah Bar David (oVirt JIRA) 13 Feb '18

13 Feb '18

Yedidyah Bar David created OVIRT-1895: ----------------------------------------- Summary: CI votes not forwarded on commit message change Key: OVIRT-1895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Hi all, If a change goes through this flow: 1. Push an update N 2. CI triggers check-patch for N 3. Push another update N+1 that changes only commit message 4. CI marks +1 N Then we have logic to not trigger CI for N+1 (with the assumption that a change to commit message should not affect the result), but also do not mark +1 N+1, leaving the patch unmarked. We should either forward the +1, when giving it, to all consecutive future patchsets that only changed the commit message, or give up on the optimization and always trigger CI. As an example, see: https://gerrit.ovirt.org/87515 Best regards, -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[CQ]: 87490, 2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87494, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87446, 3 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87419, 5 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87486, 4 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87481, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 79842,3 (ovirt-vmconsole) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 79842,3 (ovirt-vmconsole) 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/79842/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/744/

1 0

[CQ]: 87467,1 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87477, 1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 51d01f2 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 51d01f2 (ovirt-ansible-cluster-upgrade) failed. However, this change seems not to be the root cause for this failure. Change a11d8a2 (ovirt-ansible-cluster-upgrade) 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 a11d8a2 (ovirt-ansible-cluster- upgrade) 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://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/51d01f26fc09a… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/a11d8a267cc9e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/733/

1 0

[CQ]: 87311, 2 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: df0ac36 (ovirt-ansible-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change df0ac36 (ovirt-ansible-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-engine-setup/commit/df0ac36a48eccfe6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/729/

1 0

[CQ]: 6158001 (ovirt-ansible-vm-infra) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 6158001 (ovirt-ansible-vm-infra) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/6158001bfee53cae3e77… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/725/

1 0

[CQ]: 70fab0c (ovirt-ansible-manageiq) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 70fab0c (ovirt-ansible-manageiq) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-manageiq/commit/70fab0c177339e00bc42… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/721/

1 0

[CQ]: 87064, 4 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 1109fd8 (ovirt-ansible) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 1109fd8 (ovirt-ansible) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible/commit/1109fd8c3170432913888a09bfb10… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/717/

1 0

[ OST Failure Report ] [ oVirt Master (vdsmt) ] [ 12-0202018 ] [ 002_bootstrap.get_host_devices ] - Reminder
by Dafna Ron 12 Feb '18

12 Feb '18

hi, I saw this failure on Friday and I also see it in 4.2 branch as well as Master. host-0 did not finish installation on misconfiguration (which I can only asume has to do with the block device list) but I cannot see anything in host-0 or engine to suggest what was the actual problem. The patches its reporting are not related. *Link and headline of suspected patches: Not relatedLink to Job:* *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5613/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5613/>Link to all logs:* *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5613/artifacts <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5613/>(Relevant) error snippet from the log: <error>Api error: *Error Message Could not find block_vda1 device in host devices: Stacktrace Traceback (most recent call last): 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 runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 78, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py", line 1208, in get_host_devices raise RuntimeError('Could not find block_vda1 device in host devices: {}'.format(device_list)) RuntimeError: Could not find block_vda1 device in host devices: *eng*ine log: [dron@dron post-002_bootstrap.py]$ less lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log |grep host-0 2018-02-12 07:20:17,184-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-9) [ebedf4a6-07be-45b3-9062-7996c362f747] method: getByName, params: [lago-basic-suite-master-host-0], timeElapsed: 18ms 2018-02-12 07:20:17,201-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-9) [ebedf4a6-07be-45b3-9062-7996c362f747] method: getAllForHostname, params: [lago-basic-suite-master-host-0], timeElapsed: 17ms 2018-02-12 07:20:17,220-05 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-9) [ebedf4a6-07be-45b3-9062-7996c362f747] Connecting 'root@lago-basic-suite-master-host-0' 2018-02-12 07:20:17,414-05 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-9) [ebedf4a6-07be-45b3-9062-7996c362f747] Connected: 'root@lago-basic-suite-master-host-0' 2018-02-12 07:20:17,427-05 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-9) [ebedf4a6-07be-45b3-9062-7996c362f747] Authenticating: 'root@lago-basic-suite-master-host-0' 2018-02-12 07:20:17,490-05 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-9) [ebedf4a6-07be-45b3-9062-7996c362f747] Authenticated: 'root@lago-basic-suite-master-host-0' 2018-02-12 07:20:18,247-05 INFO [org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand] (default task-9) [21f04b96] START, RemoveVdsVDSCommand(HostName = lago-basic-suite-master-host-0, RemoveVdsVDSCommandParameters:{hostId='468d8314-e2e0-416b-af9d-295f8ab5a522'}), log id: 9f1017d 2018-02-12 07:20:18,262-05 INFO [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-9) [21f04b96] START, AddVdsVDSCommand(HostName = lago-basic-suite-master-host-0, AddVdsVDSCommandParameters:{hostId='468d8314-e2e0-416b-af9d-295f8ab5a522'}), log id: a336fc4 2018-02-12 07:20:18,288-05 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (default task-9) [21f04b96] Initialize vdsBroker 'lago-basic-suite-master-host-0:54321' 2018-02-12 07:20:18,345-05 DEBUG [org.ovirt.engine.core.vdsbroker.ResourceManager] (default task-9) [21f04b96] subscribe called with subscription id: lago-basic-suite-master-host-0|*|VM_status|* 2018-02-12 07:20:18,346-05 DEBUG [org.ovirt.engine.core.vdsbroker.ResourceManager] (default task-9) [21f04b96] subscribe called with subscription id: lago-basic-suite-master-host-0|net|host_conn|no_id 2018-02-12 07:20:18,369-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-9) [21f04b96] EVENT_ID: VDS_ALERT_FENCE_IS_NOT_CONFIGURED(9,000), Failed to verify Power Management configuration for Host lago-basic-suite-master-host-0. 2018-02-12 07:20:18,398-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-9) [21f04b96] EVENT_ID: USER_ADD_VDS(42), Host lago-basic-suite-master-host-0 was added by admin@internal-authz. 2018-02-12 07:20:18,486-05 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] Before Installation host 468d8314-e2e0-416b-af9d-295f8ab5a522, lago-basic-suite-masterhost-0 2018-02-12 07:20:18,549-05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] START, SetVdsStatusVDSCommand(HostName = lago-basic-suite-master-host-0, SetVdsStatusVDSCommandParameters:{hostId='468d8314-e2e0-416b-af9d-295f8ab5a522', status='Installing', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 4a95e559 2018-02-12 07:20:18,567-05 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHDialog] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] connect enter (lago-basic-suite-master-host-0:22, 1800000, 600000) 2018-02-12 07:20:18,567-05 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] Connecting 'root@lago-basic-suite-master-host-0' 2018-02-12 07:20:18,751-05 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] Connected: 'root@lago-basic-suite-master-host-0' 2018-02-12 07:20:18,767-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Connected to host lago-basic-suite-master-host-0 with SSH key fingerprint: SHA256:efkJTmSmltPF5S4VbnQ1avsb7whAX0dgLgxZJTxFgqo. 2018-02-12 07:20:18,767-05 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] Authenticating: 'root@lago-basic-suite-master-host-0' 2018-02-12 07:20:18,835-05 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] Authenticated: 'root@lago-basic-suite-master-host-0' 2018-02-12 07:20:18,835-05 INFO [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] Installation of lago-basic-suite-master-host-0. Executing command via SSH umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True < /var/cache/ovirt-engine/ovirt-host-deploy.tar 2018-02-12 07:20:18,888-05 INFO [org.ovirt.engine.core.uutils.ssh.SSHDialog] (EE-ManagedThreadFactory-engine-Thread-1) [7389a3fe] SSH execute 'root@lago-basic-suite-master-host-0' 'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True' 2018-02-12 07:20:19,933-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Initializing. 2018-02-12 07:20:20,094-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Environment setup. 2018-02-12 07:20:20,112-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Environment packages setup. 2018-02-12 07:20:24,084-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Programs detection. 2018-02-12 07:20:24,199-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Environment setup. 2018-02-12 07:20:24,205-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Environment customization. 2018-02-12 07:20:24,617-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Kdump supported. 2018-02-12 07:20:24,775-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Logs at host located at: '/tmp/ovirt-host-deploy-20180212072019-56s96x.log'. 2018-02-12 07:20:24,890-05 INFO [org.ovirt.engine.core.bll.hostdeploy.VdsDeployVdsmUnit] (VdsDeploy) [7389a3fe] Host lago-basic-suite-master-host-0 reports unique id A29E23CD-AF59-423B-9FCB-D3E4A0CD6AA1 2018-02-12 07:20:24,908-05 INFO [org.ovirt.engine.core.bll.hostdeploy.VdsDeployVdsmUnit] (VdsDeploy) [7389a3fe] Assigning unique id A29E23CD-AF59-423B-9FCB-D3E4A0CD6AA1 to Host lago-basic-suite-master-host-0 2018-02-12 07:20:24,987-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Disabling Kdump integration. 2018-02-12 07:20:25,070-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Setup validation. 2018-02-12 07:20:25,280-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Hardware supports virtualization. 2018-02-12 07:20:25,383-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Transaction setup. 2018-02-12 07:20:25,429-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Misc configuration. 2018-02-12 07:20:25,433-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Package installation. 2018-02-12 07:20:27,065-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Yum Status: Downloading Packages. 2018-02-12 07:20:27,069-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Yum Download/Verify: tuned-2.8.0-5.el7_4.2.noarch. 2018-02-12 07:20:27,074-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Yum Status: Check Package Signatures. 2018-02-12 07:20:27,078-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Yum Status: Running Test Transaction. 2018-02-12 07:20:27,192-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Yum Status: Running Transaction. 2018-02-12 07:20:27,309-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Yum update: 1/2: tuned-2.8.0-5.el7_4.2.noarch. 2018-02-12 07:20:27,524-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Yum updated: 2/2: tuned. 2018-02-12 07:20:29,174-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Yum Verify: 1/2: tuned.noarch 0:2.8.0-5.el7_4.2 - u. 2018-02-12 07:20:29,182-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Yum Verify: 2/2: tuned.noarch 0:2.8.0-5.el7 - ud. 2018-02-12 07:20:29,266-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [7389a3fe] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-basic-suite-master-host-0. Stage: Misc configuration. *</error>*

2 1

[CQ]: 34cc3c3 (ovirt-ansible-image-template) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 34cc3c3 (ovirt-ansible-image-template) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-image-template/commit/34cc3c3922b81c… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/713/

1 0

[CQ]: 449099e (ovirt-ansible-repositories) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 449099e (ovirt-ansible-repositories) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-repositories/commit/449099ea80719d43… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/709/

1 0

[JIRA] (OVIRT-1894) Add conditional execution parameter (run_if) to DSL options
by Daniel Belenky (oVirt JIRA) 12 Feb '18

12 Feb '18

This is a multi-part message in MIME format... ------------=_1518448129-17839-165 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1894?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1894: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Add conditional execution parameter (run_if) to DSL options > ----------------------------------------------------------- > > Key: OVIRT-1894 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: STDCI DSL > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > We want to have the ability to specify conditional execution of threads (stage, substage, ... ) with different conditions. > The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. > Example schema for the syntax: > {code:yaml} > --- > stage: check-patch > substage: > - change1: > run-if: > - file-changed: <filename> > - change2: > run-if: > - file-changed: > - <file1> > - <file2> > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518448129-17839-165 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1894?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky reassigned OVIRT-1894:</h3> <pre>Assignee: Daniel Belenky (was: infra)</pre> <blockquote><h3>Add conditional execution parameter (run_if) to DSL options</h3> <pre> Key: OVIRT-1894 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 Project: oVirt - virtualization made easy Issue Type: Improvement Components: STDCI DSL Reporter: Daniel Belenky Assignee: Daniel Belenky</pre> <p>We want to have the ability to specify conditional execution of threads (stage, substage, … ) with different conditions. The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. Example schema for the syntax: {code:yaml} --- stage: check-patch substage:</p> <pre> - change1: run-if: - file-changed: <filename> - change2: run-if: - file-changed: - <file1> - <file2></pre> <p>{code}</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</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> ------------=_1518448129-17839-165--

1 0

[JIRA] (OVIRT-1894) Add conditional execution parameter (run_if) to DSL options
by Daniel Belenky (oVirt JIRA) 12 Feb '18

12 Feb '18

This is a multi-part message in MIME format... ------------=_1518448116-12711-117 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1894?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1894: ---------------------------------- Epic Link: OVIRT-400 > Add conditional execution parameter (run_if) to DSL options > ----------------------------------------------------------- > > Key: OVIRT-1894 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > We want to have the ability to specify conditional execution of threads (stage, substage, ... ) with different conditions. > The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. > Example schema for the syntax: > {code:yaml} > --- > stage: check-patch > substage: > - change1: > run-if: > - file-changed: <filename> > - change2: > run-if: > - file-changed: > - <file1> > - <file2> > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518448116-12711-117 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1894?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1894:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Add conditional execution parameter (run_if) to DSL options</h3> <pre> Key: OVIRT-1894 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 Project: oVirt - virtualization made easy Issue Type: Improvement Components: STDCI DSL Reporter: Daniel Belenky Assignee: infra</pre> <p>We want to have the ability to specify conditional execution of threads (stage, substage, … ) with different conditions. The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. Example schema for the syntax: {code:yaml} --- stage: check-patch substage:</p> <pre> - change1: run-if: - file-changed: <filename> - change2: run-if: - file-changed: - <file1> - <file2></pre> <p>{code}</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</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> ------------=_1518448116-12711-117--

1 0

[JIRA] (OVIRT-1894) Add conditional execution parameter (run_if) to DSL options
by Daniel Belenky (oVirt JIRA) 12 Feb '18

12 Feb '18

Daniel Belenky created OVIRT-1894: ------------------------------------- Summary: Add conditional execution parameter (run_if) to DSL options Key: OVIRT-1894 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1894 Project: oVirt - virtualization made easy Issue Type: Improvement Components: STDCI DSL Reporter: Daniel Belenky Assignee: infra We want to have the ability to specify conditional execution of threads (stage, substage, ... ) with different conditions. The first condition to implement (and probably the most straightforward one) is to execute a thread in certain files were changed. Example schema for the syntax: {code:yaml} --- stage: check-patch substage: - change1: run-if: - file-changed: <filename> - change2: run-if: - file-changed: - <file1> - <file2> {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[CQ]: 87396,1 (ovirt-live) failed "ovirt-master" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 87396,1 (ovirt-live) 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/87396/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5617/

1 0

[oVirt CI] standard-enqueue - Build #9982 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Feb '18

12 Feb '18

------=_Part_209_1031571882.1518446894793 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9982/ Build Name: #9982 Build Description: Gerrit: 87408 - ovirt-log-collector (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/87408 - title: automation: add stdci - project: ovirt-log-collector - branch: ovirt-log-collector-3.6 - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_209_1031571882.1518446894793--

1 0

[CQ]: 46998fa (ovirt-ansible-infra) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 46998fa (ovirt-ansible-infra) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-infra/commit/46998fa9f79051ed435cd07… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/705/

1 0

[CQ]: a11d8a2 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change a11d8a2 (ovirt-ansible-cluster-upgrade) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/a11d8a267cc9e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/702/

1 0

[CQ]: 87486, 4 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87369, 5 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87394, 2 (ovirt-hosted-engine-ha) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 87394,2 (ovirt-hosted-engine-ha) 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/87394/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/697/

1 0

[CQ]: 87481, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 79842,3 (ovirt-vmconsole) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 79842,3 (ovirt-vmconsole) 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/79842/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/694/

4 5

[CQ]: 84635,14 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[JIRA] (OVIRT-1893) Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead
by eyal edri (oVirt JIRA) 12 Feb '18

12 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1893?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1893: ---------------------------------- The best way to solve it is to release a newer version than 1.1 with the fix, removing deployed versions from yum repos is not recommended and can cause issues to users/qe who is already using that repo. Also, master repo is pointing on nightly compose, not official release, you might want to use the 4.2 release rpm which includes only official releases ( and might also include the 0.1 version you're looking for ). [~sbonazzo@redhat.com][~bkorren@redhat.com] > Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead > ------------------------------------------------------------------------------------------ > > Key: OVIRT-1893 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1893 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Maor Lipchuk > Assignee: infra > > Hi all, > It seems that ovirt-ansible-disaster-recovery repo installed from upstream > [1] is installed with version 1.1 [2]: > ovirt-ansible-disaster-recovery-1.1 is broken, because of a bug which was > already fixed [3] in ovirt-ansible-disaster-recovery 0.1. > The thing is that the release which automatically installed is 1.1 although > the fix is available in ovirt-ansible-disaster-recovery 0.1. > Is there a way to do something about it, could we remove the 1.1 versions, > so 0.1 will be installed instead? > [1] http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > [2] > ovirt-ansible-disaster-recovery-1.1.0-0.1.master.20180104150940.el7.centos.noarch > [3] https://github.com/oVirt/ovirt-ansible-disaster-recovery/pull/4 > Regards, > Maor -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1268
by jenkins＠jenkins.phx.ovirt.org 12 Feb '18

12 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-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-centos-updates-el7-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 5095e42a4078481a012b7133945333cfcb61af44 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 5095e42a4078481a012b7133945333cfcb61af44 Commit message: "ovirt-engine-metrics: re-align" > git rev-list 5095e42a4078481a012b7133945333cfcb61af44 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins5318091456045681313.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-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 <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/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7/gen' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 87468, 1 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87469, 1 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87467,1 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87459,1 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[JIRA] (OVIRT-1893) Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead
by Maor Lipchuk (oVirt JIRA) 12 Feb '18

12 Feb '18

Maor Lipchuk created OVIRT-1893: ----------------------------------- Summary: Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead Key: OVIRT-1893 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1893 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Maor Lipchuk Assignee: infra Hi all, It seems that ovirt-ansible-disaster-recovery repo installed from upstream [1] is installed with version 1.1 [2]: ovirt-ansible-disaster-recovery-1.1 is broken, because of a bug which was already fixed [3] in ovirt-ansible-disaster-recovery 0.1. The thing is that the release which automatically installed is 1.1 although the fix is available in ovirt-ansible-disaster-recovery 0.1. Is there a way to do something about it, could we remove the 1.1 versions, so 0.1 will be installed instead? [1] http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm [2] ovirt-ansible-disaster-recovery-1.1.0-0.1.master.20180104150940.el7.centos.noarch [3] https://github.com/oVirt/ovirt-ansible-disaster-recovery/pull/4 Regards, Maor -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[CQ]: 87477, 1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87418,2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 87418,2 (ovirt-provider-ovn) 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/87418/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/682/

1 0

[JIRA] (OVIRT-1892) Make STDCI DSL case insensitive
by Daniel Belenky (oVirt JIRA) 12 Feb '18

12 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1892?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1892: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Make STDCI DSL case insensitive > ------------------------------- > > Key: OVIRT-1892 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1892 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: STDCI DSL > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > In order to prevent confusion among users of the DSL, it should be case insensitive, and even commas, underscores, and spaces should be ignored. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1892) Make STDCI DSL case insensitive
by Daniel Belenky (oVirt JIRA) 12 Feb '18

12 Feb '18

Daniel Belenky created OVIRT-1892: ------------------------------------- Summary: Make STDCI DSL case insensitive Key: OVIRT-1892 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1892 Project: oVirt - virtualization made easy Issue Type: Improvement Components: STDCI DSL Reporter: Daniel Belenky Assignee: infra In order to prevent confusion among users of the DSL, it should be case insensitive, and even commas, underscores, and spaces should be ignored. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1892) Make STDCI DSL case insensitive
by Daniel Belenky (oVirt JIRA) 12 Feb '18

12 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1892?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1892: ---------------------------------- Epic Link: OVIRT-400 > Make STDCI DSL case insensitive > ------------------------------- > > Key: OVIRT-1892 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1892 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > In order to prevent confusion among users of the DSL, it should be case insensitive, and even commas, underscores, and spaces should be ignored. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[OST] Some tests failed?
by Nir Soffer 12 Feb '18

12 Feb '18

I got this error when running OST with engine 4.2 - is this a test error? environment error? Looks like some error message needs work :-) http://jenkins.ovirt.org/job/ovirt-system-tests_manual/2157/console *00:10:32.263* @ Run test: 002_bootstrap.py: *00:10:32.281* nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']*00:10:32.301* # add_dc: *00:10:53.839* # add_dc: Success (in 0:00:21)*00:10:53.843* # add_cluster: *00:10:54.123* * Collect artifacts: *00:10:55.995* * Collect artifacts: Success (in 0:00:01)*00:10:56.000* # add_cluster: Success (in 0:00:02)*00:10:56.003* # Results located at /dev/shm/ost/deployment-basic-suite-4.2/default/002_bootstrap.py.junit.xml*00:10:56.005* @ Run test: 002_bootstrap.py: Success (in 0:00:23)*00:10:56.296* Error occured, aborting*00:10:56.296* Traceback (most recent call last):*00:10:56.296* File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 362, in do_run*00:10:56.297* self.cli_plugins[args.ovirtverb].do_run(args)*00:10:56.298* File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run*00:10:56.299* self._do_run(**vars(args))*00:10:56.299* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 505, in wrapper*00:10:56.300* return func(*args, **kwargs)*00:10:56.300* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 516, in wrapper*00:10:56.301* return func(*args, prefix=prefix, **kwargs)*00:10:56.301* File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 99, in do_ovirt_runtest*00:10:56.302* raise RuntimeError('Some tests failed')*00:10:56.303* RuntimeError: Some tests failed

2 1

[CQ]: 87451,5 (ovirt-dwh) failed "ovirt-master" system tests
by oVirt Jenkins 11 Feb '18

11 Feb '18

Change 87451,5 (ovirt-dwh) 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/87451/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5608/

1 0

[CQ]: 87454, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Feb '18

11 Feb '18

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

1 0

[CQ]: 87448, 4 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 11 Feb '18

11 Feb '18

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

1 0

[CQ]: 87454,1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests
by oVirt Jenkins 11 Feb '18

11 Feb '18

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

1 0

[CQ]: 87434, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 11 Feb '18

11 Feb '18

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

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 07-02-2018 ] [ 004_basic_sanity.vm_run ]
by Dafna Ron 11 Feb '18

11 Feb '18

Hi, We failed test 004_basic_sanity.vm_run in the upgrade from release suite. the reason we failed to run the vm is that the host was filtered from selection for vm. Please also notice other errors in the log relating to network sync failing. *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/87116/5 <https://gerrit.ovirt.org/#/c/87116/5> - core: Add 4.3 support Link to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/artifact/>(Relevant) error snippet from the log: <error>2018-02-06 16:42:39,431-05 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 4d0244492018-02-06 16:42:39,472-05 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] Running command: RunVmOnceCommand internal: false. Entities affected : ID: ccfe9852-f2d6-4e18-8213-29d958d3a8ed Type: VMAction group RUN_VM with role type USER, ID: ccfe9852-f2d6-4e18-8213-29d958d3a8ed Type: VMAction group EDIT_ADMIN_VM_PROPERTIES with role type ADMIN2018-02-06 16:42:39,486-05 INFO [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] Candidate host 'lago-upgrade-from-release-suite-master-host0' ('6ec7721d-beae-4b7e-807f-7f3a794fb7c4') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'CPU-Level' (correlation id: 03cdc0e6-eb94-46a4-9882-77762b2ed787)2018-02-06 16:42:39,486-05 ERROR [org.ovirt.engine.core.bll.RunVmCommand] (default task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] Can't find VDS to run the VM 'ccfe9852-f2d6-4e18-8213-29d958d3a8ed' on, so this VM will not be run.2018-02-06 16:42:39,493-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM vm0 (User: admin(a)internal-authz).2018-02-06 16:42:39,500-05 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] Lock freed to object 'EngineLock:{exclusiveLocks='[ccfe9852-f2d6-4e18-8213-29d958d3a8ed=VM]', sharedLocks=''}'2018-02-06 16:42:39,505-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-5) [] Operation Failed: []2018-02-06 16:42:39,512-05 INFO [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-17) [4fe81490] Running command: ProcessDownVmCommand internal: true.(END)</error>*

6 8

[CQ]: 87171,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 11 Feb '18

11 Feb '18

Change 87171,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/87171/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5597/

2 1

[JIRA] (OVIRT-1891) Add a tool to locally test stdci.yaml configuration
by Daniel Belenky (oVirt JIRA) 11 Feb '18

11 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1891?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1891: ---------------------------------- Epic Link: OVIRT-400 > Add a tool to locally test stdci.yaml configuration > --------------------------------------------------- > > Key: OVIRT-1891 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1891 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > Labels: first_time_task, standard-ci > > As the production usage of STDCI DSL is up around the corner, we should create a simple tool to allow users to test their configurations locally, to show them the jobs/environments that will be generated by their config. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1891) Add a tool to locally test stdci.yaml configuration
by Daniel Belenky (oVirt JIRA) 11 Feb '18

11 Feb '18

Daniel Belenky created OVIRT-1891: ------------------------------------- Summary: Add a tool to locally test stdci.yaml configuration Key: OVIRT-1891 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1891 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Standard CI (Pipelines), STDCI DSL Reporter: Daniel Belenky Assignee: infra As the production usage of STDCI DSL is up around the corner, we should create a simple tool to allow users to test their configurations locally, to show them the jobs/environments that will be generated by their config. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 199 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 Feb '18

11 Feb '18

------=_Part_177_410376571.1518233468420 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/199/ Build Number: 199 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #199 [Dafna Ron] basic-suite-master: disabling get_host_numa_nodes [Sandro Bonazzola] ovirt-imageio: re-align [Sandro Bonazzola] imgbased: re-align [Sandro Bonazzola] ovirt-hosted-engine-ha: re-align [Sandro Bonazzola] ovirt-engine-sdk: re-align [Sandro Bonazzola] pthreading: re-align [Ondra Machacek] ovirt-engine-sdk-python: Update branch to 4.2 [Sandro Bonazzola] ovirt-engine-api-model: re-align [Sandro Bonazzola] ovirt-live: add project [Sandro Bonazzola] ovirt-engine-metrics: re-align ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_master_storage_domain Error Message: Could not find hosts that are up in DC Default -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:0cd1a9a0-4e99-4316-8394-251edbecee52:Get ssh client for lago-he-basic-suite-master-storage: lago.ssh: DEBUG: end task:0cd1a9a0-4e99-4316-8394-251edbecee52:Get ssh client for lago-he-basic-suite-master-storage: lago.ssh: DEBUG: Running c6ebea6c on lago-he-basic-suite-master-storage: cat /root/multipath.txt lago.ssh: DEBUG: Command c6ebea6c on lago-he-basic-suite-master-storage returned with 0 lago.ssh: DEBUG: Command c6ebea6c on lago-he-basic-suite-master-storage output: 3600140567931dd153fc4e039cabd162a 360014057142c30a2c6b4bc5bdb8488ce 3600140586cb843131664d80bb8f80f12 36001405883b7f7869fe4a7090ba4cd77 36001405ae995f75a8fc45eb945e120b6 --------------------- >> 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 runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in 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-master/ovirt-system-tests/he-basic-suite-master/test-scenarios/002_bootstrap.py", line 485, in add_master_storage_domain add_iscsi_storage_domain(prefix) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-master/ovirt-system-tests/he-basic-suite-master/test-scenarios/002_bootstrap.py", line 600, in add_iscsi_storage_domain host=_random_host_from_dc(api, DC_NAME), File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-master/ovirt-system-tests/he-basic-suite-master/test-scenarios/002_bootstrap.py", line 102, in _random_host_from_dc return random.choice(_hosts_in_dc(api, dc_name)) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-master/ovirt-system-tests/he-basic-suite-master/test-scenarios/002_bootstrap.py", line 92, in _hosts_in_dc raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name) 'Could not find hosts that are up in DC Default\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:0cd1a9a0-4e99-4316-8394-251edbecee52:Get ssh client for lago-he-basic-suite-master-storage:\nlago.ssh: DEBUG: end task:0cd1a9a0-4e99-4316-8394-251edbecee52:Get ssh client for lago-he-basic-suite-master-storage:\nlago.ssh: DEBUG: Running c6ebea6c on lago-he-basic-suite-master-storage: cat /root/multipath.txt\nlago.ssh: DEBUG: Command c6ebea6c on lago-he-basic-suite-master-storage returned with 0\nlago.ssh: DEBUG: Command c6ebea6c on lago-he-basic-suite-master-storage output:\n 3600140567931dd153fc4e039cabd162a\n360014057142c30a2c6b4bc5bdb8488ce\n3600140586cb843131664d80bb8f80f12\n36001405883b7f7869fe4a7090ba4cd77\n36001405ae995f75a8fc45eb945e120b6\n\n--------------------- >> end captured logging << ---------------------' ------=_Part_177_410376571.1518233468420--

2 2

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 183 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 Feb '18

11 Feb '18

------=_Part_109_2133950097.1517888604454 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/183/ Build Number: 183 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #183 [Sandro Bonazzola] hc-basic-suite-4.1: add centos-qemu-ev-release-el7 [Sandro Bonazzola] ovirt-engine: dropped fcraw on master [Barak Korren] Add a timeout to pipline STDCI jobs [Sandro Bonazzola] ovirt-guest-agent: drop el6 on >= 4.2 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_109_2133950097.1517888604454--

3 7

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 33 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 Feb '18

11 Feb '18

------=_Part_175_1841804717.1518230064185 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build Number: 33 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #33 [Dafna Ron] basic-suite-master: disabling get_host_numa_nodes [Sandro Bonazzola] ovirt-imageio: re-align [Sandro Bonazzola] imgbased: re-align [Sandro Bonazzola] ovirt-hosted-engine-ha: re-align [Sandro Bonazzola] ovirt-engine-sdk: re-align [Sandro Bonazzola] pthreading: re-align [Ondra Machacek] ovirt-engine-sdk-python: Update branch to 4.2 [Sandro Bonazzola] ovirt-engine-api-model: re-align [Sandro Bonazzola] ovirt-live: add project [Sandro Bonazzola] ovirt-engine-metrics: re-align ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_175_1841804717.1518230064185--

1 1