February 2018 - Infra - oVirt List Archives

[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