March 2017 - Devel - oVirt List Archives

Lowering the bar for wiki contribution?
by Roy Golan 22 Jun '17

22 Jun '17

I'm getting the feeling I'm not alone in this, authoring and publishing a wiki page isn't as used to be for long time. I want to suggest a bit lighter workflow: 1. Everyone can merge their page - (it's a wiki) Same as with (public and open) code, no one has the motivation to publish a badly written wiki page under their name. True, it can have an impact, but not as with broken code 2. Use Page-Status marker The author first merges the draft. Its now out there and should be updated as time goes and its status is DRAFT. Maintainers will come later and after review would change the status to PUBLISH. That could be a header in on the page: --- page status: DRAFT/PUBLISH --- Simple I think, and should work.

14 23

[ OST Failure Report ] [ oVirt 4.1 ] [ 23-03-2017 ] [ 002_bootstrap.add_secondary_storage_domains ]
by Shlomo Ben David 20 Apr '17

20 Apr '17

Hi, Test failed: [ 002_bootstrap.add_secondary_storage_domains ] Link to suspected patches: N/A Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1054 Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1054/artifact… Error snippet from the log: <error> 2017-03-23 07:23:38,867-0400 ERROR (jsonrpc/2) [storage.TaskManager.Task] (Task='8347d74c-92fe-4371-bc84-1314a43a2971') Unexpected error (task:870) Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 877, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 52, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 1159, in attachStorageDomain pool.attachSD(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/share/vdsm/storage/sp.py", line 924, in attachSD dom = sdCache.produce(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 112, in produce domain.getRealDomain() File "/usr/share/vdsm/storage/sdc.py", line 53, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 136, in _realProduce domain = self._findDomain(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 153, in _findDomain return findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 178, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'127fbe66-204c-4c6d-b521-d0f431af2b6c',) </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCVA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

2 1

[OST] [HC] HE VM fails to start
by Sahina Bose 06 Apr '17

06 Apr '17

The error in vdsm.log Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 2016, in _setup_devices dev_object.setup() File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/graphics.py", line 63, in setup net_api.create_libvirt_network(display_network, self.conf['vmId']) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 90, in create_libvirt_network libvirt.create_network(netname, user_reference) File "/usr/lib/python2.7/site-packages/vdsm/network/libvirt.py", line 94, in create_network if not is_libvirt_network(netname): File "/usr/lib/python2.7/site-packages/vdsm/network/libvirt.py", line 159, in is_libvirt_network netname = LIBVIRT_NET_PREFIX + netname TypeError: cannot concatenate 'str' and 'NoneType' objects 2017-03-29 22:58:39,559-0400 ERROR (vm/d71bdf4e) [virt.vm] (vmId='d71bdf4e-1eb3-4762-bd0e-05bb9f5e43ef') The vm start process failed (vm:659) The tests last passed on Mar 28. Did a recent patch break this? The full build logs at http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/52/artifact/expor… thanks sahina

4 12

Firewalld migration.
by Leon Goldberg 06 Apr '17

06 Apr '17

Hey, We're looking to migrate from iptables to firewalld. We came up with a couple of possible approaches we'd like opinions on. I'll list the options first, and will 1) Replicate existing flow: As of date, iptable rules are inserted in the database via SQL config files. During host deployment, VdsDeployIptablesUnit adds the required rules (based on cluster/firewall configuration) to the deployment configuration, en route to being deployed on the host via otopi and its iptables plugin. Pros: - Reuse of existing infrastructure. Cons: - Current infrastructure is overly complex... - Many of the required services are provided by firewalld. Rewriting them is wasteful; specifying them (instead of providing actual service .xml content) will require adaptations on both (engine/host) sides. More on that later. 2) Host side based configuration: Essentially, all the required logic (aforementioned cluster/firewall configuration) to determine if/how firewalld should be deployed could be passed on to the host via ohd. Vdsm could take on the responsibility of examining the relevant configuration, and then creating and/or adding the required services (using vdsm.conf and vdsm-tool). Pros: - Engine side involvement is greatly diminished. - Simple(r). Cons: - Custom services/rules capabilities will have to be rethought and re-implemented (current infrastructure supports custom iptables rules by being specified in the SQL config file). 3) Some other hybrid approach: If we're able to guarantee all the required firewalld services are statically provided one way or the other, the current procedure could be replicated and be made more simpler. Instead of providing xml content in the form of strings, service names could be supplied. The responsibility of actual service deployment becomes easier, and could be left to otopi (with the appropriate modifications) or switched over to vdsm. -- Regardless, usage of statically provided vs. dynamically created services remains an open question. I think we'd like to avoid implementing logic that ask whether some service is provided (and then write it if it isn't...), and so choosing between the dynamic and static approaches is also needed. Using the static approach, guaranteeing *all* services are provided will be required. I do believe guaranteeing the presence of all required services is worth it, however custom services aren't going to be naively compatible, and we'll still have to use similar mechanism as described in #1 (service string -> .xml -> addition of service name to active zone). Your thoughts are welcome. Thanks, Leon

10 37

Live demo session on how to debug oVirt GWT applications
by Vojtech Szocs 04 Apr '17

04 Apr '17

Hello UI devs, with oVirt master UI using the latest GWT SDK [1], I'd like to host a live demo session with two goals in mind: a, explain how the (Java IDE based) Classic Dev Mode works and mention its limitations b, explain how the (browser based) Super Dev Mode works and encourage people to start using it to boost their productivity [1] http://www.mail-archive.com/devel@ovirt.org/msg08558.html The Classic vs. Super Dev Mode are two possible ways to debug GWT applications. This session will give you the knowledge to decide which one to use in a specific situation. Proposed time: Mon, Apr 3 @ 5pm CET / 6pm TLV / 11am US EST. (This can be changed as needed.) Let me know if this kind of session interests you or if the above time doesn't fit you but you'd still like to join. Thanks, Vojtech

2 5

oVirt master UI now uses GWT 2.8
by Vojtech Szocs 02 Apr '17

02 Apr '17

Hello folks, we're using the latest GWT version in master UI now [1]. We can start using Java 8 syntax in our frontend code. GWT 2.8 also brings partial support for Java 8 standard library APIs, see "JDK emulation" at [2] for details. [1] https://gerrit.ovirt.org/#/q/topic:gwtupgrade [2] http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0_RC1 Effectively, all Engine (Java Maven) modules [3] are now Java 8 source & target compilant. [3] except backend/manager/modules/extensions-api-root With this upgrade, the GWT UI should be a bit faster - generated JavaScript should take advantage of new web APIs (e.g. using ES6 Maps to implement Java HashMap) as well as general performance improvements (e.g. using a faster "long" emulation). GWT 2.8 removes deRPC (direct-eval RPC) mechanism but that's OK because we're already using the standard GWT RPC [4]. [4] https://gerrit.ovirt.org/#/c/65735/ There are no changes to existing build & development process: - debugging via Java IDE (aka Classic Dev Mode) remains the default debug method - debugging via browser (aka Super Dev Mode) can be enabled via DEV_BUILD_GWT_SUPER_DEV_MODE flag [5] [5] example: $ make gwt-debug DEBUG_MODULE=webadmin DEV_BUILD_GWT_SUPER_DEV_MODE=1 Note that in GWT 2.8 the Super Dev Mode is the new default debug method (with Classic Dev Mode being deprecated). There are still some post-upgrade tasks to do, we're tracking them on Trello: https://trello.com/b/o26RrVLz/post-gwt-2-8-upgrade-tasks If you encounter any issues related to GWT compilation or debugging, let me know. Regards, Vojtech

2 1

Re: [ovirt-devel] Interest in contributing to oVirt
by Konrad Djimeli 31 Mar '17

31 Mar '17

Hello Yaniv, Thanks very much for the response. I am currently trying to develop a proposal for this project but I have not yet been able to successfully setup oVirt. I just realized I could not install the oVirt-engine an Ubuntu 14, so I am currently trying to download and install Fedora 23, where I intend to setup the oVirt-engine. I would then use another machine with Ubuntu for the host. Please with respect to this project I would like to know if I am also required compile and install the source code for oVirt-engine or do I only need to build and install ovirt4cli. Thanks Konrad On 17 March 2017 at 20:26, Yaniv Kaul <ykaul(a)redhat.com> wrote: > Hi Konrad, > > I'm very happy to hear that and wish you good luck with the project. > > I think it'd be best if you can begin with familiarizing yourself with > oVirt. > If you have few computers around, it should be fairly easy to set it up. If > you have a single computer, you can set up Lago[1] and ovirt-system-test[2] > to bring up an environment as well. > > The (very basic) code for ovirt4cli is available on my github[3] - I have > just created a very basic framework as a proof of concept - feel free to > fork and modify it. Specifically, I think we should re-work it to share more > code with our Ansible code[4]. > > Let me know if there's anything I can help you with in the project! > Y. > > [1] http://lago.readthedocs.io/en/stable/ > [2] http://ovirt-system-tests.readthedocs.io/en/latest/ > [3] https://github.com/mykaul/ovirt4cli > [4] > https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/ovir… > > > On Fri, Mar 17, 2017 at 9:06 AM, Konrad Djimeli <djkonro35(a)gmail.com> wrote: >> >> Hello, >> >> My name is Konrad Djimeli a third year Computer Science Student at the >> University of Buea, Cameroon. I am interested in contributing to oVirt >> and I would like to work on the Google Summer of Code project >> "ovirt4cli". I am very comfortable working with Python and I have >> experience working with web services like REST. >> >> Please I would appreciate any suggestion on how to get started and to >> better familiarize myself with the project. >> >> >> Thanks >> Konrad >> http://djimeli.me/ > >

2 2

[ANN] oVirt 4.1.1 Async release candidate
by Sandro Bonazzola 30 Mar '17

30 Mar '17

Hi, following oVirt 4.1.1 GA the oVirt team identified some bugs worth to be addressed out of the usual release cycle. For this reason an async release including these fixes is under preparation. An update to the following packages have been pushed to the pre-release repository for testing. - ovirt-engine-4.1.1.7 - vdsm-4.19.10.1 - ovirt-release41-4.1.1.1_rc1 - ovirt-web-ui-0.1.2-4 - cockpit-ovirt-0.10.7-0.0.16 In order to test it, you'll need pre-release repository enabled: yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release41-pre.rpm An update to release notes including bugs related to above packages and updates applied in bugzilla documentation texts has been pushed to https://github.com/oVirt/ovirt-site/pull/888 for review. On behalf of the oVirt team, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[OST failure report] vdsmfake doesn't produce artifacts
by Pavel Zhukov 30 Mar '17

30 Mar '17

Hello, Vdsmfake doesn't build any installable artifacts and deploy-to* job fails because of this. Example: See <http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/14413> Can someone take a look please? -- Pavel Zhukov Software Engineer

2 1

Writing SQL queries in DAO code
by Yevgeny Zaspitsky 30 Mar '17

30 Mar '17

Hi All, Recently I had a task of performance improvement in one of our network related flows and had some hard time following our DAL code and one of the outcomes of the task was defining a couple of new quite simple, but neat queries. When I came to coding those new queries I remembered how hard was following the existing DAL code, I decided to make my own new methods clearer. So I created [1] and [2] patches. Everything is quite standard there beside the fact that they do not use any stored procedure, but use SQL directly, IMHO by that they save time that I spent in trying to follow what a DAO method does. Looking into the method code you get the understanding of what this method is all about: - no looking for a stored procedure name that is buried in the DAO class hierarchy - no looking for the SP definition So I'd like to propose moving towards this approach in general in all cases when nothing beyond a simple SQL is needed (no stored procedure programming language is needed). >From my experience with the performance improvement task it looks like people avoid adding new queries for a specific need of a flow, instead they use the existing general ones (e.g. dao.getAllForX()) and do the actual join in the bll code. IMHO the proposed approach would simplify adding new specific queries and by that would prevent a decent part of performance issues in the future. I do not propose changing all existing SP's to inline queries in a once, but to allow adding new queries this way. Also we might consider converting relatively simple SP's to inline SQL statements later in a graduate way. [1] - https://gerrit.ovirt.org/#/c/74456 [2] - https://gerrit.ovirt.org/#/c/74458 Regards, Yevgeny

5 12

[ Announcment ] STD CI now supports custom junit reports
by Daniel Belenky 29 Mar '17

29 Mar '17

Hi all, The oVirt infra team is proud to announce that as from today the standard ci supports export of custom junit reports. *How to use?* Simply generate your junit .xml files, and follow the following naming: *<your_custom_name>.junit.xml. *Make sure you move them to exported-artifacts directory. That's all, the std ci will collect your .junit.xml files, and generate the junit report for you. Please feel free to contact the infra team on infra(a)ovirt.org for any more questions you have. Sincerely, -- *Daniel Belenky* *RHV DevOps* *Red Hat Israel*

1 0

Wildfly 11.0.0 Alpha is out
by Sandro Bonazzola 29 Mar '17

29 Mar '17

Hi, just an heads up that Wildfly 11.0.0 Alpha is out so we can start looking at it for master http://wildfly.org/downloads/ Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12313721&version… -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

ovirt guest agent and local address
by Marc Young 29 Mar '17

29 Mar '17

Is there a way to manually blacklist a range from being submitted via the ovirt guest agent? The reason I ask, 169.x and 127.0.0.1 never display, but if you're running docker, the agent submits the docker host address (172.17.0.1) RFC1918 defines local address and contains 172.16.0.0/12, which includes 172.17.0.0/16 (it ranges from 172.16.0.0 to 172.31.255.255), so it seems valid, but the UI displays "IP Address" (not plural) Is there anything I can do to prevent this IP from submitting? Screen shot attached. Guest agent info: Operating System: CentOS Linux 7.3.1611 (Core) Kernel Version: 3.10.0-514.el7.x86_64

2 2

oVirt Engine checkstyle upgrade
by Allon Mureinik 28 Mar '17

28 Mar '17

Hi all, As per [1], I've just merged a series of patches that upgrades the oVirt engine to use the latest maven-checkstyle-plugin and checkstyle packages. Please note that the newer checkstyle is a tad stricter than the old one we used to have (read: it contains several fixes for bugs where the old checkstyle was supposed to find issues but missed them). I also took the opportunity and added a couple of new checks that enforce rules we were de-facto adhering to anyway. If any problems come up, please let me know. -Your friendly neighborhood cleanup dude [1] https://bugzilla.redhat.com/show_bug.cgi?id=1433408

5 12

planned Jenkins restart
by Evgheni Dereveanchin 28 Mar '17

28 Mar '17

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new builds will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin

1 1

REST API data aggregation
by Tomas Jelinek 27 Mar '17

27 Mar '17

Hi All, for quite some time I have been more or less involved in development of various UIs for oVirt based entirely on the oVirt's REST API ranging from the quite mature moVirt [1] through some cockpit extensions to a young and experimental user portal replacement [2]. One issue we hit over and over again is the missing data aggregation. In the 3.x era we used to use in moVirt the detail=something api to get the disks and nics of the VM, something like: GET /ovirt-engine/api/vms Accept: application/json; detail=disks This allowed us to store this data in local database leading to great user experience. Since this feature has been removed in 4.x API [3] we needed to retire to a different solution. When the VM detail is selected by the user, start loading the disks and nics and hope the user will not be fast enough to see the delay. The UX is slightly worse bug kinda acceptable. We hit this issue harder in the new user portal [2], because we already have the VM cached and show the whole VM in one screen. So, if you pick it, you will get it's details immediately. But, since you don't have all the details, we need to do an additional call (two actually) to load this data and they start to appear later. So, something which would be very fast and smooth starts to feel sluggish. Recently, we hit this issue again which forced us to sacrifice the UX even more - it is the "console in use" feature of user portal. The use case is this: - if the console is already taken by some user, there are complications if other current user tryes to take it as well (will avoid details about settings and permissins involved, but long story short, the user will probably not be allowed to connect to it. The "probably" is the key here since we can not do any intelligent decision in advance, we can only warn the user that the console is taken). - in the current GWT user portal, if the VM's console is taken, it is shown on the VM's "box" that "console is taken". This was a highly requested feature - to get this information using the current REST API, we need to go to the /vms/<vmid>/sessions subcollection. To get this for all VMs, it would be doing N queries per poll which we can not afford - so the current PR [4] will probably end up to only check it on the attempt to connect to the console warning the user. Maybe it will be also shown in Vm details. But the UX in case the user will look for a VM which has free console will suffer significantly (e.g. try one by one until some opens or look at details one by one to see if the warning appears (with a delay)) I understand that embedding the details of the VM to the response comes with a cost, namely: - performance hit - complexity of the API code - the "cleanness" of REST suffers But I think we should seriously consider to provide some option to data aggregation. I know this has been discussed many times with no result, but I think it is time to bring this topic up again. I'll try to summarize the (failed) attempts tried so far: - the detail=<something> parameter with ad-hoc embedding of data. This has been there and removed in 4.0 [3] - the DoctorREST project - e.g. a proxy above the current api. The idea was to create a service which will be independent of the engine itself, will locally poll the engine's REST, store all data in local (mongo)DB and provide a rich api with aggregations and projections and push notifications. This polling of everything to get the data to DoctorREST proved to be pretty costy, so also a more invasive approach of pushing data from engine to doctor has been discused [5]. None of this two approaches have been accepted (too complicated, too invasive). - writing some custom ad-hoc servlet serving only a purpose of one frontend - this is actually there for the dashboard, but it is not a generic solution for the other frontends and we really should not develop custom "APIs" for every frontend - there were some other proposals discussed (some 3th party solutions etc) but I think none of them made it even to a PoC So, now I would try again and try small to get at least some benefit. I see 2 paths we could try: 1: embed something which burns us immediatly, e.g. the /sessions into VMs. I really liked the ;detail=sessions approach, could we move it back? 2: add some tiny service which would just accept a list of queries, execute them locally (but using real HTTP requests) and return in one bulk. A naive implementation just to give a sense of what I mean of this would be a shell script getting list of strings like " https://localhost/ovirt-engine/api/vms/123/sessions" iterate over them and do a curl request for each, mangle the results into one string and return (credits for this idea to msivak). Easy to implement, possibility to add also projections later to save some bandwidth. But the API would anyway be hammered by bunch of queries, only the network roundtrip would be saved. 3: any other simple approaches? I honestly prefer the first approach. It is not beautiful, it is not REST-ful, but it is easy to implement, very pragmatic and useful. What do you think? Thank you and sorry for the long mail :) Tomas [1]: https://github.com/oVirt/moVirt [2]: https://github.com/oVirt/ovirt-web-ui [3]: https://gerrit.ovirt.org/#/c/61260 [4]: https://github.com/oVirt/ovirt-web-ui/pull/106/ [5]: https://gerrit.ovirt.org/#/c/45233/

7 15

[ OST Failure Report ] [ oVirt 4.1 ] [ 21-03-2017 ] [ test-repo_ovirt_experimental_4.1 ]
by Shlomo Ben David 27 Mar '17

27 Mar '17

Hi, Test failed: [ test-repo_ovirt_experimental_4.1 ] Link to suspected patches: N/A Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1018 Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1018/artifact… Error snippet from the log: <error> ifup/VLAN100_Network::DEBUG::2017-03-21 06:12:03,550::commands::93::root::(execCmd) FAILED: <err> = 'Running scope as unit 979f3d61-c1f9-49c2-b168-799b882f64d5.scope.\n/etc/sysconfig/network-scripts/ifup-eth: line 297: 30633 Terminated /sbin/dhclient ${DHCLIENTARGS} ${DEVICE}\nCannot find device "VLAN100_Network"\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice ... ... ... "VLAN100_Network" does not exist.\n'; <rc> = 1 ifup/VLAN100_Network::ERROR::2017-03-21 06:12:03,551::utils::371::root::(wrapper) Unhandled exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 368, in wrapper return f(*a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 180, in run return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 924, in _exec_ifup _exec_ifup_by_name(iface.name, cgroup) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 910, in _exec_ifup_by_name raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '') ConfigNetworkError: (29, 'Determining IPv6 information for VLAN100_Network... failed.') </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCVA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

3 2

vdsm-hook-ovs dependency
by Daniel Belenky 27 Mar '17

27 Mar '17

Hi all, I try to test our master tested repo for repoclosure, and the test fails on the following dependency: 10:44:49 package: vdsm-hook-ovs-4.20.0-162.gitcc43be6.el7.centos.noarch from internal_repo 10:44:49 unresolved deps: 10:44:49 vdsm = 0:4.20.0-162.gitcc43be6.el7.centos When looking at the last builds of VDSM, I could not find this package: *vdsm-hook-ovs* in the 'exported artifacts'. Can someone advise where this package is coming from? Do we need this package? Thanks, -- *Daniel Belenky* *RHV DevOps* *Red Hat Israel*

2 2

master branch host installation fails in ovirt-system-tests - regression due to ABRT integration?
by Yaniv Kaul 27 Mar '17

27 Mar '17

2017-03-26 09:50:47,235-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [2c34dfce] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), Correlation ID: 2c34dfce, Call Stack: null, Custom Event ID: -1, Message: Failed to install Host lago-basic-suite-master-host1. Failed to execute stage 'Package installation': [u'vdsm-4.20.0-542.git93156a7.el7.centos.x86_64 requires abrt-addon-vmcor e', u'vdsm-4.20.0-542.git93156a7.el7.centos.x86_64 requires abrt-addon-ccpp', u'vdsm-4.20.0-542.git93156a7.el7.centos.x86_64 requires abrt-addon-python'].

2 1

[ OST Failure Report ] [ oVirt 4.1 ] [ 24-03-2017 ] [ 002_bootstrap.list_glance_images ]
by Shlomo Ben David 27 Mar '17

27 Mar '17

Hi, Test failed: [ 002_bootstrap.list_glance_images ] Link to suspected patches: N/A Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1063 Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1063/artifact… Error snippet from the log: <error> 2017-03-24 08:04:46,983-04 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (org.ovirt.thread.pool-7-thread-1) [2b2b4693] Command 'PollVDSCommand(HostName = lago-basic-suite-4-1-host1, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='746e816f-6e21-4185-9d50-3e90ebefb187'})' execution failed: VDSGenericException: VDSNetworkException: Timeout during rpc call 2017-03-24 08:04:46,983-04 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (org.ovirt.thread.pool-7-thread-1) [2b2b4693] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Timeout during rpc call at org.ovirt.engine.core.vdsbroker.vdsbroker.FutureVDSCommand.get(FutureVDSCommand.java:73) [vdsbroker.jar:] at org.ovirt.engine.core.bll.network.host.HostSetupNetworkPoller.getValue(HostSetupNetworkPoller.java:56) [bll.jar:] at org.ovirt.engine.core.bll.network.host.HostSetupNetworkPoller.poll(HostSetupNetworkPoller.java:41) [bll.jar:] at org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand.invokeSetupNetworksCommand(HostSetupNetworksCommand.java:426) [bll.jar:] at org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand.executeCommand(HostSetupNetworksCommand.java:287) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1251) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1391) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2055) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:164) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:103) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1451) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:397) [bll.jar:] at org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute(DefaultBackendActionExecutor.java:13) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runAction(Backend.java:511) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:493) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:697) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_121] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121] at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:70) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:80) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:374) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:243) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) at org.ovirt.engine.core.bll.interfaces.BackendInternal$$$view5.runInternalAction(Unknown Source) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_121] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121] at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:433) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:128) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.ovirt.engine.core.bll.BackendCommandObjectsHandler$BackendInternal$BackendLocal$2049259618$Proxy$_$$_Weld$EnterpriseProxy$.runInternalAction(Unknown Source) [bll.jar:] at org.ovirt.engine.core.bll.network.NetworkConfigurator.configureManagementNetwork(NetworkConfigurator.java:230) [bll.jar:] at org.ovirt.engine.core.bll.network.NetworkConfigurator.createManagementNetworkIfRequired(NetworkConfigurator.java:85) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.configureManagementNetwork(InstallVdsInternalCommand.java:219) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.installHost(InstallVdsInternalCommand.java:181) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.executeCommand(InstallVdsInternalCommand.java:87) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1251) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1391) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2055) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:164) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:103) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1451) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:397) [bll.jar:] at org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute(DefaultBackendActionExecutor.java:13) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runAction(Backend.java:511) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:493) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:697) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_121] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121] at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:70) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:80) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:374) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:243) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) at org.ovirt.engine.core.bll.interfaces.BackendInternal$$$view5.runInternalAction(Unknown Source) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_121] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121] at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:433) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:128) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.ovirt.engine.core.bll.BackendCommandObjectsHandler$BackendInternal$BackendLocal$2049259618$Proxy$_$$_Weld$EnterpriseProxy$.runInternalAction(Unknown Source) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInternalAction(CommandBase.java:2452) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand.lambda$executeCommand$2(AddVdsCommand.java:186) [bll.jar:] at org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$InternalWrapperRunnable.run(ThreadPoolUtil.java:92) [utils.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_121] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121] 2017-03-24 08:04:46,991-04 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (org.ovirt.thread.pool-7-thread-1) [2b2b4693] Timeout waiting for VDSM response: Internal timeout occured </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCVA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

3 3

[ OST Failure Report ] [ oVirt 4.1 && oVirt master ] [ 20-03-2017 ] [ 004_basic_sanity.snapshots_merge ]
by Shlomo Ben David 27 Mar '17

27 Mar '17

Hi, Test failed: [ 004_basic_sanity.snapshots_merge ] Link to suspected patches: N/A Link to Job: 1. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1007 2. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5918 Link to all logs: 1. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1007/artifact… 2. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5918/artif… Error snippet from the log: <error> ovirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x446a758> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within res = func() File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/004_basic_sanity.py", line 449, in <lambda> api.vms.get(VM0_NAME).disks.get(disk_name).status.state == 'ok' AttributeError: 'NoneType' object has no attribute 'state' lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/004_basic_sanity.py", line 448, in snapshot_live_merge lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 264, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 251, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within res = func() File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/004_basic_sanity.py", line 449, in <lambda> api.vms.get(VM0_NAME).disks.get(disk_name).status.state == 'ok' AttributeError: 'NoneType' object has no attribute 'state' </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCVA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

5 5

Gsoc proposal on Configuring backup storage in ovirt
by shubham dubey 26 Mar '17

26 Mar '17

Hello, I have created the draft proposal recently on Configuring backup storage in ovirt.Here is the link to view https://docs.google.com/document/d/1orulgCTY1K6jUmomCIgZHA0g9xsWWUqttj0c1R0… . Any suggestion or comments are welcome. Thanks, Shubham Dubey

3 5

Fwd: Question for oVirt
by jeff hsueh 26 Mar '17

26 Mar '17

Hi Devel, Could you help to give me some detail information about this feature? Thanks. Jeff ---------- Forwarded message ---------- From: Mike Burns <mburns(a)redhat.com> Date: 2017-03-20 20:44 GMT+08:00 Subject: Re: Question for oVirt To: jeff hsueh <jeffhsueh(a)qnap.com> This is very old (last update 2012). I haven't worked on oVirt in a long time either. You should redirect this and other questions to devel(a)ovirt.org. Thanks On Mon, Mar 20, 2017 at 4:56 AM, jeff hsueh <jeffhsueh(a)qnap.com> wrote: > Hi Mike, > > I am studying "NetworkManager Support" of oVirt project. > Link: http://www.ovirt.org/develop/release-management/featur > es/network/networkmanager-support/ > > I could not understand what does this feature want to achieve. > Could I get more information and status about this feature from you? > Because the information about this feature in oVirt web site is too brief. > > Thanks. > > Jeff > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > 不含病毒。www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_-8795404721952800494_m_4727600564310439803_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >

2 1

[ OST Failure Report ] [ oVirt master ] [ 24-03-2017 ] [ 002_bootstrap.list_glance_images ]
by Shlomo Ben David 26 Mar '17

26 Mar '17

Hi, Test failed: [ 002_bootstrap.list_glance_images ] Link to suspected patches: N/A Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5997 Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5997/artif… Error snippet from the log: <error> 2017-03-23 20:19:39,699-04 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (org.ovirt.thread.pool-7-thread-2) [796c74] Command 'PollVDSCommand(HostName = lago-basic-suite-master-host1, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='e8fa4803-7372-41d9-b5a5-848d08773479'})' execution failed: VDSGenericException: VDSNetworkException: Timeout during rpc call 2017-03-23 20:19:39,699-04 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (org.ovirt.thread.pool-7-thread-2) [796c74] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Timeout during rpc call at org.ovirt.engine.core.vdsbroker.vdsbroker.FutureVDSCommand.get(FutureVDSCommand.java:74) [vdsbroker.jar:] at org.ovirt.engine.core.bll.network.host.HostSetupNetworkPoller.getValue( HostSetupNetworkPoller.java:56) [bll.jar:] at org.ovirt.engine.core.bll.network.host.HostSetupNetworkPoller.poll( HostSetupNetworkPoller.java:41) [bll.jar:] at org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand. invokeSetupNetworksCommand(HostSetupNetworksCommand.java:422) [bll.jar:] at org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand. executeCommand(HostSetupNetworksCommand.java:290) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1253) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1393) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2057) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport. executeInSuppressed(TransactionSupport.java:164) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport. executeInScope(TransactionSupport.java:103) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1453) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:397) [bll.jar:] at org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute( DefaultBackendActionExecutor.java:13) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runAction(Backend.java:496) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:478) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:684) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_121] at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121] at org.jboss.as.ee.component.ManagedReferenceMethodIntercep tor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation. proceed(InterceptorContext.java:437) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception( Jsr299BindingsInterceptor.java:70) [wildfly-weld-10.1.0.Final. jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception( Jsr299BindingsInterceptor.java:80) [wildfly-weld-10.1.0.Final. jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation( Jsr299BindingsInterceptor.java:93) [wildfly-weld-10.1.0.Final. jar:10.1.0.Final] at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1. processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor. processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation. proceed(InterceptorContext.java:437) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivat ionInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInter ceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor. processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InitialInterceptor.processInvocation( InitialInterceptor.java:21) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation( ChainedInterceptor.java:61) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor .processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAsso ciationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:374) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:243) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterc eptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor. processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-10.1.0.Final. jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation( SecurityContextInterceptor.java:100) [wildfly-ejb3-10.1.0.Final. jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor. processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1. processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor. processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-10.1.0.Final. jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation( NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation( ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.wildfly.security.manager.WildFlySecurityManager.doChecked( WildFlySecurityManager.java:636) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation( AccessCheckingInterceptor.java:61) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation( PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation( ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee.component.ViewDescription$1.processInvocation( ViewDescription.java:185) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation( ChainedInterceptor.java:61) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke( ProxyInvocationHandler.java:73) at org.ovirt.engine.core.bll.interfaces.BackendInternal$$$ view4.runInternalAction(Unknown Source) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_121] at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121] at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:433) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke( EnterpriseBeanProxyMethodHandler.java:128) [weld-core-impl-2.3.5.Final. jar:2.3.5.Final] at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke( EnterpriseTargetBeanInstance.java:56) [weld-core-impl-2.3.5.Final. jar:2.3.5.Final] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.ovirt.engine.core.bll.BackendCommandObjectsHandler$ BackendInternal$BackendLocal$2049259618$Proxy$_$$_Weld$EnterpriseProxy$.runInternalAction(Unknown Source) [bll.jar:] at org.ovirt.engine.core.bll.network.NetworkConfigurator. configureManagementNetwork(NetworkConfigurator.java:230) [bll.jar:] at org.ovirt.engine.core.bll.network.NetworkConfigurator. createManagementNetworkIfRequired(NetworkConfigurator.java:85) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand. configureManagementNetwork(InstallVdsInternalCommand.java:219) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand. installHost(InstallVdsInternalCommand.java:181) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand. executeCommand(InstallVdsInternalCommand.java:87) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1253) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1393) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2057) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport. executeInSuppressed(TransactionSupport.java:164) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport. executeInScope(TransactionSupport.java:103) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1453) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:397) [bll.jar:] at org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute( DefaultBackendActionExecutor.java:13) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runAction(Backend.java:496) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:478) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:684) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_121] at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121] at org.jboss.as.ee.component.ManagedReferenceMethodIntercep tor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation. proceed(InterceptorContext.java:437) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception( Jsr299BindingsInterceptor.java:70) [wildfly-weld-10.1.0.Final. jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception( Jsr299BindingsInterceptor.java:80) [wildfly-weld-10.1.0.Final. jar:10.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation( Jsr299BindingsInterceptor.java:93) [wildfly-weld-10.1.0.Final. jar:10.1.0.Final] at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1. processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor. processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation. proceed(InterceptorContext.java:437) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivat ionInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInter ceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) [wildfly-weld-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor. processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InitialInterceptor.processInvocation( InitialInterceptor.java:21) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation( ChainedInterceptor.java:61) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor .processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAsso ciationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:374) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:243) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterc eptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor. processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-10.1.0.Final. jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation( SecurityContextInterceptor.java:100) [wildfly-ejb3-10.1.0.Final. jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor. processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1. processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor. processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-10.1.0.Final. jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation( NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation( ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.wildfly.security.manager.WildFlySecurityManager.doChecked( WildFlySecurityManager.java:636) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation( AccessCheckingInterceptor.java:61) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation( PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation( ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee.component.ViewDescription$1.processInvocation( ViewDescription.java:185) at org.jboss.invocation.InterceptorContext.proceed( InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation( ChainedInterceptor.java:61) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke( ProxyInvocationHandler.java:73) at org.ovirt.engine.core.bll.interfaces.BackendInternal$$$ view4.runInternalAction(Unknown Source) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_121] at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121] at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:433) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke( EnterpriseBeanProxyMethodHandler.java:128) [weld-core-impl-2.3.5.Final. jar:2.3.5.Final] at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke( EnterpriseTargetBeanInstance.java:56) [weld-core-impl-2.3.5.Final. jar:2.3.5.Final] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.3.5.Final.jar:2.3.5.Final] at org.ovirt.engine.core.bll.BackendCommandObjectsHandler$ BackendInternal$BackendLocal$2049259618$Proxy$_$$_Weld$EnterpriseProxy$.runInternalAction(Unknown Source) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInternalAction(CommandBase.java:2454) [bll.jar:] at org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand. lambda$executeCommand$2(AddVdsCommand.java:183) [bll.jar:] at org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$ InternalWrapperRunnable.run(ThreadPoolUtil.java:92) [utils.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_121] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121] 2017-03-23 20:19:39,704-04 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (org.ovirt.thread.pool-7-thread-2) [796c74] Timeout waiting for VDSM response: Internal timeout occured <error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCVA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

2 1

ovirt 4.1.1
by Paul Dyer 24 Mar '17

24 Mar '17

Is this new release ready? When I do engine-setup, I get an error because centos/7Server directory is missing... Stage: Environment packages setup [ ERROR ] Yum Cannot queue package iproute: failure: repodata/repomd.xml from ovirt-centos-ovirt41: [Errno 256] No more mirrors to try. http://mirror.centos.org/centos/7Server/virt/x86_64/ovirt-4.1/repodata/repo…: [Errno 14] HTTP Error 404 - Not Found -- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750

3 3

Introducing engine micro-benchmarks
by Roy Golan 24 Mar '17

24 Mar '17

Lately we came across an interesting case where multi-host+mult-networks resulted editing a host to conclude in minutes. One assumption that was raised which we wanted to eliminate was that the decryption we perform on a fence agent password might be taking too long. So these days it's an easy task thanks to JMH[1], supplied by the jdk itself. I kickstarted [2] and added a 'DecryptionBenchmark', see the output as an example[3] Although The JMH project recommends to create a separate project I find it would be less trivial to people to contribute benchmarks let alone just playing around with current code they want to test. - So, (when it will be merged) you add your benchmark under backend/manager/modules/benchmarks/MyBenchmark.java - run it from intellij using the jmh plugin exactly like a unit-test OR - mvn test -P benchmarks -pl org.ovirt.engine:benchmarks OR - java -jar benchmarks.jar I hope this would serve all of us well, please review and add your benchmarks. PS - this will not run in the CI atm. [1] http://openjdk.java.net/projects/code-tools/jmh/ [2] https://gerrit.ovirt.org/74537 microbenchmarks: Introduce microbenchmarks using JMH [3] DecryptionBenchmark output (short version): # Run complete. Total time: 00:09:06 Benchmark Mode Samples Score Score error Units b.DecryptionBenchmark.decryption thrpt 50 101.258 1.270 ops/s b.DecryptionBenchmark.encryption thrpt 50 238.587 4.667 ops/s b.DecryptionBenchmark.decryption avgt 50 0.010 0.000 s/op b.DecryptionBenchmark.encryption avgt 50 0.004 0.000 s/op b.DecryptionBenchmark.decryption sample 5544 0.010 0.000 s/op b.DecryptionBenchmark.encryption sample 13067 0.004 0.000 s/op b.DecryptionBenchmark.decryption ss 50 0.014 0.001 s b.DecryptionBenchmark.encryption ss 50 0.009 0.001 s Process finished with exit code 0

7 9

Re: [ovirt-devel] Connection refuse in ovirt webservice
by shubham dubey 23 Mar '17

23 Mar '17

Actually I want to compile webadmin but it is giving me some error so I just skip its compilation. Now the webserver is working but in most of the pages (like when I am logging using admin) I am getting blank page. In logs it is written 2017-03-23 23:04:35,364+05 ERROR [org.ovirt.engine.core.utils.servlet.ServletUtils] (default task-5) [] Can't read file '/home/0day/ovirt-engine/etc/ovirt-engine/branding/00-ovirt.brand/ovirt-js-dependencies/insertion-query/insQ.min.js' for request '/ovirt-engine/webadmin/theme/00-ovirt.brand/ovirt-js-dependencies/insertion-query/insQ.min.js', will send a 404 error response So,is it happening because of webadmin? One more question is that I want to install ovirt-engine for development purpose,so did installing webadmin from rpm will also work or I have to only install it from source. On Thu, Mar 23, 2017 at 10:58 PM, Greg Sheremeta <gshereme(a)redhat.com> wrote: > You're welcome. > > You'll need to compile webadmin if you want to do the good stuff :) > > You can also always install it from rpm -- not sure what your goal is. > > Best wishes, > Greg > > On Thu, Mar 23, 2017 at 1:13 PM, shubham dubey <sdubey504(a)gmail.com> > wrote: > >> Thanks,It works now.;) >> >> On Thu, Mar 23, 2017 at 10:06 PM, Greg Sheremeta <gshereme(a)redhat.com> >> wrote: >> >>> Step 3: start it >>> >>> $HOME/ovirt-engine/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py >>> start >>> >>> Greg >>> >>> On Thu, Mar 23, 2017 at 12:21 PM, shubham dubey <sdubey504(a)gmail.com> >>> wrote: >>> >>>> Hello, >>>> I have recently installed the ovirt engine development enviornment >>>> using >>>> $make clean install-dev PREFIX="$HOME/ovirt-engine" BUILD_GWT_WEBADMIN=0 >>>> after that I run $HOME/ovirt-engine/bin/engine-setup. >>>> Both run successfully but when I am opening the webservice link(in my >>>> case http://localhost.localdomain:8080/) in my browser I am getting >>>> connection refused. >>>> >>>> I have my seLinux disabled and I have also done iptables -F. >>>> So any other Solution? >>>> And is this because of disabling webadmin? >>>> >>>> Thanks, >>>> Shubham >>>> >>>> _______________________________________________ >>>> Devel mailing list >>>> Devel(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/devel >>>> >>> >>> >>> >>> -- >>> Greg Sheremeta, MBA >>> Red Hat, Inc. >>> Sr. Software Engineer >>> gshereme(a)redhat.com >>> >> >> > > > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com >

2 2

Fwd: Connection refuse in ovirt webservice
by shubham dubey 23 Mar '17

23 Mar '17

---------- Forwarded message ---------- From: shubham dubey <sdubey504(a)gmail.com> Date: Thu, Mar 23, 2017 at 10:43 PM Subject: Re: [ovirt-devel] Connection refuse in ovirt webservice To: Greg Sheremeta <gshereme(a)redhat.com> Thanks,It works now.;) On Thu, Mar 23, 2017 at 10:06 PM, Greg Sheremeta <gshereme(a)redhat.com> wrote: > Step 3: start it > > $HOME/ovirt-engine/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py > start > > Greg > > On Thu, Mar 23, 2017 at 12:21 PM, shubham dubey <sdubey504(a)gmail.com> > wrote: > >> Hello, >> I have recently installed the ovirt engine development enviornment >> using >> $make clean install-dev PREFIX="$HOME/ovirt-engine" BUILD_GWT_WEBADMIN=0 >> after that I run $HOME/ovirt-engine/bin/engine-setup. >> Both run successfully but when I am opening the webservice link(in my >> case http://localhost.localdomain:8080/) in my browser I am getting >> connection refused. >> >> I have my seLinux disabled and I have also done iptables -F. >> So any other Solution? >> And is this because of disabling webadmin? >> >> Thanks, >> Shubham >> >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> > > > > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gshereme(a)redhat.com >

1 0

Connection refuse in ovirt webservice
by shubham dubey 23 Mar '17

23 Mar '17

Hello, I have recently installed the ovirt engine development enviornment using $make clean install-dev PREFIX="$HOME/ovirt-engine" BUILD_GWT_WEBADMIN=0 after that I run $HOME/ovirt-engine/bin/engine-setup. Both run successfully but when I am opening the webservice link(in my case http://localhost.localdomain:8080/) in my browser I am getting connection refused. I have my seLinux disabled and I have also done iptables -F. So any other Solution? And is this because of disabling webadmin? Thanks, Shubham

2 1

[vdsm] Engine XML: metadata and devices from XML
by Francesco Romani 23 Mar '17

23 Mar '17

Hi everyone, This is both a report of the current state of my Vdsm patches for Engine XML support, and a proposal to how move forward and solve the current open issues. TL;DR: 1. we can and IMO should reuse the current JSON schema to describe the structure (layout) and the types of the metadata section. 2. we don't need a priori validation of stuff in the metadata section. We will just raise in the creation flow if data is missing, or wrong, according to our schema. 2. we will add *few* items to the metadata section, only thing we can't express clearly-or at all in the libvirt XML. Redundancy and verbosiness will be thus kept at bay 3. I believe [3] is the best tool to do (de)serialize data to the metadata section. Existing tools fits poorly in our very specific use case Examples below +++ Long(er) discussion: I have working code[1][2] to encode any custom, picklable, python object in the metadata section. We should decide which module will do the actual python<=>XML transformation. Please note that this actually also influences how the data in the medata section look like, so the two things are a bit coupled. I'm eager to reinvent another wheel, but after initial evaluation I honestly think that my pyxmlpickle[3] is the best tool for the job over the current alternatives: plistlib[4] and xmltodict[5]. I added the initial rationale here: https://gerrit.ovirt.org/#/c/73790/4//COMMIT_MSG I have completed the initial draft of patches to make it possible to initialize devices from their XML representation [6]. This is the bare minimum we need to support the Engine XML, and we *need* this anyway to unlock the cleanup we planned and I outlined in my google doc. So we are progressing, but I'd like to speed up things. Those [6] patches are not yet complete, many flows are not covered or tested; but they are good enough to demonstrate that there *are* pieces of information wen need to properly initialize the devices, but we can't easily extract from the XML. First examples that come to my mind are the storage.Drive UUIDs; there could also be some ambiguity I'm investigating right now for displayIp/displayNetwork in Graphics devices. In [6] there are various TODO to mark more of those cases. Most likely, few more cases will pop out as I cover all the flows we support. Long story short: it is hard to correctly rebuild the device conf from the XML. This is why in [6] I added the 'meta' argument to from_xml_tree classmethod in [7]. 'meta' is supposed to be the device metadata: extra data related to a device which doesn't (yet) fit in the libvirt XML representation. For example, we can store 'displayIp' and 'displayNetwork' here and be done with that: using both per-device metadata and the XML representation of one graphic device, we will have everything we need to properly build one graphics.Graphics device. This example may (hopefully) be bogus, but I'm keeping it because it is one case easy to follow. The device metadata is going to be stored in the vm metadata for the short/mid term future. Even if the per-device metadata idea/RFE is accepted (no answer yet, but we are working on it), we will not have in 7.4, and unlikely in 7.5. As it stands today, I believe there are two open questions: 1. do we need a schema for the metadata section? 2. how do we bind the metadata to the devices? How do we know which metadata belongs to which metadata, if we don't have aliases nor addresses to match? (e.g. very first time the VM is created!) My current stance is the following 1. In general, one schema gives us two benefits: 1.a. we document how the layout of the data should be, including types; 1.b. we can validate the data we receive. So yes, we need a schema, but we don't need a *new* schema. I think we are in good enough shape with the current Vdsm schema: we can just translate the python object layout to a XML layout. One example is probably more explicative. Some actual data may look like, using my pyxmlpickle module: <domain type='kvm' id='5'> <name>a0</name> <uuid>ccd945c8-8069-4f31-8471-bbb58e9dd6ea</uuid> <metadata xmlns:ovirt-tune="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm="http://ovirt.org/vm/1.0" xmlns:ovirt-instance="http://ovirt.org/vm/instance/1.0"> <ovirt-tune:qos/> <ovirt-vm:vm/> <ovirt-instance:instance> <ovirt-instance:value type="dict"> <ovirt-instance:item key="devices" type="list"> <ovirt-instance:item index="0" type="dict"> <ovirt-instance:item key="device" type="str">vnc</ovirt-instance:item> <ovirt-instance:item key="specParams" type="dict"> <ovirt-instance:item key="displayNetwork" type="str">ovirtmgmt</ovirt-instance:item> <ovirt-instance:item key="displayIp" type="str">192.168.1.53</ovirt-instance:item> </ovirt-instance:item> <ovirt-instance:item key="type" type="str">graphics</ovirt-instance:item> </ovirt-instance:item> <ovirt-instance:item index="1" type="dict"> <ovirt-instance:item key="device" type="str">spice</ovirt-instance:item> <ovirt-instance:item key="specParams" type="dict"> <ovirt-instance:item key="displayNetwork" type="str">ovirtmgmt</ovirt-instance:item> <ovirt-instance:item key="displayIp" type="str">192.168.1.53</ovirt-instance:item> </ovirt-instance:item> <ovirt-instance:item key="type" type="str">graphics</ovirt-instance:item> </ovirt-instance:item> <ovirt-instance:item index="2" type="dict"> <ovirt-instance:item key="poolID" type="str">5890a292-0390-01d2-01ed-00000000029a</ovirt-instance:item> <ovirt-instance:item key="imageID" type="str">66441539-f7ac-4946-8a25-75e422f939d4</ovirt-instance:item> <ovirt-instance:item key="domainID" type="str">c578566d-bc61-420c-8f1e-8dfa0a18efd5</ovirt-instance:item> <ovirt-instance:item key="device" type="str">disk</ovirt-instance:item> <ovirt-instance:item key="path" type="str">/rhev/data-center/5890a292-0390-01d2-01ed-00000000029a/c578566d-bc61-420c-8f1e-8dfa0a18efd5/images/66441539-f7ac-4946-8a25-75e422f939d4/5c4eeed4-f2a7-490a-ab57-a0d6f3a711cc</ovirt-instance:item> <ovirt-instance:item key="volumeID" type="str">5c4eeed4-f2a7-490a-ab57-a0d6f3a711cc</ovirt-instance:item> </ovirt-instance:item> </ovirt-instance:item> </ovirt-instance:value> </ovirt-instance:instance> </metadata>  </domain> Please note that yes, this is still verbose, but we don't want to add much data here, for most of information the most reliable source will be the domain XML. We will add here only the extra info we can't really fetch from that. 2. I don't think we need explicit validation: we could just raise along the way in the creation flow if we don't find some extra metadata we need. This will also solve the issue that if we reuse the current schema and we omit most of data, we will lack quite a lot of elements marked mandatory. Once we reached agreement, I will update my https://docs.google.com/document/d/1eD8KSLwwyo2Sk64MytbmE0wBxxMlpIyEI1GRcHD… accordingly. Final note: while device take the lion's share, we will likely need help from the metadata section also to store VM extra info, but all the above discussion also applies here. +++ [1] https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v… - uses xmltodict [2] https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v… ported the 'virt-metadata3' topic to pyxmlpickle [3] https://github.com/fromanirh/pyxmlpickle [4] https://docs.python.org/2/library/plistlib.html [5] https://github.com/martinblech/xmltodict [6] https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v… [7] https://gerrit.ovirt.org/#/c/72880/15/lib/vdsm/virt/vmdevices/core.py -- Francesco Romani Red Hat Engineering Virtualization R & D IRC: fromani

4 11

[vdsm] Patches awaiting review
by Piotr Kliczewski 22 Mar '17

22 Mar '17

All, Here is bunch of patches that I would like have reviewed: https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:s… https://gerrit.ovirt.org/#/c/72284/ https://gerrit.ovirt.org/#/c/74005/ A draft from Nir: https://gerrit.ovirt.org/#/c/72306/ And xmlrpc removal: https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:x… Thanks, Piotr

1 0

Dates for This Phase of GSoC
by Brian Proffitt 22 Mar '17

22 Mar '17

I've had some questions about the Google Summer of Code, and I wanted to share with you the dates and milestones for the student/mentor onboarding phase of the event. All dates can be found on the GSoC site[1]. Right now we are in the student application phase, which goes until April 3. By that time, students should have their draft proposals in. Then we review them and turn them in to Google by April 16. On April 17, we ask for student slots, and then on April 19, slots are allocated to us. Finally, on April 24, we tell Google which students are going to take the slots, and then on May 3, Google announces all projects/students/mentors. Hopefully this helps. Please watch your inbox for notifications from Google to ensure what you are getting does not need an action item. What I get as one of the oVirt admins for GSoC is different that what you get as (potential) mentors. Peace, Brian [1] https://summerofcode.withgoogle.com/dashboard/timeline/ -- Brian Proffitt Principal Community Analyst Open Source and Standards @TheTechScribe 574.383.9BKP

1 0

planned Jenkins restart
by Evgheni Dereveanchin 21 Mar '17

21 Mar '17

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new builds will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin

1 1

[ OST Failure Report ] [ oVirt master ] [ 21-03-2017 ] [test-repo_ovirt_experimental_master]
by Shlomo Ben David 21 Mar '17

21 Mar '17

Hi, Test failed: [ test-repo_ovirt_experimental_master ] Link to suspected patches: N/A Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5945 Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5945/artif… Error snippet from the log: <error> 2017-03-21 11:55:15,975-0400 ERROR (jsonrpc/7) [storage.TaskManager.Task] (Task='02a8b5a3-ff82-4a07-bc8a-b3a756630e8c') Unexpected error (task:871) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 878, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 52, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 1158, in attachStorageDomain pool.attachSD(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/share/vdsm/storage/sp.py", line 930, in attachSD dom = sdCache.produce(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 112, in produce domain.getRealDomain() File "/usr/share/vdsm/storage/sdc.py", line 53, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 136, in _realProduce domain = self._findDomain(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 153, in _findDomain return findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 178, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'a8739fae-284f-4640-800d-016c084de7e6',) </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCVA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

1 0

NetworkManager (was: Fwd: Question for oVirt)
by Yedidyah Bar David 21 Mar '17

21 Mar '17

On Tue, Mar 21, 2017 at 4:40 AM, jeff hsueh <jeffhsueh(a)qnap.com> wrote: > Hi Devel, > > Could you help to give me some detail information about this feature? > Thanks. > > Jeff > > ---------- Forwarded message ---------- > From: Mike Burns <mburns(a)redhat.com> > Date: 2017-03-20 20:44 GMT+08:00 > Subject: Re: Question for oVirt > To: jeff hsueh <jeffhsueh(a)qnap.com> > > > This is very old (last update 2012). I haven't worked on oVirt in a long > time either. You should redirect this and other questions to > > devel(a)ovirt.org. > > Thanks > > On Mon, Mar 20, 2017 at 4:56 AM, jeff hsueh <jeffhsueh(a)qnap.com> wrote: > >> Hi Mike, >> >> I am studying "NetworkManager Support" of oVirt project. >> Link: http://www.ovirt.org/develop/release-management/featur >> es/network/networkmanager-support/ >> >> I could not understand what does this feature want to achieve. >> Could I get more information and status about this feature from you? >> Because the information about this feature in oVirt web site is too brief. >> > (changed the subject) Please check these: https://bugzilla.redhat.com/show_bug.cgi?id=1326798 https://bugzilla.redhat.com/show_bug.cgi?id=1330138 Should work in 4.1.1 (to be released tomorrow). Best, > >> Thanks. >> >> Jeff >> >> >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> >> 不含病毒。www.avast.com >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> >> <#m_-8543651732826125291_m_-8795404721952800494_m_4727600564310439803_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> > > > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- Didi

1 0

Get Involved with the oVirt Project! Spring 2017 Edition
by Sandro Bonazzola 21 Mar '17

21 Mar '17

Hi, Got some time to spare? Join us on the oVirt project! oVirt is a feature rich server virtualization management system with advanced capabilities. It also provides a crucial venue for user and developer cooperation, and is the first truly open and comprehensive data center virtualization management initiative. If you are new to oVirt, we recommend that you visit the develop <https://www.ovirt.org/develop/> page to learn more about the project, and the working with Gerrit <https://www.ovirt.org/develop/dev-process/working-with-gerrit/> page for more about our code review system. If you haven’t worked with Gerrit before, we recommend you visit the introduction to Gerrit <https://gerrit-review.googlesource.com/Documentation> page. On our community page <https://www.ovirt.org/community/> you’ll discover the many ways in which you can contribute to the project, even without programming skills. More suggestions? Below you’ll find other ways in which you can contribute to the oVirt project. Keep ‘em Fresh Like the idea of having fresh disk images of your favorite distribution in the oVirt Glance repository? You can help in two ways: First, test existing online images to ensure that they work with cloud-init. Second, create an online image and report your success to devel(a)ovirt.org. We’ll be happy to upload the images once they are ready. Get Vdsm Running on Debian If you like Debian and have programming or packaging skills, you can help with the ongoing effort to get VDSM running on Debian <https://www.ovirt.org/develop/release-management/features/debian-support-fo…>. All the current work on Debian (VDSM and related packages) can be found in the Debian git repositories <http://git.debian.org/>. You can also keep up to date on how the work is progressing by subscribing to the oVirt devel mailing list <http://lists.ovirt.org/mailman/listinfo/devel>. Fix Some Bugs These bugs are just waiting to be resolved: Bug ID Summary 1411133 Hosted-Engine: iscsi activation storage failing 1209881 [RFE] Remove iptables from hosted-engine.spec file to be able to deploy hosted-engine without firewall services installed 1353713 [RFE] - iSCSI Setup Should use different User/Password For Discovery and Portal 1130445 [TEXT] - If engine-setup asks for updates and choice is no, suggest '--offline' on re-run. 1174236 [RFE] Integrate installation with Server Roles of Fedora Server 1356425 [TEXT] 'hosted-engine --vm-start' said it destroyed the VM 1328488 The engine fails with oracle java8 Port oVirt to Your Favorite Distribution Are you sure-handed at packaging software, and using a distribution currently unsupported by oVirt? Help to get oVirt ported to any of the following distributions: Fedora <http://lists.ovirt.org/pipermail/devel/2015-September/011426.html> CentOS <https://wiki.centos.org/SpecialInterestGroup/Virtualization> Gentoo <https://wiki.gentoo.org/wiki/OVirt>. Also, check out Google Summer of Code <https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2016/Ideas> to learn how you can contribute to Gentoo and get paid for it! Debian <http://www.ovirt.org/develop/release-management/features/debian-support-for…>: Archlinux <http://www.ovirt.org/develop/developer-guide/arch-linux/> OpenSUSE <https://build.opensuse.org/project/show/Virtualization:oVirt> Get into DevOps If you love DevOps and find yourself counting stable builds in Jenkins CI while trying to fall asleep, then the oVirt infrastructure team is looking for you! Join us and dive into the latest and coolest DevOps tools today! Check out these open tasks <https://ovirt-jira.atlassian.net/secure/RapidBoard.jspa?rapidView=6.>. You can also help by telling us how you use oVirt in your DevOps environment. Email us at devel(a)ovirt.org (Please use [DevOps] in the subject line. For more information on oVirt DevOps, visit oVirt infrastructure docs <http://ovirt-infra-docs.readthedocs.io/en/latest/> and oVirt infra documentation <http://www.ovirt.org/develop/infra/infrastructure-documentation/>. Improve the oVirt System Testing Make oVirt system testing <https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=summary> - and the Lago system <https://github.com/lago-project/lago> that runs it - even better. Visit Lago project documentation <http://lago.readthedocs.io/en/stable/> to learn how to run the test suite yourself. More Bugs, No Coding Required No time for DevOps and you are not a programer? You can still contribute. Here are some easy bugs to fix <https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%…> that don’t require a single line of code. Tests to Run Do you prefer to test things? Here are some test cases you can try <http://www.ovirt.org/develop/infra/testing/>, using nightly snapshots <http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/>. Switching to Fedora 25 For oVirt 4.2, support for Fedora will be based on Fedora 25. You can help to get it ready by running nightly snapshots <http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/> and reporting any issues. Create Your Own Test Cases We’d love you to contribute some much needed test cases for oVirt features <http://www.ovirt.org/develop/release-management/features/>. Get Creative You are welcome to contribute artwork, such as oVirt live backgrounds and covers, release banners, stickers, and t-shirt designs. Check out Fedora artworks <https://fedoraproject.org/wiki/Artwork#Resources> for inspiration. Get Alternative Into alternative architectures? Test ppc64le <https://cbs.centos.org/repos/virt7-ovirt-41-release/ppc64le/> and aarch64 <https://cbs.centos.org/repos/virt7-ovirt-41-release/aarch64/> packages from CentOS Virt SIG. Talk to Us! Feel free to ask any other question about development by emailing us at devel(a)ovirt.org, or by reaching out on the IRC channel <https://www.ovirt.org/community/>. Spread the Good News Help to spread the word about oVirt! We are the complete virtual machine management system that’s free and comes with an impressive list of enterprise capabilities <http://www.zdnet.com/article/how-much-longer-can-red-hats-ovirt-remain-cove…> including live migration, high availability, load balancing, a self-hosted engine, an intuitive user-interface, and much more. How to Contribute If you’d like to get involved, we’d love to hear from you! Simply shoot us an email at devel(a)ovirt.org and tell us how you’d like to contribute. We look forward to hearing from you!. The oVirt Development Team oVirt: Better technology. Faster Innovation. Powered by community innovation.

1 0

UI dialog visual update
by Alexander Wels 20 Mar '17

20 Mar '17

Hi, I just merged a large patch that does a complete visual update of all dialogs in oVirt. All the dialogs should now follow the standard patternfly modal dialog visuals and layout. One of the consequences of this is that you can no longer move the dialogs around in the application like before. This is by design. I tried very hard to make sure I updated every dialog in the application to match the look and feel as needed, or at the very least did not display any major issues like missing content or extra scrollbars where none were needed. Please report any issues you find to me, and I will try to make sure they get fixed ASAP. Alexander ps. attached are some screenshots from my development environment.

1 0

[ OST Failure Report ] [ oVirt master ] [ 20-03-2017 ] [007_sd_reattach.reattach_storage_domain]
by Shlomo Ben David 20 Mar '17

20 Mar '17

Hi, Test failed: [ 007_sd_reattach.reattach_storage_domain ] Link to suspected patches: N/A Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5915/conso… Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5915/artif… Error snippet from the log: <error> 12:01:51 [basic_suit_el7] @ Run test: 007_sd_reattach.py: ERROR (in 0:00:44) 12:01:51 [basic_suit_el7] Error occured, aborting 12:01:51 [basic_suit_el7] Traceback (most recent call last): 12:01:51 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 267, in do_run 12:01:51 [basic_suit_el7] self.cli_plugins[args.ovirtverb].do_run(args) 12:01:51 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run 12:01:51 [basic_suit_el7] self._do_run(**vars(args)) 12:01:51 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 495, in wrapper 12:01:51 [basic_suit_el7] return func(*args, **kwargs) 12:01:51 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 506, in wrapper 12:01:51 [basic_suit_el7] return func(*args, prefix=prefix, **kwargs) 12:01:51 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 96, in do_ovirt_runtest 12:01:51 [basic_suit_el7] raise RuntimeError('Some tests failed') 12:01:51 [basic_suit_el7] RuntimeError: Some tests failed </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCVA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

4 3

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML
by Francesco Romani 20 Mar '17

20 Mar '17

On 03/17/2017 11:07 PM, Michal Skrivanek wrote: >> On 17 Mar 2017, at 15:57, Francesco Romani <fromani(a)redhat.com> wrote: >> >> On 03/16/2017 08:03 PM, Francesco Romani wrote: >>> On 03/16/2017 01:26 PM, Francesco Romani wrote: >>>> On 03/16/2017 11:47 AM, Michal Skrivanek wrote: >>>>>> On 16 Mar 2017, at 09:45, Francesco Romani <fromani(a)redhat.com> wrote: >>>>>> >>>>>> We talked about sending storage device purely on metadata, letting Vdsm >>>>>> rebuild them and getting the XML like today. >>>>>> >>>>>> In the other direction, Vdsm will pass through the XML (perhaps only >>>>>> parts of it, e.g. the devices subtree) like before. >>>>>> >>>>>> This way we can minimize the changes we are uncertain of, and more >>>>>> importantly, we can minimize the risky changes. >>>>>> >>>>>> >>>>>> The following is a realistic example of how the XML could look like if >>>>>> we send all but the storage devices. It is built using my pyxmlpickle >>>>>> module (see [3] below). >>>>> That’s quite verbose. How much work would it need to actually minimize it and turn it into something more simple. >>>>> Most such stuff should go away and I believe it would be beneficial to make it difficult to use to discourage using metadata as a generic junkyard >>>> It is verbose because it is generic - indeed perhaps too generic. >>>> I can try something else based on a concept from Martin Polednik. Will >>>> follow up soon. >>> Early preview: >>> https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v… >>> >>> still plenty of TODOs, I expect to be reviewable material worst case >>> monday morning. >> This is how typical XML could look like: >> >> <metadata> >> <ovirt-tune:qos /> >> <ovirt-vm:vm /> >> <devices> >> <ovirt-instance:graphics> > not under the <ovirt-vm:vm>? > any reason? No reason, I'll move under it Bests, -- Francesco Romani Red Hat Engineering Virtualization R & D IRC: fromani

1 1

Friendly reminder on how to run OST on your patches
by Eyal Edri 20 Mar '17

20 Mar '17

Hi oVirt developers, A few weeks ago we announced that it is now possible to run oVirt System Tests on any open patch in oVirt [1]. Just wanted to remind everyone how easy it to run the whole basic suite or upgrade suite on your open patches. Here is a summary of the steps needed to run the job [2]: *How to use?* - Add a comment to your open patch in Gerrit and write '*ci please build*' - Wait for the 'build-on-demand' job to finish and copy the URL of the build that shows up on the comments in Gerrit. - Go the manual job [2] and click 'Build with parameters' [3] - Add your 'build-on-demand' URLs to the job (you can put multiple URLs, one per line) - Choose the oVirt version you wish to test (should match to the oVirt version of your patch). - Choose the suite type from the drop-down menu (choose basic to run normal sanity or upgrade to test upgrade engine) There are other options to choose, but the default ones will work best for most cases, You can checkout the documentation [4] for more detailed info. Feel free to reach out to infra team for more info or help! [1] https://lists.ovirt.org/pipermail/devel/2017-February/029565.html [2] http://jenkins.ovirt.org/job/ovirt-system-tests_manual/ [3] make sure you have the 'dev' role for Jenkins, if you don't, send email to infra-support(a)ovirt.org and ask to be added. [4] http://ovirt-system-tests.readthedocs.io/en/latest/docs/CI/developers_info.… -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Ceph hyperconvergence
by Logan Kuhn 19 Mar '17

19 Mar '17

Hi It was suggested that I ask this list. Are there any plans to add hyperconverge with Ceph, similar to the way it has been implemented with Gluster? I know that I can add Cinder as an external provider as an interface to Ceph, but it's more clunky than a hyperconverged solution. Regards, Logan Kuhn

3 3

System tests failure (wrong test code?)
by Nir Soffer 19 Mar '17

19 Mar '17

If found this error in system tests - looks like wrong assert - code should check if disk is not None before checking state. I'm not sure who is the owner of this test, so posting here. *08:28:05* # snapshots_merge: *08:28:31* Unhandled exception in <function <lambda> at 0x276a5f0>*08:28:31* Traceback (most recent call last):*08:28:31* File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within*08:28:31* res = func()*08:28:31* File "/home/jenkins/workspace/ovirt-system-tests_manual/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 466, in <lambda>*08:28:31* api.vms.get(VM0_NAME).disks.get(disk_name).status.state == 'ok'*08:28:31* AttributeError: 'NoneType' object has no attribute 'state'*08:28:31* Error while running thread*08:28:31* Traceback (most recent call last):*08:28:31* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue*08:28:31* queue.put({'return': func()})*08:28:31* File "/home/jenkins/workspace/ovirt-system-tests_manual/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 465, in snapshot_live_merge*08:28:31* lambda:*08:28:31* File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 264, in assert_true_within_long*08:28:31* assert_equals_within_long(func, True, allowed_exceptions)*08:28:31* File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 251, in assert_equals_within_long*08:28:31* func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions*08:28:31* File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within*08:28:31* res = func()*08:28:31* File "/home/jenkins/workspace/ovirt-system-tests_manual/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 466, in <lambda>*08:28:31* api.vms.get(VM0_NAME).disks.get(disk_name).status.state == 'ok'*08:28:31* AttributeError: 'NoneType' object has no attribute 'state'

4 9

[ OST Failure Report ] [ ovirt-engine-4.1 ] [ 02.03.2017 ] [004_basic_sanity]
by Pavel Zhukov 19 Mar '17

19 Mar '17

Hi, This is one-time failure. Non reproducible. disk_id was not inserted into DB because of jsonrpc/networking issue. But once OST runs on localhost networking (should not) be a problem here so adding Piotr. Failed jobs: http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… Logs: http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… [LOGS SNIPPETS] 35897:2017-03-02 07:12:28,721-05 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateImageVDSCommand] (default task-19) [4adab878] START, CreateImageVDSCommand( CreateImageVDSCommandParameters:{runAsync='true', storagePoolId='9314c679-9a20-48b4-b62a-f7b6a3703287', ignoreFailoverLimit='false', storageDomainId='49226db8-e43f-4a15-a3a3-0bddd690d06b', imageGroupId='9cf5a90d-05fc-45de-a3c1-adbb6822150e', imageSizeInBytes='2', volumeFormat='COW', newImageId='c5275e2f-ac80-47c2-a43e-b5a0420a4211', newImageDescription='{"DiskAlias":"vm0_disk0","DiskDescription":""}', imageInitialSizeInBytes='0'}), log id: 657ef611 35920:{"jsonrpc":"2.0","method":"Volume.create","params":{"volumeID":"c5275e2f-ac80-47c2-a43e-b5a0420a4211","storagepoolID":"9314c679-9a20-48b4-b62a-f7b6a3703287","storagedomainID":"49226db8-e43f-4a15-a3a3-0bddd690d06b","imageID":"9cf5a90d-05fc-45de-a3c1-adbb6822150e","size":"2","volFormat":4,"preallocate":2,"diskType":2,"desc":"{\"DiskAlias\":\"vm0_disk0\",\"DiskDescription\":\"\"}","srcImgUUID":"00000000-0000-0000-0000-000000000000","srcVolUUID":"00000000-0000-0000-0000-000000000000"},"id":"0a757eae-0cc2-4f15-9bb5-05ad3221f697"} <=== NOTE NULL character here 35926:<JsonRpcRequest id: "0a757eae-0cc2-4f15-9bb5-05ad3221f697", method: Volume.create, params: {volumeID=c5275e2f-ac80-47c2-a43e-b5a0420a4211, storagepoolID=9314c679-9a20-48b4-b62a-f7b6a3703287, storagedomainID=49226db8-e43f-4a15-a3a3-0bddd690d06b, imageID=9cf5a90d-05fc-45de-a3c1-adbb6822150e, size=2, volFormat=4, preallocate=2, diskType=2, desc={"DiskAlias":"vm0_disk0","DiskDescription":""}, srcImgUUID=00000000-0000-0000-0000-000000000000, srcVolUUID=00000000-0000-0000-0000-000000000000}> 35996:2017-03-02 07:12:30,468-05 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (default task-19) [4adab878] ERROR, CreateImageVDSCommand( CreateImageVDSCommandParameters:{runAsync='true', storagePoolId='9314c679-9a20-48b4-b62a-f7b6a3703287', ignoreFailoverLimit='false', storageDomainId='49226db8-e43f-4a15-a3a3-0bddd690d06b', imageGroupId='9cf5a90d-05fc-45de-a3c1-adbb6822150e', imageSizeInBytes='2', volumeFormat='COW', newImageId='c5275e2f-ac80-47c2-a43e-b5a0420a4211', newImageDescription='{"DiskAlias":"vm0_disk0","DiskDescription":""}', imageInitialSizeInBytes='0'}), exception: VDSGenericException: VDSNetworkException: 880 > 879, log id: 657ef611 36511:2017-03-02 07:12:35,744-05 INFO [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (default task-19) [4adab878] Command [id=35007fba-781c-4a15-8f29-a8efe441b2f3]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage.DiskImage; snapshot: 9cf5a90d-05fc-45de-a3c1-adbb6822150e. 2017-03-02 07:12:35,766-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler7) [6dc0e793] EVENT_ID: SYSTEM_CHANGE_STORAGE_POOL_STATUS_PROBLEMATIC(980), Correlation ID: 6dc0e793, Call Stack: null, Custom Event ID: -1, Message: Invalid status on Data Center test-dc. Setting status to Non Responsive. 2017-03-02 07:12:35,773-05 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-19) [4adab878] Removed task '10b3bd58-8f3e-4b23-a8b6-27db110810d5' from DataBase 2017-03-02 07:12:35,779-05 DEBUG [org.ovirt.engine.core.dal.dbbroker.CustomSQLErrorCodeSQLExceptionTranslator] (default task-19) [4adab878] Translating SQLException with SQL state '23503', error code '0', message [ERROR: insert or update on table "disk_vm_element" violates foreign key constraint "fk_disk_vm_element_base_disks" Detail: Key (disk_id)=(9cf5a90d-05fc-45de-a3c1-adbb6822150e) is not present in table "base_disks". -- Pavel

7 10

[WARNING] Minimum requirements to fit the disk from the appliance OVF not met (required 50 GiB)
by Yaniv Kaul 19 Mar '17

19 Mar '17

ovirt-system-tests is failing[1] even though I've given it 100GB+ for every disk I could think of. What is it looking for and where exactly? TIA, Y. [1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… *13:24:17* [ INFO ] Checking OVF archive content (could take a few minutes depending on archive size)*13:24:43* [ INFO ] Checking OVF XML content (could take a few minutes depending on archive size)*13:25:08* [ INFO ] Detecting host timezone.*13:25:08* [WARNING] Minimum requirements to fit the disk from the appliance OVF not met (required 50 GiB)*13:25:08* [ ERROR ] Failed to execute stage 'Environment customization': Minimum requirements to fit the disk from the appliance OVF not met (required 50 GiB)*13:25:08* [ INFO ] Stage: Clean up

3 3

Error in ovirt-engine installation
by shubham dubey 17 Mar '17

17 Mar '17

Hello, I am trying to install ovirt-engine from almost 2 or 3 weeks in my fedora 25. But everytime I run this $ make install-dev PREFIX="$HOME/ovirt-engine" I got following error http://pastebin.com/cEfDJYix. I have tried to debug the problem lots of time but doesn't get succeeded. With little googling I might think that error is memory related but I have checked the memory usage and that looks normal. So,can anyone help to solve the problem? Thanks, Shubham

5 6

Ovirt 4.1 USB Api problems
by Adolfo 17 Mar '17

17 Mar '17

Hi, I don't know if this is the correct place for this question (i hope it is ;-) ). We are trying to make "enable USB support" work with a machine created from python ovirtsdk4 api, here is the code: cluster = ovirt.types.Cluster(id=six.binary_type(clusterId)) template = ovirt.types.Template(id=six.binary_type(templateId)) if usbType in ('native', 'legacy'): usb = ovirt.types.Usb(enabled=True, type=ovirt.types.UsbType.NATIVE if usbType == 'native' else ovirt.types.UsbType.LEGACY) else: usb = ovirt.types.Usb(enabled=False) memoryPolicy = ovirt.types.MemoryPolicy(guaranteed=guaranteedMB * 1024 * 1024) par = ovirt.types.Vm(name=name, cluster=cluster, template=template, description=comments, type=ovirt.types.VmType.DESKTOP, memory=memoryMB * 1024 * 1024, memory_policy=memoryPolicy, usb=usb) # display=display, return api.system_service().vms_service().add(par).id The cuestion is that the machines gets correctly created, but when we try to start the machine, we get an this error (extract from vdsm): Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 552, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 1994, in _run self._connection.createXML(domxml, flags), File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 123, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 941, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3784, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: Error XML: Duplicate USB controllers with index 0 The question is, that if to this machine we have created, from administration interface, remove an add support for usb, the machine works, and the generated XML differs: This is the difference we have found: < <controller index="0" model="piix3-uhci" type="usb"> < <address bus="0x00" domain="0x0000" function="0x2" slot="0x01" type="pci" /> < </controller> 40a38 > <address bus="0x00" domain="0x0000" function="0x0" slot="0x02" type="pci" /> The "<" are from the non working (created from API call), and the ">" are same machine after disabling and enabling again "usb support". Is this a bug?, if not, ¿How is supposed to be enabled USB support from API on VM Creation?, By the way, the equivalent code for oVirt 3.x was working without problems, the problems arises from 4.0 onwards. Sorry for the inconveniences, and thank in advance for any help, Adolfo Gómez

2 2

Loadbalancer.org Enterprise VA with oVirt(RHEV) 4.1
by Nir Soffer 17 Mar '17

17 Mar '17

User explains how cool is ovirt and image upload: http://www.loadbalancer.org/blog/loadbalancer-org-enterprise-va-with-ovirtr… Enjoy, Nir

2 1

Line of death for tests
by Shmuel Melamud 16 Mar '17

16 Mar '17

Hi! I've found yesterday a very strange bug, most likely in Mockito. Hard to believe it really happens, but I've reproduced it in different environmentы and several revisions of oVirt master. I've added the following line into MigrateVmCommand: private Integer actualDowntime; + private Object actualDowntimeLock; This line causes ALL tests to fail with NullPointerException. Some tests print such a stack trace: java.lang.NullPointerException at org.mockito.internal.junit.util.TestName.getTestName(TestName.java:11) at org.mockito.internal.junit.MismatchReportingTestListener.testFinished(MismatchReportingTestListener.java:29) at org.mockito.internal.runners.DefaultInternalRunner$1$1.testFinished(DefaultInternalRunner.java:56) at org.junit.runner.notification.SynchronizedRunListener.testFinished(SynchronizedRunListener.java:56) at org.junit.runner.notification.RunNotifier$7.notifyListener(RunNotifier.java:190) ... Name of the field doesn't matter, but type matters - changing the type to Integer solved the problem. Does anybody has an idea why this happens and how to fix it? Shmuel

2 2

Re: [ovirt-devel] [monitoring][collectd] the collectd virt plugin is now on par with Vdsm needs
by Yaniv Dary 16 Mar '17

16 Mar '17

Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary(a)redhat.com IRC : ydary On Feb 21, 2017 13:06, "Francesco Romani" <fromani(a)redhat.com> wrote: Hello everyone, in the last weeks I've been submitting PRs to collectd upstream, to bring the virt plugin up to date with Vdsm and oVirt needs. Previously, the collectd virt plugin reported only a subset of metrics oVirt uses. In current collectd master, the collectd virt plugin provides all the data Vdsm (thus Engine) needs. This means that it is now possible for Vdsm or Engine to query collectd, not Vdsm/libvirt, and have the same data. There are only two caveats: 1. it is yet to be seen which version of collectd will ship all those enhancements 2. collectd *intentionally* report metrics as rates, not as absolute values as Vdsm does. This may be one issue in presence of restarts/data loss in the link between collectd and the metrics store. How does this work? If we want to show memory usage over time for example, we need to have the usage, not the rate. How would this be reported? Please keep reading for more details: How to get the code? -------------------------------- This somehow tricky until we get one official release. If one is familiar with the RPM build process, it is easy to build one custom packages from a snapshot from collectd master (https://github.com/collectd/collectd) and a recent 5.7.1 RPM (like https://koji.fedoraproject.org/koji/buildinfo?buildID=835669) How to configure it? ------------------------------ Most thing work out of the box. One currently in progress Vdsm patch ships the recommended configuration https://gerrit.ovirt.org/#/c/71176/6/static/etc/collectd.d/virt.conf The meaning of the configuration option is documented in man 5 collectd.conf How it looks like? -------------------------- Let me post one "screenshot" :) $ collectdctl listval | grep a0 a0/virt/disk_octets-hdc a0/virt/disk_octets-vda a0/virt/disk_ops-hdc a0/virt/disk_ops-vda a0/virt/disk_time-hdc a0/virt/disk_time-vda a0/virt/if_dropped-vnet0 a0/virt/if_errors-vnet0 a0/virt/if_octets-vnet0 a0/virt/if_packets-vnet0 a0/virt/memory-actual_balloon a0/virt/memory-rss a0/virt/memory-total a0/virt/ps_cputime a0/virt/total_requests-flush-hdc a0/virt/total_requests-flush-vda a0/virt/total_time_in_ms-flush-hdc a0/virt/total_time_in_ms-flush-vda a0/virt/virt_cpu_total a0/virt/virt_vcpu-0 a0/virt/virt_vcpu-1 How to consume the data? ----------------------------------------- Among the ways to query collectd, the two most popular (and most fitting for oVirt use case) ways are perhaps the network protocol (https://collectd.org/wiki/index.php/Binary_protocol) and the plain text protocol (https://collectd.org/wiki/index.php/Plain_text_protocol) The first could be used by Engine to get the data directly, or to consolidate the metrics in one database (e.g to run any kind of query, for historical series...). The latter will be used by Vdsm to keep reporting the metrics (again https://gerrit.ovirt.org/#/c/71176/6) Please note that the performance of the plain text protocol are known to be lower than the binary protocol What about the unresponsive hosts? ------------------------------------------------------- We know from experience that hosts may become unresponsive, and this can disrupt monitoring. however, we do want to keep monitoring the responsive hosts, avoiding that one rogue hosts makes us lose all the monitoring data. To cope with this need, the virt plugin gained support for "partition tag". With this, we can group VMs together using one arbitrary tag. This is completely transparent to collectd, and also completely optional. oVirt can use this tag to group VMs per-storage-domain, or however it sees fit, trying to minimize the disruption should one host become unresponsive. Read the full docs here: https://github.com/collectd/collectd/commit/999efc28d8e2e96bc15f535254d412 a79755ca4f What about the collectd-ovirt plugin? -------------------------------------------------------- Some time ago I implemented one out-of-tree collectd plugin leveraging the libvirt bulk stats: https://github.com/fromanirh/collectd-ovirt This plugin is meant to be a modern, drop-in replacement for the existing virt plugin. The development of that out of tree plugin is now halted, because we have everything we need in the upstream collectd plugin. Future work ------------------ We believe we have reached feature parity, so we are looking for bugixes/performance tuning in the near term future. I'll be happy to provide more patches/PRs about that. Thanks and bests, -- Francesco Romani Red Hat Engineering Virtualization R & D IRC: fromani _______________________________________________ Devel mailing list Devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

3 11

Error in setup of ovirt-engine Development Environment
by shubham dubey 16 Mar '17

16 Mar '17

Hello, I am trying to setup ovirt-engine using this link http://www.ovirt.org/develop/developer-guide/engine/engine-development-envi… . Now when I am trying these commands I am getting following error $ postgres -c "psql -d template1 -c \"create user engine password 'engine';\"" FATAL: -c psql -d template1 -c "create user engine password 'engine';" requires a value and $postgres -c "psql -d template1 -c "create database engine \ owner engine template template0 encoding 'UTF8' lc_collate \ 'en_US.UTF-8' lc_ctype 'en_US.UTF-8';\"" FATAL: -c psql -d template1 -c "create database engine owner engine template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8';" requires a value So I think the syntax given there is not right,So can anyone tell me the correct syntax.Or maybe I am doing something wrong. Thanks, Shubham

6 8