- Infra - oVirt List Archives

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1163
by jenkins＠jenkins.phx.ovirt.org 11 Jan '18

11 Jan '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 fd03fa52a1e8bc9b4c687967ec3909b51b8b1238 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f fd03fa52a1e8bc9b4c687967ec3909b51b8b1238 Commit message: "Skip 'pusher.py' when jobs are triggered manually" > git rev-list fd03fa52a1e8bc9b4c687967ec3909b51b8b1238 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins7543104959395246052.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 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-1839) mock_runner.sh broken on FC27 because of GDBM import issues
by Barak Korren (oVirt JIRA) 11 Jan '18

11 Jan '18

This is a multi-part message in MIME format... ------------=_1515653586-23683-351 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1839?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1839: ----------------------------------- Assignee: Barak Korren (was: infra) > mock_runner.sh broken on FC27 because of GDBM import issues > ----------------------------------------------------------- > > Key: OVIRT-1839 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1839 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: mock_runner > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > Labels: fedora, gdbm > > Unit tests for '{{mock_runner.sh}}' Python code have shown us that it now fails with errors while importing the '{{gdbm}}' package. > It seems the latest '{{gdbm}}' package in Fedora (1.14-1) was changes in a way that is incompatible with its Python bindings. The previous version (1.13-3) seems to work just fine. > A bug was reported to the Fedora project: > https://bugzilla.redhat.com/show_bug.cgi?id=1533176 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515653586-23683-351 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1839?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1839:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>mock_runner.sh broken on FC27 because of GDBM import issues</h3> <pre> Key: OVIRT-1839 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1839 Project: oVirt - virtualization made easy Issue Type: Outage Components: mock_runner Reporter: Barak Korren Assignee: Barak Korren Priority: High Labels: fedora, gdbm</pre> <p>Unit tests for ‘{{mock_runner.sh}}’ Python code have shown us that it now fails with errors while importing the ‘{{gdbm}}’ package. It seems the latest ‘{{gdbm}}’ package in Fedora (1.14-1) was changes in a way that is incompatible with its Python bindings. The previous version (1.13-3) seems to work just fine. A bug was reported to the Fedora project: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1533176">https://bugzilla.redhat.com/show_bug.cgi?id=1533176</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515653586-23683-351--

1 0

[JIRA] (OVIRT-1839) mock_runner.sh broken on FC27 because of GDBM import issues
by Barak Korren (oVirt JIRA) 11 Jan '18

11 Jan '18

This is a multi-part message in MIME format... ------------=_1515653559-21047-356 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1839: ----------------------------------- Summary: mock_runner.sh broken on FC27 because of GDBM import issues Key: OVIRT-1839 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1839 Project: oVirt - virtualization made easy Issue Type: Outage Components: mock_runner Reporter: Barak Korren Assignee: infra Priority: High Unit tests for '{{mock_runner.sh}}' Python code have shown us that it now fails with errors while importing the '{{gdbm}}' package. It seems the latest '{{gdbm}}' package in Fedora (1.14-1) was changes in a way that is incompatible with its Python bindings. The previous version (1.13-3) seems to work just fine. A bug was reported to the Fedora project: https://bugzilla.redhat.com/show_bug.cgi?id=1533176 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515653559-21047-356 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1839:</h3> <pre> Summary: mock_runner.sh broken on FC27 because of GDBM import issues Key: OVIRT-1839 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1839 Project: oVirt - virtualization made easy Issue Type: Outage Components: mock_runner Reporter: Barak Korren Assignee: infra Priority: High</pre> <p>Unit tests for ‘{{mock_runner.sh}}’ Python code have shown us that it now fails with errors while importing the ‘{{gdbm}}’ package.</p> <p>It seems the latest ‘{{gdbm}}’ package in Fedora (1.14-1) was changes in a way that is incompatible with its Python bindings. The previous version (1.13-3) seems to work just fine.</p> <p>A bug was reported to the Fedora project: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1533176">https://bugzilla.redhat.com/show_bug.cgi?id=1533176</a></p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515653559-21047-356--

1 0

[JIRA] (OVIRT-1839) mock_runner.sh broken on FC27 because of GDBM import issues
by Barak Korren (oVirt JIRA) 11 Jan '18

11 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1839?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1839: -------------------------------- Epic Link: OVIRT-400 > mock_runner.sh broken on FC27 because of GDBM import issues > ----------------------------------------------------------- > > Key: OVIRT-1839 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1839 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: fedora, gdbm > > Unit tests for '{{mock_runner.sh}}' Python code have shown us that it now fails with errors while importing the '{{gdbm}}' package. > It seems the latest '{{gdbm}}' package in Fedora (1.14-1) was changes in a way that is incompatible with its Python bindings. The previous version (1.13-3) seems to work just fine. > A bug was reported to the Fedora project: > https://bugzilla.redhat.com/show_bug.cgi?id=1533176 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc26-x86_64 #536
by jenkins＠jenkins.phx.ovirt.org 11 Jan '18

11 Jan '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc26-x86_64…> Changes: [Barak Korren] Add fc27/s390x build jobs for ovirt-host [Barak Korren] Skip 'pusher.py' when jobs are triggered manually ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc26-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 fd03fa52a1e8bc9b4c687967ec3909b51b8b1238 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f fd03fa52a1e8bc9b4c687967ec3909b51b8b1238 Commit message: "Skip 'pusher.py' when jobs are triggered manually" > git rev-list ea8121495c2217b967a7c3b320fb69bec5bae5c9 # timeout=10 [system-sync_mirrors-fedora-updates-fc26-x86_64] $ /bin/bash -xe /tmp/jenkins3175248313381152073.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc26 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 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1039, in _getFile raise e yum.Errors.NoMoreMirrorsRepoError: failure: repodata/repomd.xml from fedora-updates-fc26: [Errno 256] No more mirrors to try. http://mirror.cc.vt.edu/pub/fedora/linux/updates/26/x86_64/repodata/repomd.…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://fedora.mirror.constant.com/fedora/linux/updates/26/x86_64/repodata/…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirrors.rit.edu/fedora/fedora/linux/updates/26/x86_64/repodata/repo…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.math.princeton.edu/pub/fedora/linux/updates/26/x86_64/repodat…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://pubmirror2.math.uh.edu/fedora-buffet/fedora/linux/updates/26/x86_64…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.cs.princeton.edu/pub/mirrors/fedora/linux/updates/26/x86_64/r…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.cs.pitt.edu/fedora/linux/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://download-ib01.fedoraproject.org/pub/fedora/linux/updates/26/x86_64/…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirror.steadfast.net/fedora/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://fedora.mirror.lstn.net/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirror.mrjester.net/fedora/linux/updates/26/x86_64/repodata/repomd.…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirror.us-midwest-1.nexcess.net/fedora/updates/26/x86_64/repodata/r…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://fedora.mirrors.pair.com/linux/updates/26/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://fedora.mirrors.pair.com/linux/updates/26/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds') http://mirror.uoregon.edu/fedora/linux/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.web-ster.com/fedora/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.metrocast.net/fedora/linux/updates/26/x86_64/repodata/repomd.…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirror.umd.edu/fedora/linux/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://linux.mirrors.es.net/fedora/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://ftp.usf.edu/pub/fedora/linux/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirrors.mit.edu/fedora/linux/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirrors.kernel.org/fedora/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirror.chpc.utah.edu/pub/fedora/linux/updates/26/x86_64/repodata/re…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.sjc02.svwh.net/fedora/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirrors.xmission.com/fedora/linux/updates/26/x86_64/repodata/repomd…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirror.vcu.edu/pub/gnu+linux/fedora/updates/26/x86_64/repodata/repo…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.liberty.edu/mirror/fedora/linux/updates/26/x86_64/repodata/re…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.cogentco.com/pub/linux/fedora/linux/updates/26/x86_64/repodat…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.utexas.edu/fedora/linux/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirrors.cat.pdx.edu/fedora/linux/updates/26/x86_64/repodata/repomd.…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirrors.tummy.com/pub/fedora.redhat.com/fedora/linux/updates/26/x86_…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://dl.fedoraproject.org/pub/fedora/linux/updates/26/x86_64/repodata/re…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://fedora.bhs.mirrors.ovh.net/linux/updates/26/x86_64/repodata/repomd.x…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://muug.ca/mirror/fedora/linux/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://fedora.mirror.iweb.com/linux/updates/26/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 https://mirror.csclub.uwaterloo.ca/fedora/linux/updates/26/x86_64/repodata/…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirror.its.dal.ca/pub/fedora/linux/updates/26/x86_64/repodata/repomd…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirrors.syringanetworks.net/fedora/linux/updates/26/x86_64/repodata/…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 http://mirrors.oit.uci.edu/fedora/linux/updates/26/x86_64/repodata/repomd.x…: [Errno -1] repomd.xml does not match metalink for fedora-updates-fc26 Build step 'Execute shell' marked build as failure

1 1

oVirt infra weekly meeting notes 10.01.2018
by Evgheni Dereveanchin 10 Jan '18

10 Jan '18

Hi everyone, This week was mostly focused on security patching (tracked in OVIRT-1828 <https://ovirt-jira.atlassian.net/browse/OVIRT-1828>), here are some highlights: - PHX engine patched - Jenkins master patched - Jenkins slave mirror snapshots changed to ones containing CVE patches - Resources, www, stats, graphite patched - Hosts need BIOS updates to get IBRS CPU support, verified on ovirt-srv17 - Gerrit does not boot with newest kernel - had to roll back OVIRT-1838 <https://ovirt-jira.atlassian.net/browse/OVIRT-1838> -- Regards, Evgheni Dereveanchin

1 0

[JIRA] (OVIRT-1838) analyze why Gerrit failed to boot with newest kernel
by Evgheni Dereveanchin (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515594748-22637-105 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1838?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1838: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > analyze why Gerrit failed to boot with newest kernel > ---------------------------------------------------- > > Key: OVIRT-1838 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1838 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Gerrit/git > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The security kernel update caused boot failures. Opening ticket to investigate the reason as we're effectively still not protected from spectre/meltdown on this system. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515594748-22637-105 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1838?page=com.atlassian.jira.… ]</pre> <h3>Evgheni Dereveanchin reassigned OVIRT-1838:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>analyze why Gerrit failed to boot with newest kernel</h3> <pre> Key: OVIRT-1838 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1838 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git Reporter: Evgheni Dereveanchin Assignee: Evgheni Dereveanchin</pre> <p>The security kernel update caused boot failures. Opening ticket to investigate the reason as we're effectively still not protected from spectre/meltdown on this system.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515594748-22637-105--

1 0

[JIRA] (OVIRT-1838) analyze why Gerrit failed to boot with newest kernel
by Evgheni Dereveanchin (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515594735-19054-144 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1838: ------------------------------------------- Summary: analyze why Gerrit failed to boot with newest kernel Key: OVIRT-1838 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1838 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git Reporter: Evgheni Dereveanchin Assignee: infra The security kernel update caused boot failures. Opening ticket to investigate the reason as we're effectively still not protected from spectre/meltdown on this system. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515594735-19054-144 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1838:</h3> <pre> Summary: analyze why Gerrit failed to boot with newest kernel Key: OVIRT-1838 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1838 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git Reporter: Evgheni Dereveanchin Assignee: infra</pre> <p>The security kernel update caused boot failures. Opening ticket to investigate the reason as we're effectively still not protected from spectre/meltdown on this system.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515594735-19054-144--

1 0

[vdsm][tag][master] Vdsm tagged: v4.20.12
by Francesco Romani 10 Jan '18

10 Jan '18

Hi infra, we have a new Vdsm tag on branch master for oVirt 4.2.1: tag v4.20.12 Tagger: Francesco Romani <fromani(a)redhat.com> Date: Wed Jan 10 13:45:01 2018 +0100 Vdsm 4.20.12 for oVirt 4.2.1 RC 2 commit 122953f3f160b3c23510e4e151ea5d55c616186e +++ NOTE ABOUT BRANCHING: * We are merging again patches targeted for 4.2.1 on master * We don't yet have plans to branch out ovirt-4.2 from master. Following the usual Vdsm habit, we will branch out late, *after* Engine does. Bests, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

1 0

[CQ]: 84331,15 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 10 Jan '18

10 Jan '18

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

1 0

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

10 Jan '18

------=_Part_7_1526834229.1515580205784 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build Number: 510 Build Status: Failure Triggered By: Started by user Lev Veyde ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #510 [Barak Korren] Re-factored usrc.py internals [Barak Korren] Add automerge functionality to pusher.py [Ryan Barry] Bump version ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_7_1526834229.1515580205784--

1 1

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 131 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Jan '18

10 Jan '18

------=_Part_5_1926236285.1515579399426 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-… Build Number: 131 Build Status: Failure Triggered By: Started by user Lev Veyde ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #131 [Barak Korren] Add vdsm build jobs for fc27/s390x [Barak Korren] Improve logging for usrc.py and pusher.py [Barak Korren] Add s390x/fc27 build for ioprocess [Evgheni Dereveanchin] Update slave repos to point to the latest snapshot [Barak Korren] Make pusher.py accept Git refs in addition to hash [Barak Korren] Replace older scripts with usrc.py and pusher.py [Barak Korren] Re-factored usrc.py internals [Barak Korren] Add automerge functionality to pusher.py [Yuval Turgeman] automation: view install log in console ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_5_1926236285.1515579399426--

1 1

[JIRA] (OVIRT-1837) Make deployment to 'tested' run asynchrnously with the '*-tester' jobs
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1837?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1837: ----------------------------------- Assignee: Barak Korren (was: infra) > Make deployment to 'tested' run asynchrnously with the '*-tester' jobs > ---------------------------------------------------------------------- > > Key: OVIRT-1837 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1837 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > The 'deploy-to_*_tested' job is triggered by the '*-change-queue-tester' job which then waits for it to finish. > Since the 'tested' repo can get big, the 'deploy-to_*_tested' job can end up taking a long time. This in turn means the next run of the '*-change-queue-tester' job gets delayed by a long time. > We should change things so that the '*-change-queue-tester' job no longer waits for the 'deploy-to_*_tested' job to finish -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1837) Make deployment to 'tested' run asynchrnously with the '*-tester' jobs
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515582610-26838-193 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1837?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1837: -------------------------------- Summary: Make deployment to 'tested' run asynchrnously with the '*-tester' jobs (was: Make deployment to 'teste' run asynchrnously with the '*-tester' jobs) > Make deployment to 'tested' run asynchrnously with the '*-tester' jobs > ---------------------------------------------------------------------- > > Key: OVIRT-1837 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1837 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Priority: High > > The 'deploy-to_*_tested' job is triggered by the '*-change-queue-tester' job which then waits for it to finish. > Since the 'tested' repo can get big, the 'deploy-to_*_tested' job can end up taking a long time. This in turn means the next run of the '*-change-queue-tester' job gets delayed by a long time. > We should change things so that the '*-change-queue-tester' job no longer waits for the 'deploy-to_*_tested' job to finish -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515582610-26838-193 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1837?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1837:</h3> <pre>Summary: Make deployment to 'tested' run asynchrnously with the '*-tester' jobs (was: Make deployment to 'teste' run asynchrnously with the '*-tester' jobs)</pre> <blockquote><h3>Make deployment to ‘tested’ run asynchrnously with the ‘*-tester’ jobs</h3> <pre> Key: OVIRT-1837 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1837 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Change Queue Reporter: Barak Korren Assignee: infra Priority: High</pre> <p>The ‘deploy-to_*_tested’ job is triggered by the ‘*-change-queue-tester’ job which then waits for it to finish. Since the ‘tested’ repo can get big, the ‘deploy-to_*_tested’ job can end up taking a long time. This in turn means the next run of the ‘*-change-queue-tester’ job gets delayed by a long time. We should change things so that the ‘*-change-queue-tester’ job no longer waits for the ‘deploy-to_*_tested’ job to finish</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515582610-26838-193--

1 0

[JIRA] (OVIRT-1837) Make deployment to 'teste' run asynchrnously with the '*-tester' jobs
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515582586-23700-294 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1837: ----------------------------------- Summary: Make deployment to 'teste' run asynchrnously with the '*-tester' jobs Key: OVIRT-1837 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1837 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Change Queue Reporter: Barak Korren Assignee: infra Priority: High The 'deploy-to_*_tested' job is triggered by the '*-change-queue-tester' job which then waits for it to finish. Since the 'tested' repo can get big, the 'deploy-to_*_tested' job can end up taking a long time. This in turn means the next run of the '*-change-queue-tester' job gets delayed by a long time. We should change things so that the '*-change-queue-tester' job no longer waits for the 'deploy-to_*_tested' job to finish -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515582586-23700-294 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1837:</h3> <pre> Summary: Make deployment to 'teste' run asynchrnously with the '*-tester' jobs Key: OVIRT-1837 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1837 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Change Queue Reporter: Barak Korren Assignee: infra Priority: High</pre> <p>The ‘deploy-to_*_tested’ job is triggered by the ‘*-change-queue-tester’ job which then waits for it to finish.</p> <p>Since the ‘tested’ repo can get big, the ‘deploy-to_*_tested’ job can end up taking a long time. This in turn means the next run of the ‘*-change-queue-tester’ job gets delayed by a long time.</p> <p>We should change things so that the ‘*-change-queue-tester’ job no longer waits for the ‘deploy-to_*_tested’ job to finish</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515582586-23700-294--

1 0

[JIRA] (OVIRT-1837) Make deployment to 'teste' run asynchrnously with the '*-tester' jobs
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1837?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1837: -------------------------------- Epic Link: OVIRT-400 > Make deployment to 'teste' run asynchrnously with the '*-tester' jobs > --------------------------------------------------------------------- > > Key: OVIRT-1837 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1837 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Priority: High > > The 'deploy-to_*_tested' job is triggered by the '*-change-queue-tester' job which then waits for it to finish. > Since the 'tested' repo can get big, the 'deploy-to_*_tested' job can end up taking a long time. This in turn means the next run of the '*-change-queue-tester' job gets delayed by a long time. > We should change things so that the '*-change-queue-tester' job no longer waits for the 'deploy-to_*_tested' job to finish -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1689) Improve error messages in STDCI environment variable handling
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515574161-11214-315 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1689?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1689: -------------------------------- Component/s: (was: oVirt CI) mock_runner > Improve error messages in STDCI environment variable handling > ------------------------------------------------------------- > > Key: OVIRT-1689 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1689 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Daniel Belenky > Assignee: infra > > * All references to things like 'xdg-home' need to be replaced with specifications of actual paths, as users are not expected to know what XDG is. > * Accurate indication of what is missing from which file and what can be done to fix it need to be given in all error messages. > * When variable/key names are given in error messages, they need to be quoted for clarity. > * Edge cases like for example an existing but empty secrets file and a missing 'secrets_data' key need to be handled better, with clear error messages > * Error message when a requested env var is missing needs to be improved to tell the user what to do. Current message can be very confusing when trying to use 'mock_runner.sh' for the 'jenkins' repo for example. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515574161-11214-315 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1689?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1689:</h3> <pre> Component/s: (was: oVirt CI) mock_runner</pre> <blockquote><h3>Improve error messages in STDCI environment variable handling</h3> <pre> Key: OVIRT-1689 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1689 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Daniel Belenky Assignee: infra</pre> <ul><li><p>All references to things like ‘xdg-home’ need to be replaced with specifications of actual paths, as users are not expected to know what XDG is.</p></li> <li><p>Accurate indication of what is missing from which file and what can be done to fix it need to be given in all error messages.</p></li> <li><p>When variable/key names are given in error messages, they need to be quoted for clarity.</p></li> <li><p>Edge cases like for example an existing but empty secrets file and a missing ‘secrets_data’ key need to be handled better, with clear error messages</p></li> <li><p>Error message when a requested env var is missing needs to be improved to tell the user what to do. Current message can be very confusing when trying to use ‘mock_runner.sh’ for the ‘jenkins’ repo for example.</p></li></ul></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515574161-11214-315--

1 0

[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1690: -------------------------------- Component/s: (was: oVirt CI) CI client projects > Add CI for groovy/pipeline code in 'jenkins' repo > ------------------------------------------------- > > Key: OVIRT-1690 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > Labels: groovy, jenkins > > We don't have any CI for Groovy code currently. > At the very least we need to check that the code compiles, this is a bit harder then it sounds because in order to test compilation for piepline code we need to mock out things like the '{{NonCPS}}' decorator which is not supported by the standard Groovy compiler. > Ideally we can also ass support for a full test suit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1717: -------------------------------- Component/s: (was: oVirt CI) Change Queue > When a component build passes OST, tag its git hash > --------------------------------------------------- > > Key: OVIRT-1717 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: danken > Assignee: infra > Labels: change-queue, standard-ci > > Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1732: -------------------------------- Issue Type: Improvement (was: Bug) Priority: Medium (was: High) > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1732: -------------------------------- Component/s: (was: oVirt CI) pusher.py > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1734: -------------------------------- Component/s: Standard CI (Freestyle) Staging infra CI client projects > Add CI jobs to test slaves on staging engine > -------------------------------------------- > > Key: OVIRT-1734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1734 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects, Jenkins Slaves, Staging infra, Standard CI (Freestyle) > Reporter: Barak Korren > Assignee: infra > Labels: staging > > After the staging engine was installed, several VMs were created on it and added as slaves to the staging Jenkins. > We need to add some jobs that will take advantage on those slaves so we can tell if they are working properly. > The should probably just add CI jobs for the 'jenkins' repo. That repo is already configured to run some jobs on the staging Jenkins and is mostly maintained by our team, so and issues there will be visible to us. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1734: -------------------------------- Component/s: (was: oVirt Infra) (was: oVirt CI) Jenkins Slaves > Add CI jobs to test slaves on staging engine > -------------------------------------------- > > Key: OVIRT-1734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1734 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: staging > > After the staging engine was installed, several VMs were created on it and added as slaves to the staging Jenkins. > We need to add some jobs that will take advantage on those slaves so we can tell if they are working properly. > The should probably just add CI jobs for the 'jenkins' repo. That repo is already configured to run some jobs on the staging Jenkins and is mostly maintained by our team, so and issues there will be visible to us. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1739?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1739: -------------------------------- Component/s: (was: oVirt CI) STDCI DSL Standard CI (Pipelines) Standard CI (Freestyle) > Unified code owners mechanism between Gerrit and GitHub > ------------------------------------------------------- > > Key: OVIRT-1739 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, GitHub, Standard CI (Freestyle), Standard CI (Pipelines), STDCI DSL > Reporter: Barak Korren > Assignee: infra > Labels: gerrit, github, reviewers, standard-ci > > "Code owners" is the mechanism that automatically assigns reviewers to new code patches. > In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165). > GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners > We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Component/s: OST Manual job > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST Manual job, Standard CI (Freestyle) > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Component/s: (was: oVirt CI) Standard CI (Freestyle) > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Freestyle) > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1745) Make upstream source collection and polling code usable for pipelines
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515572840-15436-331 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1745: -------------------------------- Component/s: (was: oVirt CI) usrc.py pusher.py > Make upstream source collection and polling code usable for pipelines > --------------------------------------------------------------------- > > Key: OVIRT-1745 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: pusher.py, usrc.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, upstream-source-collector > > The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because: > # We support having 'jenkins' repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main 'jenkins' repo in gerrit.ovirt.org > # This creates a situation where in order to get the STDCI code we need to run the upstream sources code > # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code > # To solve this issue we simply embedded the upstream sources code into the job code by using '{{#include}}' in JJB rather then running it as a stand-alone script. > # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515572840-15436-331 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1745:</h3> <pre> Component/s: (was: oVirt CI) usrc.py pusher.py</pre> <blockquote><h3>Make upstream source collection and polling code usable for pipelines</h3> <pre> Key: OVIRT-1745 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 Project: oVirt - virtualization made easy Issue Type: New Feature Components: pusher.py, usrc.py Reporter: Barak Korren Assignee: infra Labels: poll-upstream-sources, upstream-source-collector</pre> <p>The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because: # We support having ‘jenkins’ repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main ‘jenkins’ repo in gerrit.ovirt.org # This creates a situation where in order to get the STDCI code we need to run the upstream sources code # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code # To solve this issue we simply embedded the upstream sources code into the job code by using ‘{{#include}}’ in JJB rather then running it as a stand-alone script. # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515572840-15436-331--

1 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1759: -------------------------------- Component/s: (was: oVirt CI) Gerrit/git Change Queue > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1770) Build on fedora 26 fails, accessing console log extremely slow
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1770: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Build on fedora 26 fails, accessing console log extremely slow > -------------------------------------------------------------- > > Key: OVIRT-1770 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > Labels: jenkins > > I wait forever for this url: > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > here example: > $ time curl > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > > /dev/null > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- > 23562 > real 0m22.107s > user 0m0.005s > sys 0m0.009s > Can we fix to be less then a second? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1770) Build on fedora 26 fails, accessing console log extremely slow
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515572133-16023-272 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1770: -------------------------------- Component/s: (was: oVirt CI) Jenkins Master > Build on fedora 26 fails, accessing console log extremely slow > -------------------------------------------------------------- > > Key: OVIRT-1770 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Nir Soffer > Assignee: infra > Labels: jenkins > > I wait forever for this url: > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > here example: > $ time curl > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > > /dev/null > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- > 23562 > real 0m22.107s > user 0m0.005s > sys 0m0.009s > Can we fix to be less then a second? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515572133-16023-272 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1770:</h3> <pre> Component/s: (was: oVirt CI) Jenkins Master</pre> <blockquote><h3>Build on fedora 26 fails, accessing console log extremely slow</h3> <pre> Key: OVIRT-1770 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Nir Soffer Assignee: infra Labels: jenkins</pre> <p>I wait forever for this url: <a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a> here example: $ time curl <a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a></p> <blockquote><p>/dev/null</p></blockquote> <pre>% Total % Received % Xferd Average Speed Time Time Time</pre> <p>Current</p> <pre>Dload Upload Total Spent Left</pre> <p>Speed 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- 23562 real 0m22.107s user 0m0.005s sys 0m0.009s Can we fix to be less then a second?</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515572133-16023-272--

1 0

[JIRA] (OVIRT-1774) Upstream source collector can fail to push on multi-branch projects
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1774?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1774: -------------------------------- Component/s: (was: oVirt CI) pusher.py > Upstream source collector can fail to push on multi-branch projects > ------------------------------------------------------------------- > > Key: OVIRT-1774 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1774 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, upstream-source-collector > > When the upstream source collection code looks for similar patches in order to avoid pushing a new patch, it lookes for patches that contain the same change to the '{{upstream-sources.yaml}}' file, regardless of the branch they may belong to. > The code currently ignores the possibility that similar changes might be required for different branches, in which case different patches may need to be pushed. > The way of detecting similar patches should be changed so that either the branch name is included in the checksum that are used to identify a patch, or the query is limited to patches of the branch being handled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1781) ci failure due to no space on slave?
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1781: -------------------------------- Component/s: (was: oVirt CI) Jenkins Slaves > ci failure due to no space on slave? > ------------------------------------ > > Key: OVIRT-1781 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves > Reporter: danken > Assignee: infra > Priority: High > Labels: vdsm > Fix For: OVIRT-INFRA-DEC-2017 > > > Exception when executing the batch command : no workspace from node > hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is > computer hudson.slaves.SlaveComputer@695d3d3c and has channel null > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1782) Make sure all VDSM build dependencies for FC27 are met.
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1782?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1782: -------------------------------- Component/s: (was: oVirt CI) CI client projects > Make sure all VDSM build dependencies for FC27 are met. > ------------------------------------------------------- > > Key: OVIRT-1782 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1782 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > Labels: vdsm > > There had been attempts recently to make VDSM build on FC27. > Those attempts were met with mixed success as issues kept surfacing. > Fro now all the FC27 jobs for VDSM had been disabled. > This ticket is for racking work of debugging issues to re-enable the jobs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1836) Optimize options normalization methods in stdci_dsl
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1836?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1836: -------------------------------- Component/s: (was: oVirt CI) STDCI DSL > Optimize options normalization methods in stdci_dsl > --------------------------------------------------- > > Key: OVIRT-1836 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner. > We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away. > Since runners and pipelines care about different sets of options, we need to split the options handling functions. > This will enable us to compose much more efficient pipelines in the API. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1817) package included in .packages file, missing in check-patch.sh - caching issue?
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515571559-19030-310 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1817?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1817: -------------------------------- Component/s: (was: oVirt CI) mock_runner > package included in .packages file, missing in check-patch.sh - caching issue? > ------------------------------------------------------------------------------ > > Key: OVIRT-1817 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1817 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Nir Soffer > Assignee: infra > Fix For: OVIRT-INFRA-DEC-2017 > > > I added 2 packages to ovirt-imageio packages files: > https://gerrit.ovirt.org/#/c/85639/ > The next patch using these packages > https://gerrit.ovirt.org/#/c/85245/ > fail to import the package on some slaves: > *00:02:34.093* ==================================== ERRORS > ====================================*00:02:34.093* > ____________________ ERROR collecting test/qemuimg_test.py > _____________________*00:02:34.093* ImportError while importing test > module '/home/jenkins/workspace/ovirt-imageio_master_check-patch-el7-x86_64/ovirt-imageio/common/test/qemuimg_test.py'.*00:02:34.094* > Hint: make sure your test modules/packages have valid Python > names.*00:02:34.094* Traceback:*00:02:34.094* test/qemuimg_test.py:16: > in <module>*00:02:34.094* from ovirt_imageio_common import > qemuimg*00:02:34.094* ovirt_imageio_common/qemuimg.py:11: in > <module>*00:02:34.094* from . compat import > subprocess*00:02:34.095* ovirt_imageio_common/compat.py:12: in > <module>*00:02:34.095* import subprocess32 as subprocess # NOQA: > F401 (unused import)*00:02:34.095* E ImportError: No module named > subprocess32*00:02:34.095* !!!!!!!!!!!!!!!!!!! Interrupted: 1 errors > during collection !!!!!!!!!!!!!!!!!!!!*00:02:34.096* > =========================== 1 error in 1.06 seconds > ============================ > Do we have a way to invalidate mock cache manually? > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515571559-19030-310 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1817?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1817:</h3> <pre> Component/s: (was: oVirt CI) mock_runner</pre> <blockquote><h3>package included in .packages file, missing in check-patch.sh – caching issue?</h3> <pre> Key: OVIRT-1817 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1817 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Nir Soffer Assignee: infra Fix For: OVIRT-INFRA-DEC-2017</pre> <p>I added 2 packages to ovirt-imageio packages files: <a href="https://gerrit.ovirt.org/#/c/85639/">https://gerrit.ovirt.org/#/c/85639/</a> The next patch using these packages <a href="https://gerrit.ovirt.org/#/c/85245/">https://gerrit.ovirt.org/#/c/85245/</a> fail to import the package on some slaves: <strong>00:02:34.093</strong> ==================================== ERRORS ====================================*00:02:34.093* <em>_________________</em>_ ERROR collecting test/qemuimg_test.py _____________________*00:02:34.093* ImportError while importing test module '/home/jenkins/workspace/ovirt-imageio_master_check-patch-el7-x86_64/ovirt-imageio/common/test/qemuimg_test.py'.*00:02:34.094* Hint: make sure your test modules/packages have valid Python names.*00:02:34.094* Traceback:*00:02:34.094* test/qemuimg_test.py:16: in <module>*00:02:34.094* from ovirt_imageio_common import qemuimg*00:02:34.094* ovirt_imageio_common/qemuimg.py:11: in <module>*00:02:34.094* from . compat import subprocess*00:02:34.095* ovirt_imageio_common/compat.py:12: in <module>*00:02:34.095* import subprocess32 as subprocess # NOQA: F401 (unused import)*00:02:34.095* E ImportError: No module named subprocess32*00:02:34.095* !!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!*00:02:34.096* =========================== 1 error in 1.06 seconds ============================ Do we have a way to invalidate mock cache manually? Nir</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515571559-19030-310--

1 0

[JIRA] (OVIRT-1818) ioprocess build fail on ppc64le
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1818?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1818: -------------------------------- Component/s: (was: oVirt CI) mock_runner > ioprocess build fail on ppc64le > ------------------------------- > > Key: OVIRT-1818 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1818 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Nir Soffer > Assignee: Barak Korren > Labels: ppc64le, standard-ci > > The new builds for ppc64le fail with the errors below. > 1. > http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc26-ppc64le/1/co… > *00:00:42.499* ERROR: Command failed: *00:00:42.500* # /usr/bin/yum > --installroot /var/lib/mock/fedora-26-ppc64le-881f89337ffa51754418efa2ad261881-16706/root/ > --releasever 26 install @buildsys-build autoconf automake git > glib2-devel python-pip python-six python-subprocess32 python2-devel > python3-devel python3-six util-linux yajl-devel > --setopt=tsflags=nocontexts*00:00:42.500* Failed to set locale, > defaulting to C*00:00:42.500* No package git available.*00:00:42.501* > No package glib2-devel available.*00:00:42.501* No package > python-subprocess32 available.*00:00:42.501* No package python2-devel > available.*00:00:42.501* No package python3-devel > available.*00:00:42.501* No package util-linux > available.*00:00:42.501* No package yajl-devel available. > 2. > http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc27-ppc64le/1/co… > *00:00:18.335* + > /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs/mock_runner.sh > --patch-only --mock-confs-dir > /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs > --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/std_ci_secrets.yaml > --try-proxy --try-mirrors > http://mirrors.phx.ovirt.org/repos/yum/all_latest.json > 'fc27.*ppc64le'*00:00:18.347* Unable to find mock env > fc27.*ppc64le*00:00:18.351* Collecting mock logs*00:00:18.352* mv: > missing destination file operand after 'exported-artifacts/mock_logs' > 3. > http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fcraw-ppc64le/1/c… > *00:00:26.701* + > /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs/mock_runner.sh > --patch-only --mock-confs-dir > /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs > --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/std_ci_secrets.yaml > --try-proxy --try-mirrors > http://mirrors.phx.ovirt.org/repos/yum/all_latest.json > 'fcraw.*ppc64le'*00:00:26.702* Unable to find mock env > fcraw.*ppc64le*00:00:26.703* Collecting mock logs > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1831) Make `global-setup.sh` check if packages are installed before trying to install them
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1831?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1831: -------------------------------- Component/s: (was: oVirt CI) Jenkins Slaves > Make `global-setup.sh` check if packages are installed before trying to install them > ------------------------------------------------------------------------------------ > > Key: OVIRT-1831 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1831 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > The way '{{global-setup.sh}}' works currently is that it tries to install all the packages it needs in a single yum command and then runs in a loop and checks if the packages were installed properly. > If the packages are already installed this takes a negligible amount of time on CentOS slaves, but on Fedora it seems to take much longer and as much as 2 minutes. > We should try to make '{{global-setup.sh}}' faster by making it not try to install packages before checking if they are there, but instead check first and only try to install the missing ones. > Note that if we'll install multiple packages in a single command, we'll still need to verify they were properly installed after the yum/dnf command finishes. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1836) Optimize options normalization methods in stdci_dsl
by Daniel Belenky (oVirt JIRA) 10 Jan '18

10 Jan '18

Daniel Belenky created OVIRT-1836: ------------------------------------- Summary: Optimize options normalization methods in stdci_dsl Key: OVIRT-1836 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Daniel Belenky Assignee: infra Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner. We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away. Since runners and pipelines care about different sets of options, we need to split the options handling functions. This will enable us to compose much more efficient pipelines in the API. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1836) Optimize options normalization methods in stdci_dsl
by Daniel Belenky (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515571288-12694-334 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1836?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1836: ---------------------------------- Epic Link: OVIRT-400 > Optimize options normalization methods in stdci_dsl > --------------------------------------------------- > > Key: OVIRT-1836 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: infra > > Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner. > We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away. > Since runners and pipelines care about different sets of options, we need to split the options handling functions. > This will enable us to compose much more efficient pipelines in the API. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515571288-12694-334 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1836?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1836:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Optimize options normalization methods in stdci_dsl</h3> <pre> Key: OVIRT-1836 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Daniel Belenky Assignee: infra</pre> <p>Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner. We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away. Since runners and pipelines care about different sets of options, we need to split the options handling functions. This will enable us to compose much more efficient pipelines in the API.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515571288-12694-334--

1 0

[JIRA] (OVIRT-1835) Create an automated update mechanism for slaves
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1835?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1835: -------------------------------- Component/s: (was: oVirt CI) Jenkins Slaves > Create an automated update mechanism for slaves > ----------------------------------------------- > > Key: OVIRT-1835 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: slaves > > While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by '{{global-setup.sh}}'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves. > Some things we'd like such a mechanism to provide: > * Require a minimal amount of manual work (Best case scenario - nothing more then merging a repository update patch would be needed). > * Test updated slaves before putting them back to production use > * Allow rolling back failed updates -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1835) Create an automated update mechanism for slaves
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515569110-24537-319 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1835: ----------------------------------- Summary: Create an automated update mechanism for slaves Key: OVIRT-1835 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by '{{global-setup.sh}}'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves. Some things we'd like such a mechanism to provide: * Require a minimal amount of manual work (Best case scenario - nothing more then merging a repository update patch would be needed). * Test updated slaves before putting them back to production use * Allow rolling back failed updates -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515569110-24537-319 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1835:</h3> <pre> Summary: Create an automated update mechanism for slaves Key: OVIRT-1835 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra</pre> <p>While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by '{{global-setup.sh}}'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves.</p> <p>Some things we'd like such a mechanism to provide:</p> <ul><li><p>Require a minimal amount of manual work (Best case scenario – nothing more then merging a repository update patch would be needed).</p></li> <li><p>Test updated slaves before putting them back to production use</p></li> <li><p>Allow rolling back failed updates</p></li></ul> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515569110-24537-319--

1 0

[JIRA] (OVIRT-1835) Create an automated update mechanism for slaves
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1835?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1835: -------------------------------- Epic Link: OVIRT-403 > Create an automated update mechanism for slaves > ----------------------------------------------- > > Key: OVIRT-1835 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: slaves > > While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by '{{global-setup.sh}}'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves. > Some things we'd like such a mechanism to provide: > * Require a minimal amount of manual work (Best case scenario - nothing more then merging a repository update patch would be needed). > * Test updated slaves before putting them back to production use > * Allow rolling back failed updates -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

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

10 Jan '18

------=_Part_163_1404145963.1515480066524 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build Number: 400 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #400 [Evgheni Dereveanchin] Update slave repos to point to the latest snapshot [Ryan Barry] Bump version ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_163_1404145963.1515480066524--

1 1

Planned restart of production services
by Evgheni Dereveanchin 10 Jan '18

10 Jan '18

Hi everyone, I will be restarting several production systems within the following hour to apply security updates. The following services may be unreachable for some period of time: - resources.ovirt.org - package repositories - gerrit.ovirt.org - code review - jenkins.ovirt.org - CI master It will not be possible to submit/review patches, clone repositories or run CI jobs during this period. Package repositories will also be unreachable for a short period of time. I will announce you once the maintenance is complete. -- Regards, Evgheni Dereveanchin

1 2

[CQ]: 86106,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 09 Jan '18

09 Jan '18

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

1 0

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Gal Ben Haim (oVirt JIRA) 09 Jan '18

09 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-1834: ------------------------------------- The issue was solved, and we are working on a long-term solution. > Jenkins failure - perhaps bad permissions > ----------------------------------------- > > Key: OVIRT-1834 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests… > *10:53:01* ERROR: Error fetching remote repo 'origin'*10:53:01* > hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at > hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at > hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01* > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at > org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01* > at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at > hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01* > at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01* > at hudson.model.Run.execute(Run.java:1724)*10:53:01* at > hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at > hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01* > at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by: > hudson.plugins.git.GitException: Command "git clean -fdx" returned > status code 1:*10:53:01* stdout: Removing > basic-suite-master/LagoInitFile*10:53:01* Removing > basic-suite-master/extra_sources*10:53:01* Removing > basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing > basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing > basic-suite-master/test_utils/constants.pyc*10:53:01* Removing > basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing > exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01* > Removing mock_script_sid.x4jv1R*10:53:01* Removing > mocker-epel-7-x86_64.el7.cfg*10:53:01* *10:53:01* stderr: warning: > failed to remove .pki/*10:53:01* warning: failed to remove > deployment-basic-suite-master/default/uuid*10:53:01* warning: failed > to remove deployment-basic-suite-master/default/id_rsa > ... > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

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

09 Jan '18

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

1 0

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Shirly Radco (oVirt JIRA) 09 Jan '18

09 Jan '18

This is a multi-part message in MIME format... ------------=_1515507124-10722-151 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.… ] Shirly Radco commented on OVIRT-1834: ------------------------------------- Any update on this? > Jenkins failure - perhaps bad permissions > ----------------------------------------- > > Key: OVIRT-1834 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests… > *10:53:01* ERROR: Error fetching remote repo 'origin'*10:53:01* > hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at > hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at > hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01* > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at > org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01* > at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at > hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01* > at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01* > at hudson.model.Run.execute(Run.java:1724)*10:53:01* at > hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at > hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01* > at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by: > hudson.plugins.git.GitException: Command "git clean -fdx" returned > status code 1:*10:53:01* stdout: Removing > basic-suite-master/LagoInitFile*10:53:01* Removing > basic-suite-master/extra_sources*10:53:01* Removing > basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing > basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing > basic-suite-master/test_utils/constants.pyc*10:53:01* Removing > basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing > exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01* > Removing mock_script_sid.x4jv1R*10:53:01* Removing > mocker-epel-7-x86_64.el7.cfg*10:53:01* *10:53:01* stderr: warning: > failed to remove .pki/*10:53:01* warning: failed to remove > deployment-basic-suite-master/default/uuid*10:53:01* warning: failed > to remove deployment-basic-suite-master/default/id_rsa > ... > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515507124-10722-151 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.… ]</pre> <h3>Shirly Radco commented on OVIRT-1834:</h3> <p>Any update on this?</p> <blockquote><h3>Jenkins failure – perhaps bad permissions</h3> <pre> Key: OVIRT-1834 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> <p><a href="http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests…">http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests…</a> <strong>10:53:01</strong> ERROR: Error fetching remote repo 'origin'*10:53:01* hudson.plugins.git.GitException: Failed to fetch from git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01*</p> <pre>at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at</pre> <p>org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01*</p> <pre>at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at</pre> <p>hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01*</p> <pre>at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01* at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01* at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01* at hudson.model.Run.execute(Run.java:1724)*10:53:01* at</pre> <p>hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01*</p> <pre>at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by:</pre> <p>hudson.plugins.git.GitException: Command “git clean -fdx” returned status code 1:*10:53:01* stdout: Removing basic-suite-master/LagoInitFile*10:53:01* Removing basic-suite-master/extra_sources*10:53:01* Removing basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01* Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01* Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01* Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01* Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing basic-suite-master/test_utils/constants.pyc*10:53:01* Removing basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01* Removing mock_script_sid.x4jv1R*10:53:01* Removing mocker-epel-7-x86_64.el7.cfg*10:53:01* <strong>10:53:01</strong> stderr: warning: failed to remove .pki/*10:53:01* warning: failed to remove deployment-basic-suite-master/default/uuid*10:53:01* warning: failed to remove deployment-basic-suite-master/default/id_rsa … — Didi</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515507124-10722-151--

1 0

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Gal Ben Haim (oVirt JIRA) 09 Jan '18

09 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-1834: ------------------------------------- The lago prefix is created by root inside mock, build http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1984/ was aborted, and the cleanup has not been called (we aware about this issue), and then the next build failed to clean OST repo (with git clean). [~dbelenky(a)redhat.com] is working on a solution for this issue. > Jenkins failure - perhaps bad permissions > ----------------------------------------- > > Key: OVIRT-1834 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests… > *10:53:01* ERROR: Error fetching remote repo 'origin'*10:53:01* > hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at > hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at > hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01* > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at > org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01* > at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at > hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01* > at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01* > at hudson.model.Run.execute(Run.java:1724)*10:53:01* at > hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at > hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01* > at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by: > hudson.plugins.git.GitException: Command "git clean -fdx" returned > status code 1:*10:53:01* stdout: Removing > basic-suite-master/LagoInitFile*10:53:01* Removing > basic-suite-master/extra_sources*10:53:01* Removing > basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing > basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing > basic-suite-master/test_utils/constants.pyc*10:53:01* Removing > basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing > exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01* > Removing mock_script_sid.x4jv1R*10:53:01* Removing > mocker-epel-7-x86_64.el7.cfg*10:53:01* *10:53:01* stderr: warning: > failed to remove .pki/*10:53:01* warning: failed to remove > deployment-basic-suite-master/default/uuid*10:53:01* warning: failed > to remove deployment-basic-suite-master/default/id_rsa > ... > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Yedidyah Bar David (oVirt JIRA) 09 Jan '18

09 Jan '18

Yedidyah Bar David created OVIRT-1834: ----------------------------------------- Summary: Jenkins failure - perhaps bad permissions Key: OVIRT-1834 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests… *10:53:01* ERROR: Error fetching remote repo 'origin'*10:53:01* hudson.plugins.git.GitException: Failed to fetch from git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01* at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01* at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01* at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01* at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01* at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01* at hudson.model.Run.execute(Run.java:1724)*10:53:01* at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01* at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" returned status code 1:*10:53:01* stdout: Removing basic-suite-master/LagoInitFile*10:53:01* Removing basic-suite-master/extra_sources*10:53:01* Removing basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01* Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01* Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01* Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01* Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing basic-suite-master/test_utils/constants.pyc*10:53:01* Removing basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01* Removing mock_script_sid.x4jv1R*10:53:01* Removing mocker-epel-7-x86_64.el7.cfg*10:53:01* *10:53:01* stderr: warning: failed to remove .pki/*10:53:01* warning: failed to remove deployment-basic-suite-master/default/uuid*10:53:01* warning: failed to remove deployment-basic-suite-master/default/id_rsa ... -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0