February 2018 - Infra - oVirt List Archives

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

21 Feb '18

------=_Part_252_1340298953.1518660704291 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: 38 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #38 [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_252_1340298953.1518660704291--

4 14

[CQ]: 87974,1 (cockpit-ovirt) failed "ovirt-4.2" system tests
by oVirt Jenkins 20 Feb '18

20 Feb '18

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

1 0

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

20 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87840,5 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 86405,7 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86405,7 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87840/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86405/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5799/

1 0

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

20 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/5794/

1 0

[CQ]: 86405,7 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 20 Feb '18

20 Feb '18

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

1 0

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

20 Feb '18

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

1 0

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

20 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1844: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > jenkins_master_deploy-configs_merged failing do to missing libraries > -------------------------------------------------------------------- > > Key: OVIRT-1844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > Since patches related to OVIRT-1746, mainly https://gerrit.ovirt.org/85158/, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: > http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso… > File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> > from xdg.BaseDirectory import xdg_cache_home > ImportError: No module named xdg.BaseDirectory -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[oVirt Jenkins] ovirt-release_master_build-artifacts-fcraw-x86_64 - Build # 22 - Fixed!
by jenkins＠jenkins.phx.ovirt.org 20 Feb '18

20 Feb '18

------=_Part_11_1809744156.1519138573235 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86… Build: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86… Build Number: 22 Build Status: Fixed Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #21 [Sandro Bonazzola] Add Javier Coscia [Sandro Bonazzola] fedora: provide katello-agent [Daniel Belenky] std enqueue: Add env.GERRIT_TRIGGER_CI_VOTE_LABEL [Daniel Belenky] cleanup: Fix race when unmounting dirs in chroot [Daniel Belenky] Add a tool to check if a change is merged Changes for Build #22 [Sandro Bonazzola] fedora: provide katello-agent [Sandro Bonazzola] ovirt-provider-ovn: drop manual jobs [Dafna Ron] jenkins: adding infra(a)ovirt.org to the alert list [Barak Korren] Run `pusher.py` on non-Gerrit events [Daniel Belenky] Utilize stdci_dsl api in standard-stage ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_11_1809744156.1519138573235--

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) 20 Feb '18

20 Feb '18

This is a multi-part message in MIME format... ------------=_1519137694-17807-279 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1893?page=com.atlassian.jira.… ] Maor Lipchuk commented on OVIRT-1893: ------------------------------------- We thought about building a newer build of ovirt-ansible-disaster-recovery-1.1 so it will be installed instead of the 1.1, but we first need first to solve an issue in the repo. It could be great if the 1.1 build will be removed since it is currently broken. Regards, Maor On Tue, Feb 20, 2018 at 4:29 PM, eyal edri (oVirt JIRA) < > 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#100080) ------------=_1519137694-17807-279 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1893?page=com.atlassian.jira.… ]</pre> <h3>Maor Lipchuk commented on OVIRT-1893:</h3> <p>We thought about building a newer build of ovirt-ansible-disaster-recovery-1.1 so it will be installed instead of the 1.1, but we first need first to solve an issue in the repo. It could be great if the 1.1 build will be removed since it is currently broken.</p> <p>Regards, Maor</p> <p>On Tue, Feb 20, 2018 at 4:29 PM, eyal edri (oVirt JIRA) <</p> <blockquote><h3>Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead</h3> <pre> 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</pre> <p>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] <a href="http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm">http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm</a> [2] ovirt-ansible-disaster-recovery-1.1.0-0.1.master.20180104150940.el7.centos.noarch [3] <a href="https://github.com/oVirt/ovirt-ansible-disaster-recovery/pull/4">https://github.com/oVirt/ovirt-ansible-disaster-recovery/pull/4</a> Regards, Maor</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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> ------------=_1519137694-17807-279--

1 0

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

20 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/5778/

1 0

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

20 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1844: ------------------------------------- [~eedri] as you can see in comments above, [~ederevea] fixed the issue manually. > jenkins_master_deploy-configs_merged failing do to missing libraries > -------------------------------------------------------------------- > > Key: OVIRT-1844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > Since patches related to OVIRT-1746, mainly https://gerrit.ovirt.org/85158/, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: > http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso… > File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> > from xdg.BaseDirectory import xdg_cache_home > ImportError: No module named xdg.BaseDirectory -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

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) 20 Feb '18

20 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1893?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1893: ---------------------------------- [~mlipchuk(a)redhat.com] is this still an issue? > 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#100080)

1 0

[JIRA] (OVIRT-1896) Fwd: repoman error
by eyal edri (oVirt JIRA) 20 Feb '18

20 Feb '18

This is a multi-part message in MIME format... ------------=_1519136915-32384-126 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1896?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1896: -------------------------------- Assignee: Anton Marchukov (was: infra) > 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: Anton Marchukov > > 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#100080) ------------=_1519136915-32384-126 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1896?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1896:</h3> <pre>Assignee: Anton Marchukov (was: infra)</pre> <blockquote><h3>Fwd: repoman error</h3> <pre> 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: Anton Marchukov</pre> <p>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):</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 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). Thanks in advance, — 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</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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> ------------=_1519136915-32384-126--

1 0

[JIRA] (OVIRT-1901) View/Expand all missing in some jobs
by eyal edri (oVirt JIRA) 20 Feb '18

20 Feb '18

This is a multi-part message in MIME format... ------------=_1519136871-15954-276 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1901?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1901: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > View/Expand all missing in some jobs > ------------------------------------ > > Key: OVIRT-1901 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1901 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: Evgheni Dereveanchin > > Hi, > Some jenkins jobs have under "Build Artifacts" a Java-script "+ View", > "Expand all" etc that let you see artifacts directly from the build > page, e.g. [1]. Some don't, e.g. [2]. It will be useful if this option > exists in all jobs. Thanks, > [1] http://jenkins.ovirt.org/job/ovirt-dwh_master_check-patch-el7-x86_64/171/ > [2] http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/368… > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519136871-15954-276 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1901?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1901:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>View/Expand all missing in some jobs</h3> <pre> Key: OVIRT-1901 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1901 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: Evgheni Dereveanchin</pre> <p>Hi, Some jenkins jobs have under “Build Artifacts” a Java-script “+ View”, “Expand all” etc that let you see artifacts directly from the build page, e.g. [1]. Some don't, e.g. [2]. It will be useful if this option exists in all jobs. Thanks, [1] <a href="http://jenkins.ovirt.org/job/ovirt-dwh_master_check-patch-el7-x86_64/171/">http://jenkins.ovirt.org/job/ovirt-dwh_master_check-patch-el7-x86_64/171/</a> [2] <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/368…">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/368…</a> — Didi</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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> ------------=_1519136871-15954-276--

1 0

[JIRA] (OVIRT-1903) awkward error on an OST change
by eyal edri (oVirt JIRA) 20 Feb '18

20 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1903?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1903: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > awkward error on an OST change > ------------------------------ > > Key: OVIRT-1903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1903 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: danken > Assignee: infra > > My benign change https://gerrit.ovirt.org/#/c/87821/ caused an error that I fail to parse in OST > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

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

20 Feb '18

This is a multi-part message in MIME format... ------------=_1519136760-20242-279 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1844: ---------------------------------- Any update? > jenkins_master_deploy-configs_merged failing do to missing libraries > -------------------------------------------------------------------- > > Key: OVIRT-1844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > Since patches related to OVIRT-1746, mainly https://gerrit.ovirt.org/85158/, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: > http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso… > File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> > from xdg.BaseDirectory import xdg_cache_home > ImportError: No module named xdg.BaseDirectory -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519136760-20242-279 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1844:</h3> <p>Any update?</p> <blockquote><h3>jenkins_master_deploy-configs_merged failing do to missing libraries</h3> <pre> Key: OVIRT-1844 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: High</pre> <p>Since patches related to OVIRT-1746, mainly <a href="https://gerrit.ovirt.org/85158/">https://gerrit.ovirt.org/85158/</a>, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: <a href="http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso…">http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso…</a></p> <pre> File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> from xdg.BaseDirectory import xdg_cache_home ImportError: No module named xdg.BaseDirectory</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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> ------------=_1519136760-20242-279--

1 0

[JIRA] (OVIRT-1856) Document procedure for infra upgrades
by eyal edri (oVirt JIRA) 20 Feb '18

20 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1856?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1856: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Document procedure for infra upgrades > -------------------------------------- > > Key: OVIRT-1856 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1856 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > Priority: High > > On Sun, Jan 21, 2018 at 1:01 PM, Barak Korren <bkorren(a)redhat.com> wrote: > > > > > > On 21 January 2018 at 12:50, Eyal Edri <eedri(a)redhat.com> wrote: > > > >> > >> > >> On Sun, Jan 21, 2018 at 12:47 PM, Barak Korren <bkorren(a)redhat.com> > >> wrote: > >> > >>> > >>> > >>> On 21 January 2018 at 12:39, Eyal Edri <eedri(a)redhat.com> wrote: > >>> > >>>> There is another issue, which is currently failing all CQ, and its > >>>> related to the new IBRS CPU model. > >>>> It looks like all of the lago slaves were upgraded to new Libvirt and > >>>> kernel on Friday, while we still don't have a fix on lago-ost-plugin for > >>>> that. > >>>> > >>>> I think there was a misunderstanding about what to upgrade, and it > >>>> might have been understood that only the bios upgrade breaks it and not the > >>>> kernel one. > >>>> > >>>> In any case, we're currently fixing the issue, either by downgrading > >>>> the relevant pkgs on lago slaves or adding the mapping to new CPU types > >>>> from OST. > >>>> > >>>> For future, I suggest a few updates to maintenance work on Jenkins > >>>> slaves ( VMs or BM ): > >>>> > >>>> 1. Let's avoid doing an upgrade close to a weekend ( i.e not on Thu-Sun > >>>> ), so all the team can be around to help if needed or if something > >>>> unexpected happens. > >>>> 2. When we have a system-wide upgrade scheduled, like all BM slaves or > >>>> VMs for a specific OS, let's adopt a gradual upgrade with a few days window > >>>> in between, > >>>> e.g, if we need to upgrade all Lago slaves, let's upgrade 1-2 and > >>>> wait to see if nothing breaks and continue after we verify OST runs ( > >>>> either seeing on CQ or running manually ) > >>>> > >>>> > >>>> Thoughts? > >>>> > >>>> > >>> We have a staging system - we should be using it for staging.... > >>> > >> > >> Do we have OST tests or manual job avaialble there? > >> > > > > We can add them easily, or simply run Lago manually when needed. > > > > > >> In any case, this doesn't contradict what I suggested, even if you test > >> on staging, there could be differences from the production system, so we > >> should take care when we upgrade regardless. > >> > > > > Yes, but at least we'd know we green lighted the new configuration - I'm > > sure in this case we could have found at least some of the issues on > > staging (Like the fc27 issues for example) and could have avoided expansive > > production failures. > > > > Another point when scheduling an upgrade, is to talk to infra owner or the > >> CI team and understand if we currently have a large Q in CQ or known > >> failures, so it might be best to wait a bit until its cleared. > >> > >> > > > > > Adding infra-support so we can gather this info and prepare a maintanaince > / upgrade checklist to add to the oVirt infra docs. > Let's continue the discussion, suggestion on that ticket. > > -- > > Barak Korren > > RHV DevOps team , RHCE, RHCi > > Red Hat EMEA > > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1905) IPv6 not enabled on FC27 slaves
by eyal edri (oVirt JIRA) 20 Feb '18

20 Feb '18

This is a multi-part message in MIME format... ------------=_1519136487-16545-290 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1905?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1905: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > IPv6 not enabled on FC27 slaves > ------------------------------- > > Key: OVIRT-1905 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1905 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: Evgheni Dereveanchin > > Hello, > VDSM check-patch tests require IPv6 enabled on the slave which runs them. > It seems that one such slave does not have IPv6 enabled. > http://jenkins.ovirt.org/job/vdsm_4.2_check-patch-fc27-x86_64/71/ > Thanks, > Edy. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519136487-16545-290 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1905?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1905:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>IPv6 not enabled on FC27 slaves</h3> <pre> Key: OVIRT-1905 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1905 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: Evgheni Dereveanchin</pre> <p>Hello, VDSM check-patch tests require IPv6 enabled on the slave which runs them. It seems that one such slave does not have IPv6 enabled. <a href="http://jenkins.ovirt.org/job/vdsm_4.2_check-patch-fc27-x86_64/71/">http://jenkins.ovirt.org/job/vdsm_4.2_check-patch-fc27-x86_64/71/</a> Thanks, Edy.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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> ------------=_1519136487-16545-290--

1 0

[JIRA] (OVIRT-1905) IPv6 not enabled on FC27 slaves
by Edward Haas (oVirt JIRA) 20 Feb '18

20 Feb '18

This is a multi-part message in MIME format... ------------=_1519136013-18143-293 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Edward Haas created OVIRT-1905: ---------------------------------- Summary: IPv6 not enabled on FC27 slaves Key: OVIRT-1905 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1905 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: infra Hello, VDSM check-patch tests require IPv6 enabled on the slave which runs them. It seems that one such slave does not have IPv6 enabled. http://jenkins.ovirt.org/job/vdsm_4.2_check-patch-fc27-x86_64/71/ Thanks, Edy. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519136013-18143-293 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Edward Haas created OVIRT-1905:</h3> <pre> Summary: IPv6 not enabled on FC27 slaves Key: OVIRT-1905 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1905 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: infra</pre> <p>Hello,</p> <p>VDSM check-patch tests require IPv6 enabled on the slave which runs them. It seems that one such slave does not have IPv6 enabled.</p> <p><a href="http://jenkins.ovirt.org/job/vdsm_4.2_check-patch-fc27-x86_64/71/">http://jenkins.ovirt.org/job/vdsm_4.2_check-patch-fc27-x86_64/71/</a></p> <p>Thanks, Edy.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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> ------------=_1519136013-18143-293--

1 0

Jenkins build is back to normal : deploy-to_ovirt-4.1_tested #1136
by jenkins＠jenkins.phx.ovirt.org 20 Feb '18

20 Feb '18

See <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.1_tested/1136/display/redire…>

1 0

Jenkins build is back to normal : system-sync_mirrors-fedora-base-fc27-x86_64 #405
by jenkins＠jenkins.phx.ovirt.org 20 Feb '18

20 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc27-x86_64/40…>

1 0

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

20 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1217/displ…> Changes: [Sandro Bonazzola] ovirt-provider-ovn: drop manual jobs [Dafna Ron] jenkins: adding infra(a)ovirt.org to the alert list ------------------------------------------ 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 eca59747fe7f94ae8694f3e69768a4ce4a71a60f (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f eca59747fe7f94ae8694f3e69768a4ce4a71a60f Commit message: "jenkins: adding infra(a)ovirt.org to the alert list" > git rev-list --no-walk 28d0b911763057b7a04becf847853d57af4e3a25 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins7237571100229054612.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

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #126
by jenkins＠jenkins.phx.ovirt.org 20 Feb '18

20 Feb '18

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/126/display/red…>

1 1

Jenkins build became unstable: ovirt_master_publish-rpms_nightly #879
by jenkins＠jenkins.phx.ovirt.org 20 Feb '18

20 Feb '18

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/879/display/…>

2 4

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

20 Feb '18

Hi, We have a failed test for project ovirt-engine-metrics. It seems that CQ is reporting that the root cause of the failure was a patch from 6 days ago. Shirly, can you please check the changes? *Link and headline of suspected patches: change reported as failed: * replace vdsm stats with collectd virt plugin - https://gerrit.ovirt.org/#/c/87310/ *change reported as root cause: * ansible: add role to copy required files - https://gerrit.ovirt.org/#/c/87430/ TASK [oVirt.ovirt-initial-validations/validate-config-yml : Validate viaq_metrics_store parameter] *** fatal: [localhost]: FAILED! => {"msg": "The conditional check 'viaq_metrics_store != true' failed. The error was: error while evaluating conditional (viaq_metrics_store != true): 'viaq_metrics_store' is undefined\n\nThe error appears to have been in '/usr/share/ansible/roles/oVirt.metrics/roles/oVirt.ovirt-initial-validations/validate-config-yml/tasks/main.yml': line 49, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: \"Validate viaq_metrics_store parameter\"\n ^ here\n"} NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* localhost : ok=4 changed=0 unreachable=0 failed=1 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 lago.ssh: DEBUG: Command 59b597f6 on lago-basic-suite-4-2-engine returned with 0 lago.ssh: DEBUG: Command 59b597f6 on lago-basic-suite-4-2-engine output: This command will collect system configuration and diagnostic information from this system. The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. INFO: /dev/shm/log does not exist. It will be created. DEBUG: API Vendor(None) API Version(4.2.0) WARNING: This ovirt-log-collector call will collect logs from all available hosts. This may take long time, depending on the size of your deployment INFO: Gathering oVirt Engine information... DEBUG: loading config '/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf' DEBUG: calling(['sosreport', '--list-plugins']) DEBUG: returncode(0) DEBUG: STDOUT( sosreport (version 3.4) *Link to Job:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/864/ <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/864/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/864/artifac… <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/864/artifacts>(Relevant) error snippet from the log: <error></error>*

3 4