- Infra - oVirt List Archives

[JIRA] (OVIRT-1820) ioporcess build-artifacts fails on fedora/ppc64le
by Nir Soffer (oVirt JIRA) 27 Dec '17

27 Dec '17

Nir Soffer created OVIRT-1820: --------------------------------- Summary: ioporcess build-artifacts fails on fedora/ppc64le Key: OVIRT-1820 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1820 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra We added recently build-artifacts jobs for ioprocess on fedora/ppc64le. I merge a patch today, and build-artifacts fail: http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc26-ppc64le/… http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc27-ppc64le/… http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fcraw-ppc64le… So it seems that we cannot support fedora on ppc64le now, and we need to remove these jobs. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 85754,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 27 Dec '17

27 Dec '17

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

1 0

[JIRA] (OVIRT-1819) Hanging processes left after mock_runner is being terminated
by Daniel Belenky (oVirt JIRA) 27 Dec '17

27 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1819?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1819: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Hanging processes left after mock_runner is being terminated > ------------------------------------------------------------ > > Key: OVIRT-1819 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1819 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Daniel Belenky > Priority: Highest > > Since mock_runner.sh runs as $user and mock runs as root, mock_runner can't propagate signals to mock process. > Due to the said above, if mock_runner is being terminated, the mock process will be left behind as an orphaned. > Another symptom is subprocesses of user script which are not being killed after users script returns. > We need to trap signals from mock_runner and implement a message pipe between mock_runner and mock to propagate the signals. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1819) Hanging processes left after mock_runner is being terminated
by Daniel Belenky (oVirt JIRA) 27 Dec '17

27 Dec '17

Daniel Belenky created OVIRT-1819: ------------------------------------- Summary: Hanging processes left after mock_runner is being terminated Key: OVIRT-1819 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1819 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra Priority: Highest Since mock_runner.sh runs as $user and mock runs as root, mock_runner can't propagate signals to mock process. Due to the said above, if mock_runner is being terminated, the mock process will be left behind as an orphaned. Another symptom is subprocesses of user script which are not being killed after users script returns. We need to trap signals from mock_runner and implement a message pipe between mock_runner and mock to propagate the signals. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 68408,12 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 27 Dec '17

27 Dec '17

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

1 0

[CQ]: 85734, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Dec '17

27 Dec '17

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

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1118
by jenkins＠jenkins.phx.ovirt.org 27 Dec '17

27 Dec '17

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 e6220a204f13e53150867224f62e4752cad89cd0 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e6220a204f13e53150867224f62e4752cad89cd0 Commit message: "ioprocess: Exclude fc2* ppc64le tests" > git rev-list e6220a204f13e53150867224f62e4752cad89cd0 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2742489996658194381.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7/gen' Build step 'Execute shell' marked build as failure

1 1

Change in stage-stdci1[master]: Another patch for checking automerge
by review＠gerrit-staging.phx.ovirt.org 26 Dec '17

26 Dec '17

>From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/112 to look at the new patch set (#2). Change subject: Another patch for checking automerge ...................................................................... Another patch for checking automerge Patch owner would be bkorren Change-Id: I725721eb11285f0566804b92e3a3a6d05ed59cc1 automerge: yes --- M dummy.txt 1 file changed, 2 insertions(+), 0 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/12/112/2 -- To view, visit https://gerrit-staging.phx.ovirt.org/112 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: I725721eb11285f0566804b92e3a3a6d05ed59cc1 Gerrit-Change-Number: 112 Gerrit-PatchSet: 2 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1116
by jenkins＠jenkins.phx.ovirt.org 26 Dec '17

26 Dec '17

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 ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 Commit message: "add network suite to manaul job suite selector" > git rev-list ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins3621825039595573999.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

[CQ]: 85451,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 26 Dec '17

26 Dec '17

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

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1734: ------------------------------------- [~eedri] no, this specifically talks about jobs for the 'jenkins' repo for testing different platforms where we only have one for now. > 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: oVirt CI, oVirt Infra > 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-1465) Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
by Barak Korren (oVirt JIRA) 26 Dec '17

26 Dec '17

This is a multi-part message in MIME format... ------------=_1514293711-12689-137 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1465: ------------------------------------- [~eedri] no, both instances still use the deploy job. > Run JJB from 'check-merged' of 'jenkins' repo instead of its own job > -------------------------------------------------------------------- > > Key: OVIRT-1465 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, jjb, standard-ci > > Right not we have a custom job for running JJB after patches are merged to the 'jenkins' repo. > Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514293711-12689-137 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1465:</h3> <p>[~eedri] no, both instances still use the deploy job.</p> <blockquote><h3>Run JJB from ‘check-merged’ of ‘jenkins’ repo instead of its own job</h3> <pre> Key: OVIRT-1465 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: jenkins, jjb, standard-ci</pre> <p>Right not we have a custom job for running JJB after patches are merged to the ‘jenkins’ repo. Once we can handle credentials in standard-CI we can move this functionality into the ‘check-merged’ job.</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> ------------=_1514293711-12689-137--

1 0

[JIRA] (OVIRT-1651) Jenkins EL7 slaves configured as Fedora slaves
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1651?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1651: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) doesn't seem to be a real issue, please reopen if you still think something should be done. > Jenkins EL7 slaves configured as Fedora slaves > ---------------------------------------------- > > Key: OVIRT-1651 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1651 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: sbonazzo > Assignee: infra > Priority: Lowest > > This morning I'm seeing jobs failing trying to use DNF instead of YUM on EL7 slaves because of the existence of /etc/dnf directory on EL7 slaves: > Example job:http://jenkins.ovirt.org/job/ovirt-release_4.1_check-patch-el7-x86_64/1… > Example slave: http://jenkins.ovirt.org/computer/vm0085.workers-phx.ovirt.org > println "ls -l /etc/dnf".execute().text > println "cat /etc/os-release".execute().text > Result > total 8 > -rw-r--r--. 1 root root 1562 Sep 16 05:43 dnf.conf > -rw-r--r--. 1 root root 72 Mar 4 2015 dnf.conf.old > drwxr-xr-x. 2 root root 6 Jul 7 2015 plugins > drwxr-xr-x. 2 root root 21 Sep 14 21:57 protected.d > NAME="CentOS Linux" > VERSION="7 (Core)" > ID="centos" > ID_LIKE="rhel fedora" > VERSION_ID="7" > PRETTY_NAME="CentOS Linux 7 (Core)" > ANSI_COLOR="0;31" > CPE_NAME="cpe:/o:centos:centos:7" > HOME_URL="https://www.centos.org/" > BUG_REPORT_URL="https://bugs.centos.org/" > CENTOS_MANTISBT_PROJECT="CentOS-7" > CENTOS_MANTISBT_PROJECT_VERSION="7" > REDHAT_SUPPORT_PRODUCT="centos" > REDHAT_SUPPORT_PRODUCT_VERSION="7" > Please fix slaves configuration. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1239) tracking ticket for supporting multiple organization in GH CR builder plugin
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1239?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1239: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) No need for it anymore due to std-ci V2 > tracking ticket for supporting multiple organization in GH CR builder plugin > ---------------------------------------------------------------------------- > > Key: OVIRT-1239 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1239 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Lowest > > In current implementation credentials can be specified only per server so it's not possible to use different credentials for ovirt and lago projects using same jenkins instance as we do. > During meeting with [~eedri] we decided to evaluate two possible options: > 1) Webhooks to trigger build. From first glance it looks good but not sure if it's solve the problem with credentials. It should be implemented anyway and it's tracked under OVIRT-1142 > 2) Open RFE under GH PR Builder plugin to support this out of the box. > This ticket is opened to track progress on second option. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1527) Make Change-Id clickable
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

This is a multi-part message in MIME format... ------------=_1514292570-19796-118 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1527?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1527: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) If possible, try to reach out to OpenStack to see how they implemented it and if its requires a special plugin. > Make Change-Id clickable > ------------------------ > > Key: OVIRT-1527 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: Evgheni Dereveanchin > Priority: Low > > In openstack's gerrit, e.g. [1], the "Change-Id:" in the commit > message is clickable, and pressing it searches for patches including > it (e.g. in other branches). Might be useful for oVirt too. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514292570-19796-118 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1527?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1527:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <p>If possible, try to reach out to OpenStack to see how they implemented it and if its requires a special plugin.</p> <blockquote><h3>Make Change-Id clickable</h3> <pre> Key: OVIRT-1527 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yedidyah Bar David Assignee: Evgheni Dereveanchin Priority: Low</pre> <p>In openstack's gerrit, e.g. [1], the “Change-Id:” in the commit message is clickable, and pressing it searches for patches including it (e.g. in other branches). Might be useful for oVirt too. [1] <a href="https://review.openstack.org/471802">https://review.openstack.org/471802</a> — 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> ------------=_1514292570-19796-118--

1 0

[JIRA] (OVIRT-1109) Create jobs parameter in manual system tests
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1109?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1109: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) > Create jobs parameter in manual system tests > -------------------------------------------- > > Key: OVIRT-1109 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1109 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > You should do that by adding a dynamic parameter that'll have a groovy script such as: > {code} > import jenkins.model.* > def list = [] > def matchedJobs = Jenkins.instance.items.findAll { job -> > job.name =~ /build-artifacts/ > } > matchedJobs.each { job -> > if (!job.name.contains("archived_for_deletion")) { > list << job.name.split('_')[0] > } > } > return list.unique() > {code} > With the above script you'll have all project names. From the project name and the other parameters you can build any job's name: > {code} > {project}_{ovirt_version}_build-artifacts-{distro}-{arch} > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1113: ----------------------------- Labels: easy_task (was: ) > Automate project Gerrit repo creation > ------------------------------------- > > Key: OVIRT-1113 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Labels: easy_task > > Because the doc is annoying to follow manually, and its easy to automate Gerrit, the API is basically 'ssh'. > Long term if the automation is good we could make this "self service". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1333: ----------------------------- Labels: easy_task (was: ) > Exclude game/desktop packages from mirrors > ------------------------------------------ > > Key: OVIRT-1333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: easy_task > > Our mirrors currently contain full copies of the CentOS and Fedora repos, including many large game and desktop productivity packages. > We should probably clean these packages from the repos to save space and bandwidth. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1465) Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

This is a multi-part message in MIME format... ------------=_1514291743-11828-156 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1465: ---------------------------------- We have this in d/s jenkins already right? > Run JJB from 'check-merged' of 'jenkins' repo instead of its own job > -------------------------------------------------------------------- > > Key: OVIRT-1465 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, jjb, standard-ci > > Right not we have a custom job for running JJB after patches are merged to the 'jenkins' repo. > Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514291743-11828-156 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1465:</h3> <p>We have this in d/s jenkins already right?</p> <blockquote><h3>Run JJB from ‘check-merged’ of ‘jenkins’ repo instead of its own job</h3> <pre> Key: OVIRT-1465 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: jenkins, jjb, standard-ci</pre> <p>Right not we have a custom job for running JJB after patches are merged to the ‘jenkins’ repo. Once we can handle credentials in standard-CI we can move this functionality into the ‘check-merged’ job.</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> ------------=_1514291743-11828-156--

1 0

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

This is a multi-part message in MIME format... ------------=_1514291674-26699-130 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1479: ----------------------------- Resolution: Fixed Status: Done (was: To Do) slaves are now using mirrors, so issue should be fixed. > dnf install in jobs setup scripts fails due to corrupted rpmdb > -------------------------------------------------------------- > > Key: OVIRT-1479 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt Infra > Reporter: Nadav Goldin > Assignee: infra > Labels: rpmdb, standard-ci > > {code} > 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML > 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: BDB1507 Thread died in Berkeley DB library > 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery > 10:24:59 error: cannot open Packages index using db5 - (-30973) > 10:24:59 error: cannot open Packages database in /var/lib/rpm > 10:24:59 Error: Error: rpmdb open failed > 10:24:59 + failed=true > {code} > http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514291674-26699-130 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1479?page=com.atlassian.jira.… ]</pre> <h3>eyal edri updated OVIRT-1479:</h3> <pre>Resolution: Fixed Status: Done (was: To Do)</pre> <p>slaves are now using mirrors, so issue should be fixed.</p> <blockquote><h3>dnf install in jobs setup scripts fails due to corrupted rpmdb</h3> <pre> Key: OVIRT-1479 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt Infra Reporter: Nadav Goldin Assignee: infra Labels: rpmdb, standard-ci</pre> <p>{code} 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: BDB1507 Thread died in Berkeley DB library 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery 10:24:59 error: cannot open Packages index using db5 – (-30973) 10:24:59 error: cannot open Packages database in /var/lib/rpm 10:24:59 Error: Error: rpmdb open failed 10:24:59 + failed=true {code} <a href="http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/…">http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/…</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> ------------=_1514291674-26699-130--

1 0

[JIRA] (OVIRT-1551) Add slaves to staging Jenkins instance
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

This is a multi-part message in MIME format... ------------=_1514291346-16631-179 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1551?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1551: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Add slaves to staging Jenkins instance > -------------------------------------- > > Key: OVIRT-1551 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1551 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, slaves > > We currently have just one slave attached to the staging Jenkins instance. > We need some more, at least one of each slave platform we support so that we can: > # Test jobs running in paralllel > # Test jobs running on different slave platforms. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514291346-16631-179 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1551?page=com.atlassian.jira.… ]</pre> <h3>eyal edri updated OVIRT-1551:</h3> <pre>Resolution: Fixed Status: Done (was: To Do)</pre> <blockquote><h3>Add slaves to staging Jenkins instance</h3> <pre> Key: OVIRT-1551 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1551 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt Infra Reporter: Barak Korren Assignee: infra Labels: jenkins, slaves</pre> <p>We currently have just one slave attached to the staging Jenkins instance. We need some more, at least one of each slave platform we support so that we can: # Test jobs running in paralllel # Test jobs running on different slave platforms.</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> ------------=_1514291346-16631-179--

1 0

[JIRA] (OVIRT-1551) Add slaves to staging Jenkins instance
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1551?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1551: ---------------------------------- [http://jenkins-staging.phx.ovirt.org/] has multiple slaves now, closing. > Add slaves to staging Jenkins instance > -------------------------------------- > > Key: OVIRT-1551 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1551 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, slaves > > We currently have just one slave attached to the staging Jenkins instance. > We need some more, at least one of each slave platform we support so that we can: > # Test jobs running in paralllel > # Test jobs running on different slave platforms. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1658) Potential issue coming to CentOS7 slaves (glibc, missing UTF-8 locale)
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1658?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1658: ---------------------------------- Is it still an issue after a few 7.4.z batches were released? > Potential issue coming to CentOS7 slaves (glibc, missing UTF-8 locale) > ---------------------------------------------------------------------- > > Key: OVIRT-1658 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1658 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Seems there is an issue with locale files in recent CentOS versions, > and we're hitting it in slaves that have been updated recently. > The symptoms are that Jenkins disconnects from the slave and then > refuses to reconnect to it. The agent log in Jenkins shows: > [09/19/17 15:42:56] [SSH] Connection closed. > [09/19/17 15:58:48] [SSH] Opening SSH connection to > vm0002.workers-phx.ovirt.org:22. > [09/19/17 15:58:48] [SSH] WARNING: SSH Host Keys are not being > verified. Man-in-the-middle attacks may be possible against this > connection. > [09/19/17 15:58:48] [SSH] Authentication successful. > SSH connection reports a garbage before a command execution. > Check your .bashrc, .profile, and so on to make sure it is quiet. > The received junk text is as follows: > /etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot > change locale (en_US.utf8): No such file or directory > /etc/profile.d/lang.sh: line 20: warning: setlocale: LC_COLLATE: > cannot change locale (en_US.utf8): No such file or directory > /etc/profile.d/lang.sh: line 23: warning: setlocale: LC_MESSAGES: > cannot change locale (en_US.utf8): No such file or directory > /etc/profile.d/lang.sh: line 26: warning: setlocale: LC_NUMERIC: > cannot change locale (en_US.utf8): No such file or directory > /etc/profile.d/lang.sh: line 29: warning: setlocale: LC_TIME: cannot > change locale (en_US.utf8): No such file or directory > null > [09/19/17 15:58:48] Launch failed - cleaning up connection > [09/19/17 15:58:48] [SSH] Connection closed. > The same locale error messages can also be reproduced on the slave by > running an interactive login from the console or 'su -'. When running > 'locale -a' you can also see the en_US.UTF-8 locale is somehow > missing. > Looking around for this I found the following: > https://github.com/CentOS/sig-cloud-instance-images/issues/71 > I tried downgrading glibc back to the version we had before, but that > did not seem to resolve the issue. Eventually I managed to resolve it > by running 'localedef -i en_US -f UTF-8 en_US.UTF-8' on the slave. > I've seen this happen on 'vm0002.workers-phx.ovirt.org' which is > attached to the staging Jenkins, but I've no reason to believe this > won't start impacting production slaves. > We need to research this further and find out if we need to do > something to prevent this issue from surfacing on production slaves. > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1702) Jenkins STD-CI are running in dirty mock chroots
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1702?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1702: ----------------------------- Resolution: Done Status: Done (was: To Do) please reopen if its still relevant > Jenkins STD-CI are running in dirty mock chroots > ------------------------------------------------ > > Key: OVIRT-1702 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1702 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Example: > http://jenkins.ovirt.org/job/ovirt-wgt_master_check-patch-fc26-x86_64/11/co… > *09:44:06* + ./automation/build-artifacts.sh*09:44:06* + [[ -d > exported-artifacts ]]*09:44:06* + mkdir -p > exported-artifacts*09:44:06* + [[ -d tmp.repos/SOURCES ]]*09:44:06* + > mkdir -p tmp.repos/SOURCES*09:44:06* + git clone > git://anongit.freedesktop.org/spice/spice-nsis*09:44:06* fatal: > destination path 'spice-nsis' already exists and is not an empty > directory. > jobs should run in clean chroots. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > <http://www.teraplan.it/redhat-osd-2017/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1703) vm0152.workers-phx.ovirt.org ran out of file descriptors
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1703?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1703: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > vm0152.workers-phx.ovirt.org ran out of file descriptors > -------------------------------------------------------- > > Key: OVIRT-1703 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1703 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Evgheni Dereveanchin > > Link to the failed job: [http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3161/console|…] > I've opened this ticket to track this issue and see if we see it again sometime. I wasn't able to reboot the slave from the terminal, had to reboot it from the engine. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1712) OST jobs fails on "address already in use"
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1712?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1712: ----------------------------- Status: In Progress (was: To Do) > OST jobs fails on "address already in use" > ------------------------------------------ > > Key: OVIRT-1712 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1712 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Gal Ben Haim > Priority: High > > Evgheni, > Was there any change recently to Lago slaves? > On Fri, Oct 20, 2017 at 11:05 AM, Piotr Kliczewski < > piotr.kliczewski(a)gmail.com> wrote: > > I attempted to run manual OST twice and both failed with below issue. > > Can someone take a look? > > > > Thanks, > > Piotr > > > > 2017-10-20 07:59:12,485::log_utils.py::__exit__::607::ovirtlago.prefix: > > :DEBUG:: > > File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, > > in wrapper > > return func(*args, **kwargs) > > File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line > > 111, in wrapper > > with utils.repo_server_context(args[0]): > > File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ > > return self.gen.next() > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line > > 100, in repo_server_context > > root_dir=prefix.paths.internal_repo(), > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line 76, > > in _create_http_server > > generate_request_handler(root_dir), > > File "/usr/lib64/python2.7/SocketServer.py", line 419, in __init__ > > self.server_bind() > > File "/usr/lib64/python2.7/BaseHTTPServer.py", line 108, in server_bind > > SocketServer.TCPServer.server_bind(self) > > File "/usr/lib64/python2.7/SocketServer.py", line 430, in server_bind > > self.socket.bind(self.server_address) > > File "/usr/lib64/python2.7/socket.py", line 224, in meth > > return getattr(self._sock,name)(*args) > > > > 2017-10-20 07:59:12,485::cmd.py::do_run::365::root::ERROR::Error > > occured, aborting > > Traceback (most recent call last): > > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 362, in > > do_run > > self.cli_plugins[args.ovirtverb].do_run(args) > > File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line > > 184, in do_run > > self._do_run(**vars(args)) > > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 501, in > > wrapper > > return func(*args, **kwargs) > > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 512, in > > wrapper > > return func(*args, prefix=prefix, **kwargs) > > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 166, > > in do_deploy > > prefix.deploy() > > File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, > > in wrapper > > return func(*args, **kwargs) > > File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line > > 111, in wrapper > > with utils.repo_server_context(args[0]): > > File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ > > return self.gen.next() > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line > > 100, in repo_server_context > > root_dir=prefix.paths.internal_repo(), > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line 76, > > in _create_http_server > > generate_request_handler(root_dir), > > File "/usr/lib64/python2.7/SocketServer.py", line 419, in __init__ > > self.server_bind() > > File "/usr/lib64/python2.7/BaseHTTPServer.py", line 108, in server_bind > > SocketServer.TCPServer.server_bind(self) > > File "/usr/lib64/python2.7/SocketServer.py", line 430, in server_bind > > self.socket.bind(self.server_address) > > File "/usr/lib64/python2.7/socket.py", line 224, in meth > > return getattr(self._sock,name)(*args) > > error: [Errno 98] Address already in use > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1712) OST jobs fails on "address already in use"
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1712?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1712: ----------------------------- Priority: High (was: Medium) > OST jobs fails on "address already in use" > ------------------------------------------ > > Key: OVIRT-1712 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1712 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Gal Ben Haim > Priority: High > > Evgheni, > Was there any change recently to Lago slaves? > On Fri, Oct 20, 2017 at 11:05 AM, Piotr Kliczewski < > piotr.kliczewski(a)gmail.com> wrote: > > I attempted to run manual OST twice and both failed with below issue. > > Can someone take a look? > > > > Thanks, > > Piotr > > > > 2017-10-20 07:59:12,485::log_utils.py::__exit__::607::ovirtlago.prefix: > > :DEBUG:: > > File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, > > in wrapper > > return func(*args, **kwargs) > > File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line > > 111, in wrapper > > with utils.repo_server_context(args[0]): > > File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ > > return self.gen.next() > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line > > 100, in repo_server_context > > root_dir=prefix.paths.internal_repo(), > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line 76, > > in _create_http_server > > generate_request_handler(root_dir), > > File "/usr/lib64/python2.7/SocketServer.py", line 419, in __init__ > > self.server_bind() > > File "/usr/lib64/python2.7/BaseHTTPServer.py", line 108, in server_bind > > SocketServer.TCPServer.server_bind(self) > > File "/usr/lib64/python2.7/SocketServer.py", line 430, in server_bind > > self.socket.bind(self.server_address) > > File "/usr/lib64/python2.7/socket.py", line 224, in meth > > return getattr(self._sock,name)(*args) > > > > 2017-10-20 07:59:12,485::cmd.py::do_run::365::root::ERROR::Error > > occured, aborting > > Traceback (most recent call last): > > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 362, in > > do_run > > self.cli_plugins[args.ovirtverb].do_run(args) > > File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line > > 184, in do_run > > self._do_run(**vars(args)) > > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 501, in > > wrapper > > return func(*args, **kwargs) > > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 512, in > > wrapper > > return func(*args, prefix=prefix, **kwargs) > > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 166, > > in do_deploy > > prefix.deploy() > > File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, > > in wrapper > > return func(*args, **kwargs) > > File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line > > 111, in wrapper > > with utils.repo_server_context(args[0]): > > File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ > > return self.gen.next() > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line > > 100, in repo_server_context > > root_dir=prefix.paths.internal_repo(), > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line 76, > > in _create_http_server > > generate_request_handler(root_dir), > > File "/usr/lib64/python2.7/SocketServer.py", line 419, in __init__ > > self.server_bind() > > File "/usr/lib64/python2.7/BaseHTTPServer.py", line 108, in server_bind > > SocketServer.TCPServer.server_bind(self) > > File "/usr/lib64/python2.7/SocketServer.py", line 430, in server_bind > > self.socket.bind(self.server_address) > > File "/usr/lib64/python2.7/socket.py", line 224, in meth > > return getattr(self._sock,name)(*args) > > error: [Errno 98] Address already in use > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1734: ---------------------------------- I think we now have more jobs running on staging, can we close this? > 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: oVirt CI, oVirt Infra > 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-1738) configure tuned on jenkins slaves
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1738?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1738: ----------------------------- Resolution: Duplicate Status: Done (was: To Do) https://ovirt-jira.atlassian.net/browse/OVIRT-1668 > configure tuned on jenkins slaves > --------------------------------- > > Key: OVIRT-1738 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1738 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: sbonazzo > Assignee: infra > > Just noticed we are not tuning our slaves missing tuned on the systems (at least the one I checked vm0160.workers-phx.ovirt.org ) > According to https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… > we should gain a bit by setting virtual-guest profile within the slaves. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1668) Load the right tuned profile on CentOS
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1668?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1668: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) Another option to add to global_setup maybe. > Load the right tuned profile on CentOS > -------------------------------------- > > Key: OVIRT-1668 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1668 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI, oVirt Infra > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > Labels: jenkins, performance, slaves > > There was a story published this weekend explaining that in CentOS, the {{tuned}} performance profile that is selected by default is probably not right for servers: > http://jperrin.org/centos/boosting-centos-server-performance/ > We need to ensure that we select the right profile for our systems. > We should probably just do this from '{{global_setup.sh}}' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1814) Re: Jenkins failing on fcraw
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1814?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1814: ----------------------------- Resolution: Fixed Status: Done (was: To Do) vdsm fcraw jobs were disabled. If at some point maintainers want to enable it, it should be done only after its verified to be working. > Re: Jenkins failing on fcraw > ---------------------------- > > Key: OVIRT-1814 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1814 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: infra > > Adding infra-support to track this. > Evgheni, can you have a look to see if its something on infra side? > On Thu, Dec 21, 2017 at 2:10 PM, Milan Zamazal <mzamazal(a)redhat.com> wrote: > > Hi, I experienced CI -1 on https://gerrit.ovirt.org/#/c/85669/1 due to > > failing fcraw test. I can see that it's due to some broken package > > dependencies on that system. I've heard that fcraw should run the tests > > but not vote, however it put -1 score on the patch. Could it be fixed > > please? > > > > Thanks, > > Milan > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1816) Vdsm builds for fc27 and fcraw enabled by mistake?
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1816?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1816: ----------------------------- Resolution: Fixed Status: Done (was: To Do) jobs disabled for now, please update if/when they should be enabled. Also, if this is something that won't be enabled soon, it might be better to remove it from the YAML > Vdsm builds for fc27 and fcraw enabled by mistake? > -------------------------------------------------- > > Key: OVIRT-1816 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1816 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We tried to enable fc27 and fcraw builds few weeks ago, but we found > that some packages are still missing (I think the only missing package now > is ioprocess). The jobs were disabled until we resolve this. > For some reason the jobs were activated yesterday, and now vdsm patches > fail again: > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/86/ > Please disable the fc27 and fcraw jobs until we resolve the missing > packages. > Nir -- 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 eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1781: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) Doesn't seem related to space issue, please report if it reproduced so we can help debug it in real time. > 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: oVirt CI > Reporter: danken > Assignee: infra > Priority: High > Labels: vdsm > > 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

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1042
by jenkins＠jenkins.phx.ovirt.org 26 Dec '17

26 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1042/displ…> Changes: [Dan Kenigsberg] add network suite to manaul job suite selector ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 Commit message: "add network suite to manaul job suite selector" > git rev-list fa64ebc3c785af5a99aeffd081ec0fb88df044c8 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins561916233656873438.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1173) Please use git shallow clone as jobs default
by eyal edri (oVirt JIRA) 25 Dec '17

25 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1173?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1173: ----------------------------- Resolution: Won't Fix Status: Done (was: To Do) We didn't see any issues with clone on Jenkins due to the current policy, and due to the caching we already have, this won't bring any significant performance improvement and might introduce new errors. > Please use git shallow clone as jobs default > -------------------------------------------- > > Key: OVIRT-1173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roy Golan > Assignee: infra > Priority: Low > Labels: standard-ci > > Most if not all the git clone of the jobs don't need history at all. > For ovirt-engine I see it downloading *11Mb* using --depth 1 vs. *157Mb* > for regular clone. > R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by eyal edri (oVirt JIRA) 25 Dec '17

25 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1788: ----------------------------- Status: In Progress (was: To Do) > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1007) repo closure job should find also optional pkg
by eyal edri (oVirt JIRA) 25 Dec '17

25 Dec '17

This is a multi-part message in MIME format... ------------=_1514218351-25028-112 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1007: ----------------------------- Resolution: Won't Fix Status: Done (was: To Do) repoclosure job migrated to test in ost. > repo closure job should find also optional pkg > ---------------------------------------------- > > Key: OVIRT-1007 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: infra > Priority: Low > > http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514218351-25028-112 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.… ]</pre> <h3>eyal edri updated OVIRT-1007:</h3> <pre>Resolution: Won't Fix Status: Done (was: To Do)</pre> <p>repoclosure job migrated to test in ost.</p> <blockquote><h3>repo closure job should find also optional pkg</h3> <pre> Key: OVIRT-1007 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri Assignee: infra Priority: Low</pre> <p><a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console">http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console</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> ------------=_1514218351-25028-112--

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by eyal edri (oVirt JIRA) 25 Dec '17

25 Dec '17

This is a multi-part message in MIME format... ------------=_1514218057-30883-100 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1769: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) As mentioned, if we want to run such scenario, we need to create a new suite for that, with the relevant tests. Having said that, I'm not sure its worth the resources over testing other flows which are not covered yet. > run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility > ----------------------------------------------------------------------------------- > > Key: OVIRT-1769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. > However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514218057-30883-100 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ]</pre> <h3>eyal edri updated OVIRT-1769:</h3> <pre>Resolution: Won't Do Status: Done (was: To Do)</pre> <p>As mentioned, if we want to run such scenario, we need to create a new suite for that, with the relevant tests. Having said that, I'm not sure its worth the resources over testing other flows which are not covered yet.</p> <blockquote><h3>run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility</h3> <pre> Key: OVIRT-1769 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 Project: oVirt - virtualization made easy Issue Type: New Feature Components: OST Reporter: danken Assignee: infra Priority: High</pre> <p>starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master.</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> ------------=_1514218057-30883-100--

1 0

[CQ]: 85723, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

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

1 0

[CQ]: 85723, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

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

1 0

[CQ]: 85717, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

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

1 0

[CQ]: 85286, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

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

1 0

[CQ]: 85677, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

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

1 0

[CQ]: 85674, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

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

1 0

[CQ]: 85637, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Dec '17

24 Dec '17

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

1 0

[CQ]: 85673, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Dec '17

24 Dec '17

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

1 0

[CQ]: 85672, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Dec '17

24 Dec '17

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

1 0

[CQ]: 85709, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Dec '17

24 Dec '17

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

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1110
by jenkins＠jenkins.phx.ovirt.org 24 Dec '17

24 Dec '17

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 fa64ebc3c785af5a99aeffd081ec0fb88df044c8 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f fa64ebc3c785af5a99aeffd081ec0fb88df044c8 Commit message: "ioprocess: Add Fedora 27 and rawhide builds" > git rev-list fa64ebc3c785af5a99aeffd081ec0fb88df044c8 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins8900733371298178833.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

[CQ]: 85706, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Dec '17

24 Dec '17

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

1 0