- Infra - oVirt List Archives

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

15 Feb '18

------=_Part_254_89133842.1518663529822 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/204/ Build Number: 204 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #204 [Gal Ben Haim] 4.2: Update reposync-config.repo [Sandro Bonazzola] ovirt-engine-api-explorer: re-align [Barak Korren] Use usrc.py in check-patch.sh ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_254_89133842.1518663529822--

2 2

[JIRA] (OVIRT-1898) Please add me (omachace) and Ori (oliel) as maintainers of ovirt-engine-api-explorer project
by Ondra Machacek (oVirt JIRA) 15 Feb '18

15 Feb '18

Ondra Machacek created OVIRT-1898: ------------------------------------- Summary: Please add me (omachace) and Ori (oliel) as maintainers of ovirt-engine-api-explorer project Key: OVIRT-1898 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1898 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git Reporter: Ondra Machacek Assignee: infra As Juan left, please add me (omachace) and Ori (oliel) as maintainers of ovirt-engine-api-explorer project. Thanks cc [~mwperina] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[CQ]: 87712, 2 (ovirt-engine-nodejs-modules) failed "ovirt-4.1" system tests
by oVirt Jenkins 15 Feb '18

15 Feb '18

Change 87712,2 (ovirt-engine-nodejs-modules) 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/87712/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1643/

1 0

[JIRA] (OVIRT-1897) resources fileserver performing slow
by Evgheni Dereveanchin (oVirt JIRA) 15 Feb '18

15 Feb '18

This is a multi-part message in MIME format... ------------=_1518688455-17376-271 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1897?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1897: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > resources fileserver performing slow > ------------------------------------ > > Key: OVIRT-1897 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1897 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: High > > The resources file server has been performing slowly for the last couple of days. Looks like most of the load is caused by repoman however this is not a new tool and we didn't have this problem before. Opening a ticket to investigate the root cause. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518688455-17376-271 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1897?page=com.atlassian.jira.… ]</pre> <h3>Evgheni Dereveanchin reassigned OVIRT-1897:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>resources fileserver performing slow</h3> <pre> Key: OVIRT-1897 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1897 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: Evgheni Dereveanchin Priority: High</pre> The resources file server has been performing slowly for the last couple of days. Looks like most of the load is caused by repoman however this is not a new tool and we didn't have this problem before. Opening a ticket to investigate the root cause.</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) <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> ------------=_1518688455-17376-271--

1 0

[JIRA] (OVIRT-1897) resources fileserver performing slow
by Evgheni Dereveanchin (oVirt JIRA) 15 Feb '18

15 Feb '18

Evgheni Dereveanchin created OVIRT-1897: ------------------------------------------- Summary: resources fileserver performing slow Key: OVIRT-1897 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1897 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: High The resources file server has been performing slowly for the last couple of days. Looks like most of the load is caused by repoman however this is not a new tool and we didn't have this problem before. Opening a ticket to investigate the root cause. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[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> 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): <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> do_add <pre> repo.save() File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 42,</pre> in _func <pre> return func(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 201,</pre> in save <pre> store.save() File</pre> “/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py”, line 263, in save <pre> self._save(**args) File</pre> “/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py”, line 305, in _save <pre> self.sign_rpms() File</pre> “/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py”, line 524, in sign_rpms <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> line 272, in sign <pre>raise exc</pre> 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: <pre>0: re.compile("pass phrase: ") 1: re.compile("passphrase: ") 2: re.compile("Passphrase: ")</pre> 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: <a href="https://gerrit.ovirt.org/#/c/87694/">https://gerrit.ovirt.org/#/c/87694/</a> (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). <h3>Thanks in advance,</h3> Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <<a href="https://www.redhat.com/">https://www.redhat.com</a>> 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 — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) <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 14 Feb '18

14 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 14 Feb '18

14 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 14 Feb '18

14 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 14 Feb '18

14 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 14 Feb '18

14 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 14 Feb '18

14 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 14 Feb '18

14 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> Hi all, If a change goes through this flow: <ol><li>Push an update N</li> <li>CI triggers check-patch for N</li> <li>Push another update N+1 that changes only commit message</li> <li>CI marks +1 N</li></ol> 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</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) <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> Hi all, If a change goes through this flow: <ol><li>Push an update N</li> <li>CI triggers check-patch for N</li> <li>Push another update N+1 that changes only commit message</li> <li>CI marks +1 N</li></ol> 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</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) <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 13 Feb '18

13 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> 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. <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> Hi all, If a change goes through this flow: <ol><li>Push an update N</li> <li>CI triggers check-patch for N</li> <li>Push another update N+1 that changes only commit message</li> <li>CI marks +1 N</li></ol> 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</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) <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