- Infra - oVirt List Archives

[JIRA] (OVIRT-2527) whitelist issue
by Eyal Edri (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2527?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2527: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > whitelist issue > --------------- > > Key: OVIRT-2527 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2527 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > Attachments: Selection_169.png > > > Hi, > Even though Bohdan is in the whitelist, (I think) the github bot is > complaining he's not. Can you assist? His redhat account is on his profile: > [image: Selection_169.png] > Example: > https://github.com/oVirt/ovirt-web-ui/pull/804#issuecomment-427324354 > Best wishes, > Greg > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2453) vdsm_{master,4.2} check-merge to run on bare metal slaves on CI
by Eyal Edri (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2453?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2453: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) check-merged job was dropped as part of moving to V2. > vdsm_{master,4.2} check-merge to run on bare metal slaves on CI > --------------------------------------------------------------- > > Key: OVIRT-2453 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2453 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: infra > > Hello, > VDSM check-merge is using lago VM/s to run functional tests, mainly in the > network domain. > Unfortunately, when running on a VM slave, the tests are running in a > nested VM which seems to be unstable (the nested VM is getting > stuck/crashes). > Here are some recent failures: > http://jenkins.ovirt.org/job/vdsm_4.2_check-merged-el7-x86_64/247/ > http://jenkins.ovirt.org/job/vdsm_4.2_check-merged-el7-x86_64/249/ > Could you please run this job on a bare metal slave? > Thanks, > Edy. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Eyal Edri (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2358: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) no reply from requestor, please reopen if needed. > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2227) Re: Push rights to vdsm
by Eyal Edri (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2227?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2227: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: Push rights to vdsm > ----------------------- > > Key: OVIRT-2227 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2227 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > Hi > You just need to ask one of the existing maintainers to send a patch to the > 'jenkins-whitelist' repo on gerrit.ovirt.org and > one of the infra members can merge it once it has +1 from an existing > maintainer. > I'm also adding 'infra-support' to open a ticket. > On Thu, Jun 21, 2018 at 11:14 AM, Tomasz Barański <tbaransk(a)redhat.com> > wrote: > > Eyal, > > > > Apparently I also need to be added to the CI whitelist. > > > > Tomo > > > > On 20.06.2018 12:49, Eyal Edri wrote: > > > > No worries, glad it works for you. > > Don't hesitate to reach out to infra again if you have any issues. > > > > On Wed, Jun 20, 2018 at 1:29 PM Tomasz Barański <tbaransk(a)redhat.com> > > wrote: > > > >> Eyal, > >> > >> I didn't set `username` in gerrit. Seems to have missed this step. > >> > >> It works now, sorry to bother you. > >> > >> Tomo > >> > >> On 20.06.2018 12:03, Eyal Edri wrote: > >> > >> Any registered user have push rights to new patches, did you follow the > >> guidelines on how to contribute to and oVirt project? > >> > >> https://ovirt.org/develop/dev-process/working-with-gerrit/ > >> > >> On Wed, Jun 20, 2018 at 1:00 PM Tomasz Barański <tbaransk(a)redhat.com> > >> wrote: > >> > >>> Hello, > >>> > >>> As a new Red Hatter, I need push right to `vdsm` project in oVirt's > >>> gerrit. > >>> > >>> Thank you > >>> Tomasz > >>> _______________________________________________ > >>> Infra mailing list -- infra(a)ovirt.org > >>> To unsubscribe send an email to infra-leave(a)ovirt.org > >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community- > >>> guidelines/ > >>> List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/ > >>> message/2QDBTW4HH2FUGSQXHVDML5K3SIEAKIE2/ > >>> > >> > >> > >> -- > >> > >> 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) > >> > >> > >> > > > > -- > > > > 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) > > > > > > > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community- > > guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/ > > message/F5LTNHLWRG4MLLBKMJQQGAOFDUGSPPCO/ > > > > > -- > Emil Natan > RHV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by Eyal Edri (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] Eyal Edri updated OVIRT-686: ---------------------------- Resolution: Won't Do Status: Done (was: To Do) > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, monitoring > Reporter: Eyal Edri > Assignee: infra > Priority: Low > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2623) use AsyncEventDispatcher on Jenkins SSE gateway
by Evgheni Dereveanchin (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2623?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2623: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > use AsyncEventDispatcher on Jenkins SSE gateway > ----------------------------------------------- > > Key: OVIRT-2623 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2623 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The SSE gateway plugin should perform better with AsyncEventDispatcher, logging ticket to add the relevant option to our instances: > -Djenkins.eventbus.web.asyncSupported=true -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2623) use AsyncEventDispatcher on Jenkins SSE gateway
by Evgheni Dereveanchin (oVirt JIRA) 12 Dec '18

12 Dec '18

Evgheni Dereveanchin created OVIRT-2623: ------------------------------------------- Summary: use AsyncEventDispatcher on Jenkins SSE gateway Key: OVIRT-2623 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2623 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra The SSE gateway plugin should perform better with AsyncEventDispatcher, logging ticket to add the relevant option to our instances: -Djenkins.eventbus.web.asyncSupported=true -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2619) Jenkins network extremely slow
by Evgheni Dereveanchin (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2619?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2619: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Jenkins network extremely slow > ------------------------------ > > Key: OVIRT-2619 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2619 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > Priority: High > Labels: network > > Looking at: > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x… > Download of Fedora Boot ISO: > *08:10:57* curl -L -O > "http://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_6…"*08:10:57* > % Total % Received % Xferd Average Speed Time Time Time > Current*08:10:57* Dload Upload > Total Spent Left Speed > It took ~ 2 hours to get the download running and then: > 83 583M 83 484M 0 0 82299 0 2:03:48 1:42:55 > 0:20:53 33902*09:53:57* curl: (92) HTTP/2 stream 1 was not closed > cleanly: INTERNAL_ERROR (err 2) > Can you please check connectivity? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

Build failed in Jenkins: system-sync_mirrors-glusterfs-3.12-el7-x86_64 #1338
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-3.12-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-glusterfs-3.12-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 ec1076002fa17ca9bbd8b4f75d54cad39e990257 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ec1076002fa17ca9bbd8b4f75d54cad39e990257 Commit message: "Adding manifests for OC" > git rev-list --no-walk ec1076002fa17ca9bbd8b4f75d54cad39e990257 # timeout=10 [system-sync_mirrors-glusterfs-3.12-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6198879915747789034.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-3.12-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 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1039, in _getFile raise e yum.Errors.NoMoreMirrorsRepoError: failure: repodata/repomd.xml from glusterfs-3.12-el7: [Errno 256] No more mirrors to try. http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.12/repodata/repo…: [Errno 14] curl#7 - "Failed to connect to 2607:4d00:1:100:250:56ff:fea3:37b5: Network is unreachable" Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2620) Mirroring error
by Eyal Edri (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2620?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2620: ---------------------------------- [~bkorren(a)redhat.com] any idea? > Mirroring error > --------------- > > Key: OVIRT-2620 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2620 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > *Hi,* > *looks like in our mirror script there's a bug, we don't clean the > <repo>/gen directory before starting the mirroring* > *04:35:12* yum.Errors.RepoError: Error making cache directory: > /home/jenkins/mirrors_cache/centos-kvm-common-el7/gen error was: > [Errno 17] File exists: > '/home/jenkins/mirrors_cache/centos-kvm-common-el7/gen' > Job: > https://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86… > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 96078,5 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 Dec '18

12 Dec '18

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

2 1

[JIRA] (OVIRT-2619) Jenkins network extremely slow
by Barak Korren (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2619?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2619: ------------------------------------- This is using the proxy: {code} 00:01:44.031 Using proxified config /home/jenkins/workspace/ovirt-appliance_ovirt-4.3_build-artifacts-fc28-x86_64/jenkins/mock_configs/fedora-28-x86_64_proxied.cfg {code} [~ederevea] can we check if the proxy became slow or unresponsive? > Jenkins network extremely slow > ------------------------------ > > Key: OVIRT-2619 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2619 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > Priority: High > Labels: network > > Looking at: > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x… > Download of Fedora Boot ISO: > *08:10:57* curl -L -O > "http://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_6…"*08:10:57* > % Total % Received % Xferd Average Speed Time Time Time > Current*08:10:57* Dload Upload > Total Spent Left Speed > It took ~ 2 hours to get the download running and then: > 83 583M 83 484M 0 0 82299 0 2:03:48 1:42:55 > 0:20:53 33902*09:53:57* curl: (92) HTTP/2 stream 1 was not closed > cleanly: INTERNAL_ERROR (err 2) > Can you please check connectivity? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Failed to run project_setup.sh for: #2890 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-6lj84.

1 0

[JIRA] (OVIRT-2621) setlocale warnings in mock logs
by Barak Korren (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2621?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2621: ------------------------------------- I think this is specific to the node-ng build job that was linked to. It seems to be trying to run the 'setlocale' command on multiple occasions and failing. It looks like it can be a simple matter of installing the right package in the {{*. packages}} file. Looking at my own RHEL workstation - I don't have the 'setlocale' command - so it may have been deprecated or move around at some point. > setlocale warnings in mock logs > ------------------------------- > > Key: OVIRT-2621 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2621 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > There's a bunch of setlocale warnings in mock logs which didn't exist before: > https://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-e… > We need to verify what happened to get rid of these messages as they are distracting attention from real failure causes -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 386 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/386/ Build Number: 386 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #386 [Dan Kenigsberg] basic suite: use fancy bond names ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 003_basic_networking.bond_nics_41 Error Message: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f93ad6d9320> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics [bond]) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host check_connectivity=True), True, []) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. ovirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f93ad6a47d0> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics [bond]) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host check_connectivity=True), True, []) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. --------------------- >> 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 runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 197, in bond_nics utils.invoke_in_parallel(_bond_nics, range(1, len(hosts) + 1), hosts) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 100, in invoke_in_parallel return vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics [bond]) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host check_connectivity=True), True, []) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error 'Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f93ad6d9320>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\nlago.utils: ERROR: Error while running thread\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue\n queue.put({\'return\': func()})\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics\n [bond])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host\n check_connectivity=True), True, [])\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short\n func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\novirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f93ad6a47d0>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\nlago.utils: ERROR: Error while running thread\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue\n queue.put({\'return\': func()})\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics\n [bond])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host\n check_connectivity=True), True, [])\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short\n func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\n--------------------- >> end captured logging << ---------------------'

1 33

[JIRA] (OVIRT-2622) jenkins slave missing KVM support
by Emil Natan (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2622?page=com.atlassian.jira.… ] Emil Natan updated OVIRT-2622: ------------------------------ Resolution: Won't Fix Status: Done (was: To Do) > jenkins slave missing KVM support > --------------------------------- > > Key: OVIRT-2622 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2622 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' > 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM > 09:02:53 + echo 'options kvm_intel nested=y' > 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf > 09:02:53 options kvm_intel nested=y > 09:02:53 + sudo -n rmmod kvm_intel > 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded > 09:02:54 + sudo -n modprobe kvm_intel nested=y > 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not > supported > 09:02:54 + is_nested_kvm_enabled > 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested > 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] > 09:02:54 + return 1 > 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' > 09:02:54 + local level=ERROR > 09:02:54 + shift > 09:02:54 + local 'message=failed to enable nested KVM, aborting' > 09:02:54 + local prefix > 09:02:54 + [[ 4 -gt 1 ]] > 09:02:54 + prefix='global_setup[nested_kvm]' > 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested > KVM, aborting' > 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, > aborting > 09:02:54 + return 1 > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2622) jenkins slave missing KVM support
by Emil Natan (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2622?page=com.atlassian.jira.… ] Emil Natan updated OVIRT-2622: ------------------------------ Summary: jenkins slave missing KVM support (was: cinteg19.ci.lab.tlv.redhat.com missing KVM support) > jenkins slave missing KVM support > --------------------------------- > > Key: OVIRT-2622 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2622 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' > 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM > 09:02:53 + echo 'options kvm_intel nested=y' > 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf > 09:02:53 options kvm_intel nested=y > 09:02:53 + sudo -n rmmod kvm_intel > 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded > 09:02:54 + sudo -n modprobe kvm_intel nested=y > 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not > supported > 09:02:54 + is_nested_kvm_enabled > 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested > 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] > 09:02:54 + return 1 > 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' > 09:02:54 + local level=ERROR > 09:02:54 + shift > 09:02:54 + local 'message=failed to enable nested KVM, aborting' > 09:02:54 + local prefix > 09:02:54 + [[ 4 -gt 1 ]] > 09:02:54 + prefix='global_setup[nested_kvm]' > 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested > KVM, aborting' > 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, > aborting > 09:02:54 + return 1 > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2622) cinteg19.ci.lab.tlv.redhat.com missing KVM support
by Emil Natan (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2622?page=com.atlassian.jira.… ] Emil Natan updated OVIRT-2622: ------------------------------ Description: 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM 09:02:53 + echo 'options kvm_intel nested=y' 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf 09:02:53 options kvm_intel nested=y 09:02:53 + sudo -n rmmod kvm_intel 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded 09:02:54 + sudo -n modprobe kvm_intel nested=y 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not supported 09:02:54 + is_nested_kvm_enabled 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] 09:02:54 + return 1 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' 09:02:54 + local level=ERROR 09:02:54 + shift 09:02:54 + local 'message=failed to enable nested KVM, aborting' 09:02:54 + local prefix 09:02:54 + [[ 4 -gt 1 ]] 09:02:54 + prefix='global_setup[nested_kvm]' 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting' 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting 09:02:54 + return 1 -- Emil Natan RHV/CNV DevOps was: https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ds-jenkins_s… 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM 09:02:53 + echo 'options kvm_intel nested=y' 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf 09:02:53 options kvm_intel nested=y 09:02:53 + sudo -n rmmod kvm_intel 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded 09:02:54 + sudo -n modprobe kvm_intel nested=y 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not supported 09:02:54 + is_nested_kvm_enabled 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] 09:02:54 + return 1 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' 09:02:54 + local level=ERROR 09:02:54 + shift 09:02:54 + local 'message=failed to enable nested KVM, aborting' 09:02:54 + local prefix 09:02:54 + [[ 4 -gt 1 ]] 09:02:54 + prefix='global_setup[nested_kvm]' 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting' 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting 09:02:54 + return 1 -- Emil Natan RHV/CNV DevOps > cinteg19.ci.lab.tlv.redhat.com missing KVM support > -------------------------------------------------- > > Key: OVIRT-2622 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2622 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' > 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM > 09:02:53 + echo 'options kvm_intel nested=y' > 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf > 09:02:53 options kvm_intel nested=y > 09:02:53 + sudo -n rmmod kvm_intel > 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded > 09:02:54 + sudo -n modprobe kvm_intel nested=y > 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not > supported > 09:02:54 + is_nested_kvm_enabled > 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested > 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] > 09:02:54 + return 1 > 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' > 09:02:54 + local level=ERROR > 09:02:54 + shift > 09:02:54 + local 'message=failed to enable nested KVM, aborting' > 09:02:54 + local prefix > 09:02:54 + [[ 4 -gt 1 ]] > 09:02:54 + prefix='global_setup[nested_kvm]' > 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested > KVM, aborting' > 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, > aborting > 09:02:54 + return 1 > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2622) cinteg19.ci.lab.tlv.redhat.com missing KVM support
by Barak Korren (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2622?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2622: ------------------------------------- [~ena(a)redhat.com] this is a DS issue, this is the US jira. Please delete this ticket and open in the right place. > cinteg19.ci.lab.tlv.redhat.com missing KVM support > -------------------------------------------------- > > Key: OVIRT-2622 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2622 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ds-jenkins_s… > 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' > 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM > 09:02:53 + echo 'options kvm_intel nested=y' > 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf > 09:02:53 options kvm_intel nested=y > 09:02:53 + sudo -n rmmod kvm_intel > 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded > 09:02:54 + sudo -n modprobe kvm_intel nested=y > 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not > supported > 09:02:54 + is_nested_kvm_enabled > 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested > 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] > 09:02:54 + return 1 > 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' > 09:02:54 + local level=ERROR > 09:02:54 + shift > 09:02:54 + local 'message=failed to enable nested KVM, aborting' > 09:02:54 + local prefix > 09:02:54 + [[ 4 -gt 1 ]] > 09:02:54 + prefix='global_setup[nested_kvm]' > 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested > KVM, aborting' > 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, > aborting > 09:02:54 + return 1 > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2622) cinteg19.ci.lab.tlv.redhat.com missing KVM support
by Emil Natan (oVirt JIRA) 12 Dec '18

12 Dec '18

Emil Natan created OVIRT-2622: --------------------------------- Summary: cinteg19.ci.lab.tlv.redhat.com missing KVM support Key: OVIRT-2622 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2622 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Emil Natan Assignee: infra https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ds-jenkins_s… 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM 09:02:53 + echo 'options kvm_intel nested=y' 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf 09:02:53 options kvm_intel nested=y 09:02:53 + sudo -n rmmod kvm_intel 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded 09:02:54 + sudo -n modprobe kvm_intel nested=y 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not supported 09:02:54 + is_nested_kvm_enabled 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] 09:02:54 + return 1 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' 09:02:54 + local level=ERROR 09:02:54 + shift 09:02:54 + local 'message=failed to enable nested KVM, aborting' 09:02:54 + local prefix 09:02:54 + [[ 4 -gt 1 ]] 09:02:54 + prefix='global_setup[nested_kvm]' 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting' 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting 09:02:54 + return 1 -- Emil Natan RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 599 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build Number: 599 Build Status: Failure Triggered By: Started by user Sandro Bonazzola ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #599 [Ryan Barry] kickstart: let VDSM reconfigure itself ----------------- Failed Tests: ----------------- No tests ran.

1 6

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Failed to run project_setup.sh for: #2889 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-gm3nr.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Failed to run project_setup.sh for: #2889 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-3ff4j.

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 386 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/386/ Build Number: 386 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #386 [Dan Kenigsberg] basic suite: use fancy bond names ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 003_basic_networking.bond_nics_42 Error Message: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f8fd4088320> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics [bond]) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host check_connectivity=True), True, []) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. ovirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f8fd40537d0> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics [bond]) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host check_connectivity=True), True, []) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. --------------------- >> 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 runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/003_basic_networking.py", line 197, in bond_nics utils.invoke_in_parallel(_bond_nics, range(1, len(hosts) + 1), hosts) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 100, in invoke_in_parallel return vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics [bond]) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host check_connectivity=True), True, []) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error 'Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f8fd4088320>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\nlago.utils: ERROR: Error while running thread\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue\n queue.put({\'return\': func()})\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics\n [bond])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host\n check_connectivity=True), True, [])\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short\n func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\novirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f8fd40537d0>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\nlago.utils: ERROR: Error while running thread\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue\n queue.put({\'return\': func()})\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics\n [bond])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host\n check_connectivity=True), True, [])\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short\n func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\n--------------------- >> end captured logging << ---------------------'

1 33

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Failed to run project_setup.sh for: #2888 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-2zt9s.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Failed to run project_setup.sh for: #2888 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-k0dq1.

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.3_build-artifacts-fc28-x86_64 - Build # 24 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc28… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc28… Build Number: 24 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #24 [Marcin Sobczyk] vdsm: Disable CI v1 for VDSM's ovirt-4.2 branch [Gal Ben Haim] Adding manifests for OC [Sandro Bonazzola] build: appliance for 4.3.0 alpha ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2621) setlocale warnings in mock logs
by Eyal Edri (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2621?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2621: ---------------------------------- [~bkorren(a)redhat.com] any idea what can cause it? > setlocale warnings in mock logs > ------------------------------- > > Key: OVIRT-2621 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2621 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > There's a bunch of setlocale warnings in mock logs which didn't exist before: > https://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-e… > We need to verify what happened to get rid of these messages as they are distracting attention from real failure causes -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2619) Jenkins network extremely slow
by Eyal Edri (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2619?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2619: ---------------------------------- [~bkorren(a)redhat.com][~ederevea] can you check if something is out of the ordinary? How long does it usually take to download that image? > Jenkins network extremely slow > ------------------------------ > > Key: OVIRT-2619 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2619 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > Priority: High > Labels: network > > Looking at: > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x… > Download of Fedora Boot ISO: > *08:10:57* curl -L -O > "http://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_6…"*08:10:57* > % Total % Received % Xferd Average Speed Time Time Time > Current*08:10:57* Dload Upload > Total Spent Left Speed > It took ~ 2 hours to get the download running and then: > 83 583M 83 484M 0 0 82299 0 2:03:48 1:42:55 > 0:20:53 33902*09:53:57* curl: (92) HTTP/2 stream 1 was not closed > cleanly: INTERNAL_ERROR (err 2) > Can you please check connectivity? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2619) Jenkins network extremely slow
by sbonazzo (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2619?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2619: --------------------------------- Happening again: https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > Jenkins network extremely slow > ------------------------------ > > Key: OVIRT-2619 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2619 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > Priority: High > Labels: network > > Looking at: > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x… > Download of Fedora Boot ISO: > *08:10:57* curl -L -O > "http://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_6…"*08:10:57* > % Total % Received % Xferd Average Speed Time Time Time > Current*08:10:57* Dload Upload > Total Spent Left Speed > It took ~ 2 hours to get the download running and then: > 83 583M 83 484M 0 0 82299 0 2:03:48 1:42:55 > 0:20:53 33902*09:53:57* curl: (92) HTTP/2 stream 1 was not closed > cleanly: INTERNAL_ERROR (err 2) > Can you please check connectivity? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2619) Jenkins network extremely slow
by sbonazzo (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2619?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-2619: ---------------------------- Labels: network (was: ) > Jenkins network extremely slow > ------------------------------ > > Key: OVIRT-2619 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2619 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > Priority: High > Labels: network > > Looking at: > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x… > Download of Fedora Boot ISO: > *08:10:57* curl -L -O > "http://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_6…"*08:10:57* > % Total % Received % Xferd Average Speed Time Time Time > Current*08:10:57* Dload Upload > Total Spent Left Speed > It took ~ 2 hours to get the download running and then: > 83 583M 83 484M 0 0 82299 0 2:03:48 1:42:55 > 0:20:53 33902*09:53:57* curl: (92) HTTP/2 stream 1 was not closed > cleanly: INTERNAL_ERROR (err 2) > Can you please check connectivity? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2619) Jenkins network extremely slow
by sbonazzo (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2619?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-2619: ---------------------------- Component/s: Jenkins Slaves > Jenkins network extremely slow > ------------------------------ > > Key: OVIRT-2619 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2619 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > Priority: High > > Looking at: > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x… > Download of Fedora Boot ISO: > *08:10:57* curl -L -O > "http://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_6…"*08:10:57* > % Total % Received % Xferd Average Speed Time Time Time > Current*08:10:57* Dload Upload > Total Spent Left Speed > It took ~ 2 hours to get the download running and then: > 83 583M 83 484M 0 0 82299 0 2:03:48 1:42:55 > 0:20:53 33902*09:53:57* curl: (92) HTTP/2 stream 1 was not closed > cleanly: INTERNAL_ERROR (err 2) > Can you please check connectivity? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2619) Jenkins network extremely slow
by sbonazzo (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2619?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-2619: ---------------------------- Priority: High (was: Medium) > Jenkins network extremely slow > ------------------------------ > > Key: OVIRT-2619 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2619 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Priority: High > > Looking at: > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x… > Download of Fedora Boot ISO: > *08:10:57* curl -L -O > "http://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_6…"*08:10:57* > % Total % Received % Xferd Average Speed Time Time Time > Current*08:10:57* Dload Upload > Total Spent Left Speed > It took ~ 2 hours to get the download running and then: > 83 583M 83 484M 0 0 82299 0 2:03:48 1:42:55 > 0:20:53 33902*09:53:57* curl: (92) HTTP/2 stream 1 was not closed > cleanly: INTERNAL_ERROR (err 2) > Can you please check connectivity? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

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

12 Dec '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Marcin Sobczyk] vdsm: Disable CI v1 for VDSM's ovirt-4.2 branch [Gal Ben Haim] Adding manifests for OC ------------------------------------------ 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 ec1076002fa17ca9bbd8b4f75d54cad39e990257 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ec1076002fa17ca9bbd8b4f75d54cad39e990257 Commit message: "Adding manifests for OC" > git rev-list --no-walk feff189d208315e470475cbdc8041d3d83492832 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1362137859218311069.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 Error setting up repositories: centos-updates-el7: Check uncompressed DB failed Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 671
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/671//artifact/exported-a… Cheers, Jenkins

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #97
by jenkins＠jenkins.phx.ovirt.org 11 Dec '18

11 Dec '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/97…> Changes: [Marcin Sobczyk] vdsm: Disable CI v1 for VDSM's ovirt-4.2 branch ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-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 e97d839d88015988b9ed86c6ffb3264c2b458417 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e97d839d88015988b9ed86c6ffb3264c2b458417 Commit message: "vdsm: Disable CI v1 for VDSM's ovirt-4.2 branch" > git rev-list --no-walk feff189d208315e470475cbdc8041d3d83492832 # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins1400875734378722728.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 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-kvm-common-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7' Build step 'Execute shell' marked build as failure

1 1

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

11 Dec '18

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

2 1

[CQ]: 96125,4 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 11 Dec '18

11 Dec '18

Change 96125,4 (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/96125/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3616/

1 0

[CQ]: 95769, 1 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests
by oVirt Jenkins 11 Dec '18

11 Dec '18

Change 95769,1 (ovirt-hosted-engine-ha) 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/95769/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11960/

1 0

[JIRA] (OVIRT-2621) setlocale warnings in mock logs
by Evgheni Dereveanchin (oVirt JIRA) 11 Dec '18

11 Dec '18

Evgheni Dereveanchin created OVIRT-2621: ------------------------------------------- Summary: setlocale warnings in mock logs Key: OVIRT-2621 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2621 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra There's a bunch of setlocale warnings in mock logs which didn't exist before: https://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-e… We need to verify what happened to get rid of these messages as they are distracting attention from real failure causes -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

Build failed in Jenkins: deploy-to_ovirt-4.2_tested #2665
by jenkins＠jenkins.phx.ovirt.org 11 Dec '18

11 Dec '18

See <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/2665/display/redire…> ------------------------------------------ Started by upstream project "ovirt-4.2_change-queue-tester" build number 3613 originally caused by: Started by upstream project "ovirt-4.2_change-queue" build number 10051 originally caused by: Started by upstream project "standard-enqueue" build number 17951 originally caused by: Triggered by Gerrit: https://gerrit.ovirt.org/96110 [EnvInject] - Loading node environment variables. Building remotely on vm0139.workers-phx.ovirt.org (phx fc28 nested) in workspace <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/> [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-RLP4yxreSRww/agent.11282 SSH_AGENT_PID=11284 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/@tmp/private_key…> (<http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/@tmp/private_key…)> [ssh-agent] Using credentials deploy-ovirt-experimental (SSH key for deploying to the tested repo) [deploy-to_ovirt-4.2_tested] $ /bin/bash -xe /tmp/jenkins764643349004539403.sh + [[ jenkins:http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-fc28-s390x/48/ jenkins:http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-el7-ppc64le/3… jenkins:http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-el7-x86_64/32… == '' ]] + queue_name=ovirt-4.2 + ssh -o StrictHostKeyChecking=no deploy-ovirt-experimental(a)resources.ovirt.org + echo repo-extra-dir:4.2 + echo 'jenkins:http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-fc28-s390x/48/ jenkins:http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-el7-ppc64le/3… jenkins:http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-el7-x86_64/32…' Pseudo-terminal will not be allocated because stdin is not a terminal. + BASE_DIR=/srv/resources/repos/ovirt/tested + PUBLISH_MD_COPIES=50 + main + local tmp_dir + mkdir -p /srv/resources/repos/ovirt/tested ++ mktemp -d /srv/resources/repos/ovirt/tested/.deploy.XXXXXXXXXX Collecting packages + tmp_dir=/srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G + trap 'rm -rf '\''/srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G'\''' EXIT HUP + echo 'Collecting packages' + collect_packages /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G + local repoman_dst=/srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G + repoman --temp-dir generate-in-repo --option main.allowed_repo_paths=/srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G --option main.on_empty_source=warn /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G add conf:stdin 2018-12-11 12:04:15,303::INFO::repoman.cmd:: 2018-12-11 12:04:15,304::INFO::repoman.cmd::Adding artifacts to the repo /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G 2018-12-11 12:04:15,304::INFO::repoman.common.repo::Adding repo extra dir 4.2 2018-12-11 12:04:15,307::INFO::repoman.common.stores.RPM::Loading repo /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G/4.2 2018-12-11 12:04:15,308::INFO::repoman.common.stores.RPM::Repo /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G/4.2 loaded 2018-12-11 12:04:15,310::INFO::repoman.common.stores.iso::Loading repo /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G/4.2 2018-12-11 12:04:15,310::INFO::repoman.common.stores.iso::Repo /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G/4.2 loaded 2018-12-11 12:04:15,324::INFO::repoman.common.repo::Resolving artifact source jenkins:http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-fc28-s390x/48/ 2018-12-11 12:04:15,519::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-fc28-s390x/48//api/js… Status: 404 Reason: Not Found Headers: {'cache-control': 'must-revalidate,no-cache,no-store', 'connection': 'close', 'content-length': '367', 'content-type': 'text/html;charset=iso-8859-1', 'date': 'Tue, 11 Dec 2018 12:04:15 GMT', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 404 Not Found</title> </head> <body><h2>HTTP ERROR 404</h2> <p>Problem accessing /job/vdsm_4.2_build-artifacts-fc28-s390x/48//api/json. Reason: <pre> Not Found</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/> </body> </html> 2018-12-11 12:04:17,579::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-fc28-s390x/48//api/js… Status: 404 Reason: Not Found Headers: {'cache-control': 'must-revalidate,no-cache,no-store', 'connection': 'close', 'content-length': '367', 'content-type': 'text/html;charset=iso-8859-1', 'date': 'Tue, 11 Dec 2018 12:04:17 GMT', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 404 Not Found</title> </head> <body><h2>HTTP ERROR 404</h2> <p>Problem accessing /job/vdsm_4.2_build-artifacts-fc28-s390x/48//api/json. Reason: <pre> Not Found</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/> </body> </html> 2018-12-11 12:04:19,640::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-fc28-s390x/48//api/js… Status: 404 Reason: Not Found Headers: {'cache-control': 'must-revalidate,no-cache,no-store', 'connection': 'close', 'content-length': '367', 'content-type': 'text/html;charset=iso-8859-1', 'date': 'Tue, 11 Dec 2018 12:04:19 GMT', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 404 Not Found</title> </head> <body><h2>HTTP ERROR 404</h2> <p>Problem accessing /job/vdsm_4.2_build-artifacts-fc28-s390x/48//api/json. Reason: <pre> Not Found</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/> </body> </html> 2018-12-11 12:04:21,702::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-fc28-s390x/48//api/js… Status: 404 Reason: Not Found Headers: {'cache-control': 'must-revalidate,no-cache,no-store', 'connection': 'close', 'content-length': '367', 'content-type': 'text/html;charset=iso-8859-1', 'date': 'Tue, 11 Dec 2018 12:04:21 GMT', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 404 Not Found</title> </head> <body><h2>HTTP ERROR 404</h2> <p>Problem accessing /job/vdsm_4.2_build-artifacts-fc28-s390x/48//api/json. Reason: <pre> Not Found</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/> </body> </html> 2018-12-11 12:04:23,705::ERROR::repoman.cmd:: 2018-12-11 12:04:23,706::ERROR::repoman.cmd::Error while adding conf:stdin 2018-12-11 12:04:23,707::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G/.lago_tmp/tmplwBoGm/tmp3mvPAy 2018-12-11 12:04:23,708::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G/.lago_tmp/tmplwBoGm + rm -rf /srv/resources/repos/ovirt/tested/.deploy.NPsAUgy36G Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 11284 killed; [ssh-agent] Stopped.

1 1

[JIRA] (OVIRT-2613) add_host fails on master and 4.2 ovirt due to missing deps
by Dafna Ron (oVirt JIRA) 11 Dec '18

11 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2613?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2613: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > add_host fails on master and 4.2 ovirt due to missing deps > ---------------------------------------------------------- > > Key: OVIRT-2613 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2613 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_lago, ost_packages > > Gal Ben Haim > > 9:28 AM (3 hours ago) > > to rhv-devops, RHV-CI > We are going to rebase [1] which will solve the deps error. > We need to replace the image otherwise add_host fails with a segmentation fault. > An image from virt-builder probably won't be available today, so we will build our own el7.6 image. > [1] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11873/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2618) ovirt-4.2 is failing on host deploy on missing packages
by Dafna Ron (oVirt JIRA) 11 Dec '18

11 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2618?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2618: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt-4.2 is failing on host deploy on missing packages > -------------------------------------------------------- > > Key: OVIRT-2618 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2618 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_packages > > the issue is in the upgrade-from-release-4.2 and we are missing packages in host-deploy: > {noformat} > 2018-12-06 12:38:23,711-0500 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Building transaction > 2018-12-06 12:38:25,102-0500 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:85 Yum [u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libepoxy.so.0()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libgbm.so.1()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libibumad.so.3()(64bit)'] > 2018-12-06 12:38:25,102-0500 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-gHBVKbY3Pr/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-gHBVKbY3Pr/otopi-plugins/otopi/packagers/yumpackager.py", line 248, in _packages > self.processTransaction() > File "/tmp/ovirt-gHBVKbY3Pr/otopi-plugins/otopi/packagers/yumpackager.py", line 262, in processTransaction > if self._miniyum.buildTransaction(): > File "/tmp/ovirt-gHBVKbY3Pr/pythonlib/otopi/miniyum.py", line 920, in buildTransaction > raise yum.Errors.YumBaseError(msg) > YumBaseError: [u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libepoxy.so.0()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libgbm.so.1()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libibumad.so.3()(64bit)'] > 2018-12-06 12:38:25,103-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Package installation': [u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libepoxy.so.0()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libgbm.so.1()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libibumad.so.3()(64bit)'] > 2018-12-06 12:38:25,126-0500 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: > id uid local foreign state pid exe > 0: 0 0.0.0.0:22 0.0.0.0:0 LISTEN 3327 /usr/sbin/sshd > 1: 0 192.168.200.3:22 192.168.200.2:38628 ESTABLISHED 3606 /usr/sbin/sshd > 2018-12-06 12:38:25,127-0500 DEBUG otopi.transaction transaction.abort:119 aborting 'Yum Transaction' > 2018-12-06 12:38:25,127-0500 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum Performing yum transaction rollback > Loaded plugins: fastestmirror > {noformat} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 95757,10 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 11 Dec '18

11 Dec '18

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

2 1

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-el7-x86_64 - Build # 136 - Still Failing!
by jenkins＠jenkins.phx.ovirt.org 11 Dec '18

11 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7… Build Number: 136 Build Status: Still Failing Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #133 [Yuval Turgeman] stdci: move build-artifacts to a v1 job [Evgheni Dereveanchin] Add distribution-gpg-keys to global_setup Changes for Build #134 [Yuval Turgeman] stdci: move build-artifacts to a v1 job [Galit Rosenthal] Remove from lago fc27-EOL Changes for Build #135 [Yuval Turgeman] stdci: move build-artifacts to a v1 job [Ehud Yonasi] mirror-reposync: remove gluster-3.10 mirror [Ehud Yonasi] sync_mirros: remove gluster-3.10 mirror. Changes for Build #136 [Yuval Turgeman] stdci: move build-artifacts to a v1 job [Eyal Edri] the CI system is low on resources, moving suites to run only once a day [Daniel Belenky] docker_cleanup: add cleanup for volumes [Liora Milbaum] remove infra(a)ovirt.org from unrelated jobs [Daniel Belenky] dsl: add support for specific hardware support ----------------- Failed Tests: ----------------- No tests ran.

1 5

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #1995
by jenkins＠jenkins.phx.ovirt.org 11 Dec '18

11 Dec '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ 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-kvm-common-el7-x86_…> > 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/changes/59/95959/1:test --prune > git rev-parse origin/test^{commit} # timeout=10 > git rev-parse test^{commit} # timeout=10 Checking out Revision 05b40dfb4ec43a82530e8c471395d1858e5c59e1 (test) > git config core.sparsecheckout # timeout=10 > git checkout -f 05b40dfb4ec43a82530e8c471395d1858e5c59e1 Commit message: "mirror-reposync: remove gluster-3.10 mirror" > git rev-list --no-walk 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2623931369959497695.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-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-kvm-common-el7/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7/gen' Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt-node-ng_4.2_build-artifacts-el7-x86_64 - Build # 274 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 Dec '18

11 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/2… Build Number: 274 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #274 [Ryan Barry] kickstart: let VDSM reconfigure itself ----------------- Failed Tests: ----------------- No tests ran.

1 14

[JIRA] (OVIRT-2620) Mirroring error
by sbonazzo (oVirt JIRA) 11 Dec '18

11 Dec '18

sbonazzo created OVIRT-2620: ------------------------------- Summary: Mirroring error Key: OVIRT-2620 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2620 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra *Hi,* *looks like in our mirror script there's a bug, we don't clean the <repo>/gen directory before starting the mirroring* *04:35:12* yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-kvm-common-el7/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7/gen' Job: https://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86… -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: d9b8189 (ovirt-ansible-infra) failed "ovirt-master" system tests
by oVirt Jenkins 11 Dec '18

11 Dec '18

Change d9b8189 (ovirt-ansible-infra) 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://github.com/oVirt/ovirt-ansible-infra/commit/d9b818927946d89bc2bb874… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11948/

1 0

oVirt infra daily report - unstable production jobs - 670
by jenkins＠jenkins.phx.ovirt.org 11 Dec '18

11 Dec '18

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/670//artifact/exported-a… Cheers, Jenkins

1 0