- Infra - oVirt List Archives

[CQ]: 88797, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

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

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1357
by jenkins＠jenkins.phx.ovirt.org 12 Mar '18

12 Mar '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Dafna Ron] jenkins_standard: remove fc24 ------------------------------------------ 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 d89ef900ffe6988b68593af3cd0d5364329124a0 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f d89ef900ffe6988b68593af3cd0d5364329124a0 Commit message: "jenkins_standard: remove fc24" > git rev-list --no-walk d30d94cdfa0b352919727029124f90a9a91af34c # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins3985586553809939408.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]: 88587, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88587,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,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 88738,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/88587/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1200/

1 0

ovirt-engine_4.2_check-patch-fc27-x86_64 fails
by Dominik Holler 12 Mar '18

12 Mar '18

Hi, dnf in CI jobs ovirt-engine_4.2_check-patch-fc27-x86_64 [1] is failing for me with: ImportError: libelf.so.1: cannot open shared object file: No such file or directory Can you please have a look? Thanks Dominik [1] http://jenkins.ovirt.org/job/ovirt-engine_4.2_check-patch-fc27-x86_64/411 12:48:21 Start: dnf install 12:48:22 ERROR: Command failed: 12:48:22 # /usr/bin/dnf --installroot /var/lib/mock/fedora-27-x86_64-27659b1e362bd3ee3ef0da8cd3f0c97c-26540/root/ --releasever 27 --disableplugin=local --setopt=deltarpm=False install @buildsys-build libcrypt-nss autoconf git java-1.8.0-openjdk-devel make maven net-tools otopi postgresql-jdbc postgresql-server postgresql-contrib pyflakes python2-mock python2-psycopg2 python2-pytest python-devel python-isort python-pep8 yum-utils --setopt=tsflags=nocontexts 12:48:22 Traceback (most recent call last): 12:48:22 File "/usr/bin/dnf", line 57, in <module> 12:48:22 from dnf.cli import main 12:48:22 File "/usr/lib/python3.6/site-packages/dnf/__init__.py", line 31, in <module> 12:48:22 import dnf.base 12:48:22 File "/usr/lib/python3.6/site-packages/dnf/base.py", line 29, in <module> 12:48:22 from dnf.yum import history 12:48:22 File "/usr/lib/python3.6/site-packages/dnf/yum/history.py", line 22, in <module> 12:48:22 import hawkey 12:48:22 File "/usr/lib64/python3.6/site-packages/hawkey/__init__.py", line 24, in <module> 12:48:22 from . import _hawkey 12:48:22 ImportError: libelf.so.1: cannot open shared object file: No such file or directory

2 1

[CQ]: 88580, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

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

1 0

[JIRA] (OVIRT-1926) squash identified as a mere message update
by Yedidyah Bar David (oVirt JIRA) 12 Mar '18

12 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1926?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-1926: ------------------------------------------- On Mon, Mar 12, 2018 at 2:09 PM, Barak Korren (oVirt JIRA) < Not sure what you mean. I already wrote that there was no code change. But there definitely was a _squash_. So the git history was very different. Patchsets 7 and 8 had different parents. Fine, so you mean I should file a bug against gerrit itself? OK: https://bugs.chromium.org/p/gerrit/issues/detail?id=8521 -- Didi > squash identified as a mere message update > ------------------------------------------ > > Key: OVIRT-1926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1926 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1926) squash identified as a mere message update
by Barak Korren (oVirt JIRA) 12 Mar '18

12 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1926?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1926: ------------------------------------- I don't think it has to do with [1], looking in Gerrit, there does not seem to be any code difference between patchsets 7 and 8 of [2]. In any case this Gerrit behaviour is not something any code we maintain does. > squash identified as a mere message update > ------------------------------------------ > > Key: OVIRT-1926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1926 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

2 1

[CQ]: 88764, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88764,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,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 88738,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/88764/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1198/

1 0

[JIRA] (OVIRT-1926) squash identified as a mere message update
by Yedidyah Bar David (oVirt JIRA) 12 Mar '18

12 Mar '18

Yedidyah Bar David created OVIRT-1926: ----------------------------------------- Summary: squash identified as a mere message update Key: OVIRT-1926 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1926 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra I had [1] and [2]. Patchset 8 of [2] is a combination of: - Patchset 7 of it, - [1] squashed into it, - Commit message change. Gerrit commented: Uploaded patch set 8: Commit message was updated. In theory it was right, because there was no code change between 7 and 8. But I'd expect it to either be silent, or to notice that there was also a squash (and suggest to abandon the squashed patch?). [1] https://gerrit.ovirt.org/#/c/88669/ [2] https://gerrit.ovirt.org/#/c/88634/ -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[CQ]: 88362, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

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

1 0

[CQ]: 88718, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88718,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,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 88738,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/88718/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1196/

1 0

[CQ]: 88717, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88717,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,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 88738,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/88717/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1195/

1 0

standard CI packages files
by Yedidyah Bar David 12 Mar '18

12 Mar '18

Hi all, The various automation/*.packages* files are rather hard to maintain - with many partial duplicates, symlinks, and changes applied to some file forgotten to be applied to others that needed them. Can we have something more dynamic? E.g. that CI will run a single script, e.g. automation/get-needed-packages, provide it as args the action to be ran ("check-patch", "build-artifacts" etc.) and the distro ("el7", "fc27" etc.) and use whatever it outputs as the list of packages to install? Thanks, -- Didi

2 3

OST testing and releases of ovirt-ansible-* projects
by Barak Korren 12 Mar '18

12 Mar '18

Due to an issue we had with our post-merge triggering code for GitHub, most merge event for Github projects were not handled and therefore theses projects were not processes by the change queue and not released into the nightly repos. We've now resolved the issue and replayed the most recent merge event for the `ovirt-ansible` project. I need to know if there are any other projects on GitHub that need to release RPMs via the oVirt change queue. If so, we probably need to take action to generate merge events for them by either merging new changes or replaying older merge events. Please let me know, Thanks, -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 2

[CQ]: 88772, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

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

1 0

[CQ]: 88670, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

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

1 0

[oVirt Jenkins] ovirt-appliance_4.2_build-artifacts-el7-x86_64 - Build # 7 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Mar '18

12 Mar '18

------=_Part_131_2080624497.1520766910612 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_4.2_build-artifacts-el7-x86_64… Build Number: 7 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #7 [Barak Korren] Adapt for lowercase GitHub headers [Sandro Bonazzola] build: use 4.2 snapshot release rpm ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_131_2080624497.1520766910612--

1 1

[CQ]: 88760, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

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

1 0

[CQ]: 88646, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

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

1 0

[CQ]: 88689, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

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

1 0

[CQ]: 88355, 13 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 210 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Mar '18

12 Mar '18

------=_Part_124_1917432440.1520739757146 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1= /=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/2= 10/ Build Number: 210 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #210 [Sandro Bonazzola] image-ng-suite-4.2: fix jobs naming ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: status: 409 reason: Conflict detail: Server 192.168.201.4 is already part of another cluster. -------------------- >> begin captured logging << -------------------- lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_v= ia_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.1/ovirt= -system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 141= , in _add_host return api.hosts.add(p) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py= ", line 18306, in add headers=3D{"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 79, in add return self.request('POST', url, body, headers, cls=3Dcls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 122, in request persistent_auth=3Dself.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body= ) RequestError:=20 status: 409 reason: Conflict detail: Server 192.168.201.4 is already part of another cluster. --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.1/ovirt= -system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 160= , in add_hosts nt.assert_true(all(vt.join_all())) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_v= ia_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.1/ovirt= -system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 141= , in _add_host return api.hosts.add(p) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py= ", line 18306, in add headers=3D{"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 79, in add return self.request('POST', url, body, headers, cls=3Dcls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 122, in request persistent_auth=3Dself.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body= ) '\r\nstatus: 409\r\nreason: Conflict\r\ndetail: Server 192.168.201.4 is alr= eady part of another cluster.\n-------------------- >> begin captured loggi= ng << --------------------\nlago.utils: ERROR: Error while running thread\n= Traceback (most recent call last):\n File "/usr/lib/python2.7/site-package= s/lago/utils.py", line 58, in _ret_via_queue\n queue.put({\'return\': fu= nc()})\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4= .1/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", = line 141, in _add_host\n return api.hosts.add(p)\n File "/usr/lib/pytho= n2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 18306, in add\= n headers=3D{"Correlation-Id":correlation_id, "Expect":expect}\n File "= /usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79= , in add\n return self.request(\'POST\', url, body, headers, cls=3Dcls)\= n File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py"= , line 122, in request\n persistent_auth=3Dself.__persistent_auth\n Fil= e "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool= .py", line 79, in do_request\n persistent_auth)\n File "/usr/lib/python= 2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in= __do_request\n raise errors.RequestError(response_code, response_reason= , response_body)\nRequestError: \r\nstatus: 409\r\nreason: Conflict\r\ndeta= il: Server 192.168.201.4 is already part of another cluster.\n-------------= -------- >> end captured logging << ---------------------' ------=_Part_124_1917432440.1520739757146--

1 1

[CQ]: 88695, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[CQ]: 88694, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[CQ]: 88571, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[CQ]: 88771, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[CQ]: 88576, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[CQ]: 88763, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[CQ]: 88575, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[CQ]: 88574, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[CQ]: 88573, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[CQ]: 88572, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 4 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 Mar '18

11 Mar '18

------=_Part_143_2113623080.1520217917378 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/4/ Build Number: 4 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #4 [Eyal Edri] Revert "track LSM job status" ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_143_2113623080.1520217917378--

3 13

[CQ]: 88759, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA) 11 Mar '18

11 Mar '18

This is a multi-part message in MIME format... ------------=_1520780298-10370-189 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1915: -------------------------------- Assignee: Dusan Dodor (was: infra) > Add option to filter packages in OST manual > ------------------------------------------- > > Key: OVIRT-1915 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: Dusan Dodor > Labels: jenkins, ost > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1520780298-10370-189 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1915:</h3> <pre>Assignee: Dusan Dodor (was: infra)</pre> <blockquote><h3>Add option to filter packages in OST manual</h3> <pre> Key: OVIRT-1915 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: Dusan Dodor Labels: jenkins, ost</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</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> ------------=_1520780298-10370-189--

1 0

[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA) 11 Mar '18

11 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ] eyal edri edited comment on OVIRT-1915 at 3/11/18 2:56 PM: ----------------------------------------------------------- Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments. {code:java} ARCHS=("x86_64 noarch") echo -n "" > ${EXT_RESOURCES} for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos {code} was (Author: eedri): Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments. {quote}ARCHS=("x86_64 noarch") echo -n "" > ${EXT_RESOURCES} for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos{quote} > Add option to filter packages in OST manual > ------------------------------------------- > > Key: OVIRT-1915 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins, ost > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA) 11 Mar '18

11 Mar '18

This is a multi-part message in MIME format... ------------=_1520780153-28237-134 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ] eyal edri edited comment on OVIRT-1915 at 3/11/18 2:55 PM: ----------------------------------------------------------- Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments. {quote}ARCHS=("x86_64 noarch") echo -n "" > ${EXT_RESOURCES} for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos{quote} was (Author: eedri): Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments. ARCHS=("x86_64 noarch") echo -n "" > ${EXT_RESOURCES} for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos > Add option to filter packages in OST manual > ------------------------------------------- > > Key: OVIRT-1915 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins, ost > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1520780153-28237-134 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ]</pre> <h3>eyal edri edited comment on OVIRT-1915 at 3/11/18 2:55 PM:</h3> <p>Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments.</p> <pre>{quote}ARCHS=("x86_64 noarch") echo -n "" > ${EXT_RESOURCES} for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos{quote}</pre> <p>was (Author: eedri): Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments.</p> <pre>ARCHS=("x86_64 noarch") echo -n "" > ${EXT_RESOURCES} for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos</pre> <blockquote><h3>Add option to filter packages in OST manual</h3> <pre> Key: OVIRT-1915 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra Labels: jenkins, ost</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</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> ------------=_1520780153-28237-134--

1 0

[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA) 11 Mar '18

11 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1915: ---------------------------------- Suggested code to add to the manual job ( taken from ds job ) to update the extra sources file, probably needs some work and adjustments. ARCHS=("x86_64 noarch") echo -n "" > ${EXT_RESOURCES} for arch in ${ARCHS} ; do echo "${CUSTOM_REPOS}${arch}/${FILTER_PACKAGES:=''}" >> ${EXT_RESOURCES} ; done sed -i "s|${SUITE_TYPE}.*|${SUITE_TYPE}_${VERSION}_custom,${CUSTOM_REPOS#rec:}|" ${WORK_DIR}/automation/${OVIRT_SUITE}.repos > Add option to filter packages in OST manual > ------------------------------------------- > > Key: OVIRT-1915 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins, ost > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 11 Mar '18

11 Mar '18

This is a multi-part message in MIME format... ------------=_1520772140-16160-156 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ] Greg Sheremeta commented on OST-99: ----------------------------------- https://gerrit.ovirt.org/#/c/67166 > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1520772140-16160-156 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ]</pre> <h3>Greg Sheremeta commented on OST-99:</h3> <p><a href="https://gerrit.ovirt.org/#/c/67166">https://gerrit.ovirt.org/#/c/67166</a></p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OST-99 URL: https://ovirt-jira.atlassian.net/browse/OST-99 Project: oVirt system tests Issue Type: Improvement Reporter: Greg Sheremeta Assignee: infra</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</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> ------------=_1520772140-16160-156--

1 0

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 11 Mar '18

11 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ] Greg Sheremeta updated OST-99: ------------------------------ Description: 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.) ... Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and [docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-S…] Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves. --- https://gerrit.ovirt.org/#/c/67166 was: 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.) ... Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and [docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-S…] Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 11 Mar '18

11 Mar '18

This is a multi-part message in MIME format... ------------=_1520772085-26371-157 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ] Greg Sheremeta commented on OST-99: ----------------------------------- I have this working and a patch posted -- closing. Thanks for the help everyone! > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1520772085-26371-157 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ]</pre> <h3>Greg Sheremeta commented on OST-99:</h3> <p>I have this working and a patch posted — closing.</p> <p>Thanks for the help everyone!</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OST-99 URL: https://ovirt-jira.atlassian.net/browse/OST-99 Project: oVirt system tests Issue Type: Improvement Reporter: Greg Sheremeta Assignee: infra</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</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> ------------=_1520772085-26371-157--

1 0

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 11 Mar '18

11 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ] Greg Sheremeta updated OST-99: ------------------------------ Resolution: Done Status: Done (was: In Progress) > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 11 Mar '18

11 Mar '18

This is a multi-part message in MIME format... ------------=_1520771999-12112-110 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ] Greg Sheremeta updated OST-99: ------------------------------ Description: 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.) ... Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and [docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-S…] Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves. was: 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.) > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1520771999-12112-110 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ]</pre> <h3>Greg Sheremeta updated OST-99:</h3> <pre>Description:</pre> <p>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.</p> <p>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.</p> <p>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.</p> <p>Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p> <p>…</p> <p>Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|<a href="https://www.seleniumhq.org/docs/07_selenium_grid.jsp">https://www.seleniumhq.org/docs/07_selenium_grid.jsp</a>] and [docker-compose|<a href="https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-Doc…">https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-Doc…</a>]. Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves.</p> <pre>was:</pre> <p>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.</p> <p>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.</p> <p>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.</p> <p>Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OST-99 URL: https://ovirt-jira.atlassian.net/browse/OST-99 Project: oVirt system tests Issue Type: Improvement Reporter: Greg Sheremeta Assignee: infra</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</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> ------------=_1520771999-12112-110--

1 0

[CQ]: 88741, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88741,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,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 88738,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/88741/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1181/

1 0

[CQ]: 88581, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Mar '18

11 Mar '18

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

1 0

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

11 Mar '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 d366bf1404c10c49b1f2ed0fe5a0bd9403edd23f (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f d366bf1404c10c49b1f2ed0fe5a0bd9403edd23f Commit message: "Make headers lowercase for standard-webhook-trigger" > git rev-list --no-walk d366bf1404c10c49b1f2ed0fe5a0bd9403edd23f # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6923647727206306001.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]: 88741, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Mar '18

10 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88741,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,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 88738,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/88741/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1176/

1 0

[CQ]: 88739, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Mar '18

10 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88739,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,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 88738,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/88739/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1175/

1 0

[CQ]: 88738,2 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 10 Mar '18

10 Mar '18

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

1 0

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 729 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Mar '18

10 Mar '18

------=_Part_111_1430416280.1520604805392 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build Number: 729 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #729 [Sandro Bonazzola] fedora: drop all fcraw jobs [Sandro Bonazzola] system-tests: add hc-basic-suite-4.2 [Sandro Bonazzola] system-tests: add he-basic-ansible-4.2 [Sandro Bonazzola] build: align fedora builds ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_111_1430416280.1520604805392--

1 1