October 2018 - Devel - oVirt List Archives

[VDSM] Started getting virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired
by Edward Haas 12 Jan '24

12 Jan '24

Hi, I have a VM which acts as an oVirt host with VDSM installed. I use it for testing without connecting it to Engine. Recently VDSM fails to come up and I see this error: Sep 26 17:58:18 localhost libvirtd: 2018-09-26 14:58:18.978+0000: 12176: error : virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired Any hint on how to generate or fetch a new certificate without the help of Engine? Thanks, Edy.

3 5

Error Java SDK Issue??
by Geschwentner, Patrick 02 Apr '21

02 Apr '21

Dear Ladies and Gentlemen! I am currently working with the java-sdk and I encountered a problem. If I would like to retrieve the disk details, I get the following error: Disk currDisk = ovirtConnection.followLink(diskAttachment.disk()); The Error is occurring in this line: [cid:image001.png@01D44537.AF127FD0] The getResponst looks quiet ok. (I inspected: [cid:image002.png@01D44537.AF127FD0] and it looks ok). Error: wrong number of arguments The code is quiet similar to what you published on github (https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/sdk/src/test/jav… ). Can you confirm the defect? Best regards Patrick

6 11

[VDSM] test_echo(1024, False) (stomp_test.StompTests) fails
by Nir Soffer 02 Dec '18

02 Dec '18

This tests used to fail in the past, but since we fixed it or the code it never failed. Maybe the slave was overloaded? *14:19:02* ======================================================================*14:19:02* ERROR: *14:19:02* ----------------------------------------------------------------------*14:19:02* Traceback (most recent call last):*14:19:02* File "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/testlib.py", line 143, in wrapper*14:19:02* return f(self, *args)*14:19:02* File "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/stomp_test.py", line 95, in test_echo*14:19:02* str(uuid4())),*14:19:02* File "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/lib/yajsonrpc/jsonrpcclient.py", line 77, in callMethod*14:19:02* raise exception.JsonRpcNoResponseError(method=methodName)*14:19:02* JsonRpcNoResponseError: No response for JSON-RPC request: {'method': 'echo'}*14:19:02* -------------------- >> begin captured logging << --------------------*14:19:02* 2018-06-27 14:17:54,524 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Creating socket (host='::1', port=0, family=10, socketype=1, proto=6) (protocoldetector:225)*14:19:02* 2018-06-27 14:17:54,526 INFO (MainThread) [vds.MultiProtocolAcceptor] Listening at ::1:36713 (protocoldetector:183)*14:19:02* 2018-06-27 14:17:54,535 DEBUG (MainThread) [Scheduler] Starting scheduler test.Scheduler (schedule:98)*14:19:02* 2018-06-27 14:17:54,537 DEBUG (test.Scheduler) [Scheduler] START thread <Thread(test.Scheduler, started daemon 140562082535168)> (func=<bound method Scheduler._run of <vdsm.schedule.Scheduler object at 0x7fd74ca00390>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,538 DEBUG (test.Scheduler) [Scheduler] started (schedule:140)*14:19:02* 2018-06-27 14:17:54,546 DEBUG (JsonRpc (StompReactor)) [root] START thread <Thread(JsonRpc (StompReactor), started daemon 140562629256960)> (func=<bound method StompReactor.process_requests of <yajsonrpc.stompserver.StompReactor object at 0x7fd74ca006d0>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,547 DEBUG (MainThread) [Executor] Starting executor (executor:128)*14:19:02* 2018-06-27 14:17:54,549 DEBUG (MainThread) [Executor] Starting worker jsonrpc/0 (executor:286)*14:19:02* 2018-06-27 14:17:54,553 DEBUG (jsonrpc/0) [Executor] START thread <Thread(jsonrpc/0, started daemon 140562612471552)> (func=<bound method _Worker._run of <Worker name=jsonrpc/0 waiting task#=0 at 0x7fd74ca00650>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,554 DEBUG (jsonrpc/0) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 14:17:54,557 DEBUG (MainThread) [Executor] Starting worker jsonrpc/1 (executor:286)*14:19:02* 2018-06-27 14:17:54,558 DEBUG (MainThread) [Executor] Starting worker jsonrpc/2 (executor:286)*14:19:02* 2018-06-27 14:17:54,559 DEBUG (jsonrpc/2) [Executor] START thread <Thread(jsonrpc/2, started daemon 140562620864256)> (func=<bound method _Worker._run of <Worker name=jsonrpc/2 waiting task#=0 at 0x7fd74c9fb350>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,560 DEBUG (jsonrpc/2) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 14:17:54,561 DEBUG (MainThread) [Executor] Starting worker jsonrpc/3 (executor:286)*14:19:02* 2018-06-27 14:17:54,562 DEBUG (jsonrpc/3) [Executor] START thread <Thread(jsonrpc/3, started daemon 140562124498688)> (func=<bound method _Worker._run of <Worker name=jsonrpc/3 waiting task#=0 at 0x7fd74bc80290>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,563 DEBUG (jsonrpc/3) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 14:17:54,564 DEBUG (MainThread) [Executor] Starting worker jsonrpc/4 (executor:286)*14:19:02* 2018-06-27 14:17:54,565 DEBUG (jsonrpc/4) [Executor] START thread <Thread(jsonrpc/4, started daemon 140562116105984)> (func=<bound method _Worker._run of <Worker name=jsonrpc/4 waiting task#=0 at 0x7fd74bc80790>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,566 DEBUG (jsonrpc/4) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 14:17:54,568 DEBUG (jsonrpc/1) [Executor] START thread <Thread(jsonrpc/1, started daemon 140562132891392)> (func=<bound method _Worker._run of <Worker name=jsonrpc/1 waiting task#=0 at 0x7fd74c9fb690>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,569 DEBUG (jsonrpc/1) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 14:17:54,569 DEBUG (MainThread) [Executor] Starting worker jsonrpc/5 (executor:286)*14:19:02* 2018-06-27 14:17:54,570 DEBUG (jsonrpc/5) [Executor] START thread <Thread(jsonrpc/5, started daemon 140562107713280)> (func=<bound method _Worker._run of <Worker name=jsonrpc/5 waiting task#=0 at 0x7fd74bc80090>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,571 DEBUG (jsonrpc/5) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 14:17:54,572 DEBUG (MainThread) [Executor] Starting worker jsonrpc/6 (executor:286)*14:19:02* 2018-06-27 14:17:54,580 DEBUG (MainThread) [Executor] Starting worker jsonrpc/7 (executor:286)*14:19:02* 2018-06-27 14:17:54,603 DEBUG (jsonrpc/6) [Executor] START thread <Thread(jsonrpc/6, started daemon 140562099320576)> (func=<bound method _Worker._run of <Worker name=jsonrpc/6 waiting task#=0 at 0x7fd74d0dacd0>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,604 DEBUG (jsonrpc/6) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 14:17:54,615 DEBUG (jsonrpc/7) [Executor] START thread <Thread(jsonrpc/7, started daemon 140562090927872)> (func=<bound method _Worker._run of <Worker name=jsonrpc/7 waiting task#=0 at 0x7fd74bfe0310>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,616 DEBUG (JsonRpcServer) [root] START thread <Thread(JsonRpcServer, started daemon 140561730238208)> (func=<bound method JsonRpcServer.serve_requests of <yajsonrpc.JsonRpcServer object at 0x7fd74ca00690>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,618 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Adding detector <yajsonrpc.stompserver.StompDetector instance at 0x7fd74c28cc68> (protocoldetector:210)*14:19:02* 2018-06-27 14:17:54,625 INFO (Detector thread) [ProtocolDetector.AcceptorImpl] Accepted connection from ::1:52432 (protocoldetector:61)*14:19:02* 2018-06-27 14:17:54,626 DEBUG (Detector thread) [ProtocolDetector.Detector] Using required_size=11 (protocoldetector:89)*14:19:02* 2018-06-27 14:17:54,627 DEBUG (jsonrpc/7) [Executor] Worker started (executor:298)*14:19:02* 2018-06-27 14:17:54,634 DEBUG (MainThread) [jsonrpc.AsyncoreClient] Sending response (stompclient:293)*14:19:02* 2018-06-27 14:17:54,634 DEBUG (Client ::1:36713) [root] START thread <Thread(Client ::1:36713, started daemon 140561713452800)> (func=<bound method Reactor.process_requests of <yajsonrpc.betterAsyncore.Reactor object at 0x7fd74bdb1d90>>, args=(), kwargs={}) (concurrent:193)*14:19:02* 2018-06-27 14:17:54,641 INFO (Detector thread) [ProtocolDetector.Detector] Detected protocol stomp from ::1:52432 (protocoldetector:125)*14:19:02* 2018-06-27 14:17:54,645 INFO (Detector thread) [Broker.StompAdapter] Processing CONNECT request (stompserver:94)*14:19:02* 2018-06-27 14:17:54,648 DEBUG (Client ::1:36713) [yajsonrpc.protocols.stomp.AsyncClient] Stomp connection established (stompclient:137)*14:19:02* 2018-06-27 14:17:54,651 DEBUG (jsonrpc/0) [jsonrpc.JsonRpcServer] Calling 'echo' in bridge with [u'Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut en'] (__init__:328)*14:19:02* 2018-06-27 14:17:54,652 DEBUG (jsonrpc/0) [jsonrpc.JsonRpcServer] Return 'echo' in bridge with Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut en (__init__:355)*14:19:02* 2018-06-27 14:17:54,653 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call echo succeeded in 0.01 seconds (__init__:311)*14:19:02* 2018-06-27 14:17:54,661 INFO (Detector thread) [Broker.StompAdapter] Subscribe command received (stompserver:123)*14:19:02* 2018-06-27 14:17:54,662 DEBUG (Detector thread) [protocoldetector.StompDetector] Stomp detected from ('::1', 52432) (stompserver:412)*14:19:02* 2018-06-27 14:18:09,649 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Stopping Acceptor (protocoldetector:214)*14:19:02* 2018-06-27 14:18:09,650 INFO (MainThread) [jsonrpc.JsonRpcServer] Stopping JsonRPC Server (__init__:441)*14:19:02* 2018-06-27 14:18:09,651 DEBUG (MainThread) [Executor] Stopping executor (executor:137)*14:19:02* 2018-06-27 14:18:09,652 DEBUG (Client ::1:36713) [root] FINISH thread <Thread(Client ::1:36713, started daemon 140561713452800)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,652 DEBUG (JsonRpcServer) [root] FINISH thread <Thread(JsonRpcServer, started daemon 140561730238208)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,654 DEBUG (JsonRpc (StompReactor)) [root] FINISH thread <Thread(JsonRpc (StompReactor), started daemon 140562629256960)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,655 DEBUG (jsonrpc/2) [Executor] Worker stopped (executor:303)*14:19:02* 2018-06-27 14:18:09,658 DEBUG (jsonrpc/3) [Executor] Worker stopped (executor:303)*14:19:02* 2018-06-27 14:18:09,659 DEBUG (jsonrpc/4) [Executor] Worker stopped (executor:303)*14:19:02* 2018-06-27 14:18:09,660 DEBUG (jsonrpc/1) [Executor] Worker stopped (executor:303)*14:19:02* 2018-06-27 14:18:09,660 DEBUG (jsonrpc/5) [Executor] Worker stopped (executor:303)*14:19:02* 2018-06-27 14:18:09,660 DEBUG (jsonrpc/6) [Executor] Worker stopped (executor:303)*14:19:02* 2018-06-27 14:18:09,665 DEBUG (jsonrpc/6) [Executor] FINISH thread <Thread(jsonrpc/6, started daemon 140562099320576)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,661 DEBUG (jsonrpc/7) [Executor] Worker stopped (executor:303)*14:19:02* 2018-06-27 14:18:09,662 DEBUG (jsonrpc/2) [Executor] FINISH thread <Thread(jsonrpc/2, started daemon 140562620864256)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,663 DEBUG (jsonrpc/3) [Executor] FINISH thread <Thread(jsonrpc/3, started daemon 140562124498688)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,663 DEBUG (jsonrpc/1) [Executor] FINISH thread <Thread(jsonrpc/1, started daemon 140562132891392)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,664 DEBUG (jsonrpc/4) [Executor] FINISH thread <Thread(jsonrpc/4, started daemon 140562116105984)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,664 DEBUG (jsonrpc/0) [Executor] Worker stopped (executor:303)*14:19:02* 2018-06-27 14:18:09,665 DEBUG (jsonrpc/5) [Executor] FINISH thread <Thread(jsonrpc/5, started daemon 140562107713280)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,667 DEBUG (jsonrpc/7) [Executor] FINISH thread <Thread(jsonrpc/7, started daemon 140562090927872)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,667 DEBUG (MainThread) [Executor] Waiting for worker jsonrpc/0 (executor:290)*14:19:02* 2018-06-27 14:18:09,671 DEBUG (jsonrpc/0) [Executor] FINISH thread <Thread(jsonrpc/0, started daemon 140562612471552)> (concurrent:196)*14:19:02* 2018-06-27 14:18:09,673 DEBUG (MainThread) [Executor] Waiting for worker jsonrpc/1 (executor:290)*14:19:02* 2018-06-27 14:18:09,674 DEBUG (MainThread) [Executor] Waiting for worker jsonrpc/6 (executor:290)*14:19:02* 2018-Coverage.py warning: Module /home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/vdsm was never imported. (module-not-imported)*14:19:05* pylint installdeps: pylint==1.8*14:19:22* pylint installed: The directory '/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.,astroid==1.6.5,backports.functools-lru-cache==1.5,backports.ssl-match-hostname==3.5.0.1,blivet==0.61.15.69,chardet==2.2.1,configparser==3.5.0,coverage==4.4.1,decorator==3.4.0,enum34==1.1.6,funcsigs==1.0.2,futures==3.2.0,iniparse==0.4,ioprocess==1.1.0,ipaddress==1.0.16,IPy==0.75,isort==4.3.4,kitchen==1.1.1,lazy-object-proxy==1.3.1,libvirt-python==3.9.0,Magic-file-extensions==0.2,mccabe==0.6.1,mock==2.0.0,netaddr==0.7.18,ovirt-imageio-common==1.4.1,pbr==3.1.1,pluggy==0.6.0,policycoreutils-default-encoding==0.1,pthreading==0.1.3,py==1.5.4,pycurl==7.19.0,pygpgme==0.3,pyinotify==0.9.4,pykickstart==1.99.66.18,pyliblzma==0.5.3,pylint==1.8.0,pyparted==3.9,python-augeas==0.5.0,python-dateutil==2.4.2,pyudev==0.15,pyxattr==0.5.1,PyYAML==3.10,requests==2.6.0,sanlock-python==3.6.0,seobject==0.1,sepolicy==1.1,singledispatch==3.4.0.3,six==1.11.0,subprocess32==3.2.6,tox==2.9.1,urlgrabber==3.10,urllib3==1.10.2,virtualenv==16.0.0,WebOb==1.2.3,wrapt==1.10.11,yum-metadata-parser==1.1.4*14:19:22* pylint runtests: PYTHONHASHSEED='528910716'*14:19:22* pylint runtests: commands[0] | pylint --errors-only static/usr/share/vdsm/sitecustomize.py lib/vdsm lib/vdsmclient lib/yajsonrpc*14:19:23* Problem importing module base.pyc: cannot import name get_node_last_lineno*14:19:24* Problem importing module base.py: cannot import name get_node_last_lineno*14:19:34* 06-27 14:18:09,674 DEBUG (MainThread) [Executor] Waiting for worker jsonrpc/7 (executor:290)*14:19:34* 2018-06-27 14:18:09,675 DEBUG (MainThread) [Executor] Waiting for worker jsonrpc/5 (executor:290)*14:19:34* 2018-06-27 14:18:09,675 DEBUG (MainThread) [Executor] Waiting for worker jsonrpc/2 (executor:290)*14:19:34* 2018-06-27 14:18:09,676 DEBUG (MainThread) [Executor] Waiting for worker jsonrpc/3 (executor:290)*14:19:34* 2018-06-27 14:18:09,676 DEBUG (MainThread) [Executor] Waiting for worker jsonrpc/4 (executor:290)*14:19:34* 2018-06-27 14:18:09,677 DEBUG (MainThread) [Scheduler] Stopping scheduler test.Scheduler (schedule:110)*14:19:34* 2018-06-27 14:18:09,678 DEBUG (test.Scheduler) [Scheduler] stopped (schedule:143)*14:19:34* 2018-06-27 14:18:09,679 DEBUG (test.Scheduler) [Scheduler] FINISH thread <Thread(test.Scheduler, started daemon 140562082535168)> (concurrent:196)*14:19:34* --------------------- >> end captured logging << ---------------------

4 10

Request for reviews - vdsm-tool update-volume
by Germano Veit Michel 29 Nov '18

29 Nov '18

Hi, I'm working an a tool (vdsm-tool update-volume) to make modifying SD metadata easier and more importantly, safer. This is very useful to recover from failed LSMs or snapshot issues. The plan is to use the VDSM API (modified by some of these patches) and add a tool (vdsm-tool) that talks to the API and modifies the volumes metadata as required by the user. Currently this is done manually, i.e.: looking at MD_XXX tags, doing dd, sed and then dd back to the storage. Any wrong argument (like a skip in place of a seek) can ruin the entire metadata, so this tool can be quite handy. The code is not necessarily 100% finished yet, but I've been testing this for some time and it seems ok from a functional point of view. I'm just not sure everything I did (especially inside VDSM, example 94366) is correct. Your comments on what can/should be improved are very welcome at this point. Please see this series and help reviewing it. https://gerrit.ovirt.org/#/q/topic:update-volume+(status:open+OR+status:mer… https://gerrit.ovirt.org/#/c/93258/ Thanks, Germano

2 9

[ovirt-ansible] inventory plugin
by verschueren.bram＠gmail.com 22 Nov '18

22 Nov '18

Hi, Some while ago I started working on an Ansible inventory plugin for ovirt. Now I just noticed there was a ticket opened by Ondra (#45104) on the github repo and I wonder if anyone is actively working on this, or if you would consider to adopt the plugin I created. I've added it to my repo at https://github.com/bverschueren/ansible/blob/ovirt_inventory_plugin/lib/ans… Regards, Bram

3 4

Fwd: Fedora 30 System-Wide Change: Deprecating /etc/sysconfig/nfs
by Sandro Bonazzola 01 Nov '18

01 Nov '18

FYI ---------- Forwarded message --------- From: Ben Cotton <bcotton(a)redhat.com> Date: mer 17 ott 2018 alle ore 15:29 Subject: Fedora 30 System-Wide Change: Deprecating /etc/sysconfig/nfs To: <devel(a)lists.fedoraproject.org>, <devel-announce(a)lists.fedoraproject.org > https://fedoraproject.org/wiki/Changes/nfs.conf == Summary == Deprecate /etc/sysconfig/nfs and only use /etc/nfs.conf to configure NFS daemons. == Owner == * Name: Steve Dickson * Email: steved(a)redhat.com == Detailed Description == Since the beginning /etc/sysconfig/nfs has been used to configure the NFS server daemons by supply command line arguments to the daemons or commands via SysVinit scripts. Then systemd(1) came along and the idea of daemons self-configuration was started. Meaning daemons and commands would get their configurations from a file, not the command line like with SysVinit scripts. Back in late 2016, Neil Brown from SuSe, implemented this changed. He built into each daemon the ability to read from one central file, /etc/nfs.conf. See nfs.conf(5) for details. After this work made it upstream, I a wrote patch that added back the ability to use /etc/sysconfig/nfs to maintain backwards compatibility which has lasted for the last few Fedora releases. I think at this point, the timing is right to introduce this single file configuration to Fedora 30. == Benefit to Fedora == * Having a single file configuration will help IT automation systems like Ansible configure NFS servers. * This change also simplifies the systemd scrips. * Having two ways of configuring NFS is not desirable. The only reason there has been no problems is because nobody know about /etc/nfs.conf * There is a new command, nfsconf(8), that checks the correctness of /etc/nfs.conf == Scope == * Proposal owners: Steve Dickson <steved(a)redhat.com> * Other developers: Justin Mitchell <jumitche(a)redhat.com> * Release engineering: [https://pagure.io/releng/issue/7864 #7864 F30: Deprecating /etc/sysconfig/nfs] ** List of deliverables: nfs-utils-2.3.3-1.fc30 * Policies and guidelines: The guidelines to use /etc/nfs.conf are already being install with nfs.conf(5) and nfsconf(8) manpages * Trademark approval: No trademarks are being changed so no approval is needed. == Upgrade/compatibility impact == In [https://bugzilla.redhat.com/show_bug.cgi?id=1619270 BZ1619270] a python script that will convert a sysconfig/nfs config into nfs.conf config. There are a couple thoughts on how to use it. On clean installs, when sysconfig/nfs does not exist, sysconfig/nfs wil still be installed with directions to use nfs.conf to do the configuration. When sysconfig/nfs does exist, the configuration will '''not''' be overwritten, but the systemd scripts will not use the file to configure NFS. The two thoughts on how to use python script: # Have the upgrade run the script and maybe throw out a message that the configuration has now been moved to nfs.conf # Throw a message indicating the NFS configuration has changed and then have the admin run the script The first thought is probably the cleanest but changing configurations behind admin's back is not very nice... I am very open on how to use this script. == How To Test == With the new nfsconf(8) command, the nfs.conf can be tested for correctness, other than that, we should do the same testing as we do today == User Experience == After the initial shock, I think users will embrace the new configuration. Being able to configure NFS via IT automation systems (aka Ansible) is a step in the right direction. Having a command to check the correctness of the configuration will be welcome. == Dependencies == There are no dependencies that I know of. == Contingency Plan == * Contingency mechanism: Revert the commit that removed support for /etc/sysconfig/nfs. * Contingency deadline: 2019-03-05 (Beta Freeze) * Blocks release? No * Blocks product? No == Documentation == There are two man pages, nfs.conf(5) and nfsconf(8). == Release Notes == The new way of configuring NFS should be release noted. -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

2 1

Query regarding OST test suite execution
by viraj shirsat 31 Oct '18

31 Oct '18

Hi , Good Morning :) This is regarding OST tool setup i need some help on the same. Please find below details. My Setup : 1> Setup one open source ovirt engine 2> Setup one node and added the same on ovrit engine 3> Setup one VM for OST tool with following dependencies. 1.Setup LAGO 2.Git Clone OST 3.Install MOCK *Please let me know if i am missing anything* Query : I am trying to run the OST from local machine but i am not able to figure sequence of the steps to execute . Can i get an sample sequence steps how to run any test suite(any). Error : [root@localhost lago]# lago status Unable to find workdir in /jenkins/jobs/confs/projects/lago What is workdir here, m i missing some thing ? Waiting for your reply :) Thanks in Advance Viraj

2 1

planned Jenkins restart
by Evgheni Dereveanchin 31 Oct '18

31 Oct '18

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

1 1

Decipher traffic between ovirt-engine and ovirt-node (vdsm)
by Anastasiya Ruzhanskaya 29 Oct '18

29 Oct '18

Hello! I was successful in deciphering the traffic between the client and ovirt-engine, actually, only by dumping the premaster key from the browser, which was generated during the session and providing it to wireshark. How it can be done for ovirt-engine and vdsm communication? Should the engine private key be provided? Actually to my surprise I don't see any ssl communication between engine and node when for example turn on the virtual machine, only tcp packets. But this page https://ovirt.org/develop/release-management/features/infra/pki/ states that there should be one. And also should I look for any xml rpc dissector? I know that for example virt-manager uses rpc protocol, I found a dissector for that case, but seems I need another one here.

3 14

ovirt engine certificate password
by Anastasiya Ruzhanskaya 28 Oct '18

28 Oct '18

Hello everyone! I am trying to analyze traffic between ovirt-engine and vdsm. First strange thing is, that it should be encrypted by default . When I listen in wireshark for message from engine to vdsm being on the engine machine, the traffic is not encrypted. It is only tcp. I expect it then be acceptable for wireshark json dissector. But this is not a json. Is this a normal situation or I should set up encryption by myself? However, on the guest machine, I see in wireshark that the traffic between engine and vdsm is encrypted. ( I have a configuration of my computer as a client and two VMs as engine and node). So , I am trying to use engine's private key to decrypt it. The private key is not engine_id_rsa (am I right?), but it is hidden inside .p12 file. To extract the key from this file I need a password. During the ovirt installing I didn't set up any password for this. Is this maybe a default one? How can I extract a private key? So, the final questions are: 1) Should the traffic between engine and vdsm be encrypted by default? 2) How the private key for engine can be extracted?

2 1

Conflicting ovs-2.10 and dpdk libraries
by Miguel Duarte de Mora Barroso 26 Oct '18

26 Oct '18

Hello all, I've seen many of you reach this same problem over the last week when updating ovirt-engine - or node - to the 4.3 candidate. The following is an excerpt of the error: -> Finished Dependency Resolution Error: Package: 1:openvswitch-ovn-common-2.10.0-1.el7.x86_64 (centos-ovirt43-testing) Requires: librte_pmd_mlx4.so.1()(64bit) Available: dpdk-17.11-13.el7.x86_64 (rhel-7.6-extras) librte_pmd_mlx4.so.1()(64bit) Installed: 2:dpdk-17.11-3.el7.x86_64 (@centos-ovirt43-testing) Not found Error: Package: 1:openvswitch-ovn-common-2.10.0-1.el7.x86_64 (centos-ovirt43-testing) Requires: librte_power.so.1()(64bit) Available: dpdk-17.11-13.el7.x86_64 (rhel-7.6-extras) librte_power.so.1()(64bit) Installed: 2:dpdk-17.11-3.el7.x86_64 (@centos-ovirt43-testing) Not found Error: Package: 1:openvswitch-ovn-common-2.10.0-1.el7.x86_64 (centos-ovirt43-testing) Requires: librte_pmd_mlx5.so.1()(64bit) Available: dpdk-17.11-13.el7.x86_64 (rhel-7.6-extras) librte_pmd_mlx5.so.1()(64bit) Installed: 2:dpdk-17.11-3.el7.x86_64 (@centos-ovirt43-testing) Not found ... Should you stumble into this situation, remove the currently installed dpdk version (yum remove "dpdk*") then install it again - this time assuring it is installed from the extras repo. After that, installation should proceed smoothly. Regards, Miguel

1 0

ovirt-engine has been tagged (ovirt-engine-4.2.7.3)
by Tal Nisan 25 Oct '18

25 Oct '18

1 1

Re: [EXTERNAL] Re: List of Queries related to RHV
by Pavan Chavva 25 Oct '18

25 Oct '18

Bumping this thread as the last update from Veritas did not reflect in OVirt Devel list. Best, Pavan. On Wed, Oct 17, 2018 at 10:03 AM Mahesh Falmari <Mahesh.Falmari(a)veritas.com> wrote: > Thanks for the prompt response on these queries. We have few follow-up > queries mentioned inline. > > > > Thanks & Regards, > Mahesh Falmari > > > > *From:* Yaniv Lavi <ylavi(a)redhat.com> > *Sent:* Tuesday, October 16, 2018 7:19 PM > *To:* Mahesh Falmari <Mahesh.Falmari(a)veritas.com> > *Cc:* Nir Soffer <nsoffer(a)redhat.com>; Erez, Daniel <derez(a)redhat.com>; > Tal Nisan <tnisan(a)redhat.com>; Pavan Chavva <pchavva(a)redhat.com>; devel < > devel(a)ovirt.org>; James Olson <James.Olson(a)veritas.com>; Navin Tah < > Navin.Tah(a)veritas.com>; Sudhakar Paulzagade < > Sudhakar.Paulzagade(a)veritas.com>; Abhay Marode <Abhay.Marode(a)veritas.com>; > Suchitra Herwadkar <Suchitra.Herwadkar(a)veritas.com>; Nirmalya Sirkar < > Nirmalya.Sirkar(a)veritas.com>; Abhijeet Barve <Abhijeet.Barve(a)veritas.com> > *Subject:* [EXTERNAL] Re: List of Queries related to RHV > > > > > *YANIV LAVI* > > SENIOR TECHNICAL PRODUCT MANAGER > > Red Hat Israel Ltd. <https://www.redhat.com/> > > 34 Jerusalem Road, Building A, 1st floor > > Ra'anana, Israel 4350109 > > ylavi(a)redhat.com T: +972-9-7692306/8272306 F: +972-9-7692223 > IM: ylavi > > <https://red.ht/sig> > > *TRIED. TESTED. TRUSTED.* <https://redhat.com/trusted> > > @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> > > > > On Tue, Oct 16, 2018 at 4:35 PM Mahesh Falmari <Mahesh.Falmari(a)veritas.com> > wrote: > > Hi Nir, > > We have few queries with respect to RHV which we would like to understand > from you. > > > > *1. Does RHV maintains the virtual machine configuration file in back end?* > > Just like we have configuration files for other hypervisors like for > VMware it is .vmx and for Hyper-V, it is .vmcx which captures most of the > virtual machine configuration information in that. On the similar lines, > does RHV also maintains such file? If not, what is the other way to get all > the virtual machine configuration information from a single API? > > > > There is a OVF storage, but this is not meant for consumption. > > Please follow the first section in: > > *https://ovirt.org/develop/release-management/features/storage/backup-restore-disk-snapshots/ > <https://ovirt.org/develop/release-management/features/storage/backup-restor…>* > > This explains how to use the API to get a OVF for a VM. > > > > > > *2. Is VM UUID the only way to uniquely identify virtual machine in the > RHV infrastructure?* > > What we understand is that VM UUID is the way to identify virtual machine > uniquely in the RHV infrastructure. Would like to know any other way than > this? > > > > UUID is the way to do this. > > > > > > *3. Do we have any version associated with the virtual machine?* > > Just like we have hardware version in case of VMware and virtual machine > version in case of Hyper-V, does RHV also associate any such version with > virtual machine? > > > > The HW version is based on the VM machine type. > > [Mahesh] Can you please elaborate more on this? How simply VM machine > type going to determine it’s version? > > > > *4. Is it possible to create virtual machines with QCOW2 as base disks > instead of RAW?* > > We would like to understand if there are any use cases customers prefer > creating virtual machines from QCOW2 as base disks instead of RAW ones. > > > > That is a possibility in cases of thin disk on file storage. > > [Mahesh] Can you please elaborate more on this? > > > > *5. RHV Deployment* > > What kind of deployments you have come across in the field? Does customers > scale their infrastructure by adding more datacenters/clusters/nodes or > they add more RHV managers? What scenarios trigger having more than one RHV > manager? > > > > We are all kind with oVirt. I depends on the use case. > > > > > > *6. Image transfer* > > We are trying to download disk chunks using multiple threads to improve > performance of reading data from RHV. Downloading 2 disk chunks > simultaneously via threads should take approximately the same time. But > from our observations this takes roughly 1.5 times. > Can RHVM server requests in parallel, if so are there any settings that > need to be tweaked? > > Here is an example: > Request 1 for chunk 1 from thread 1, Range: bytes=0-1023 > Request 2 for chunk 2 from thread 2, Range: bytes=1024-2047 > Takes roughly 1.5 seconds, whereas a single request would take 1 second. > Expecting it to take just around 1 second. > > [Mahesh] Seeking response to this query. > > *7. Free and Thaw operation* > > For cinder based VM, API recommended for FS consistent backup. > > - POST /api/vms/<ID>/freezefilesystems > - POST /api/vms/<ID>/thawfilesystems > > Why do we need this whereas it is not required for other storage? > > Creating a snapshot does this for you in a case where you have the oVirt > guest agent install on the guest. > > [Mahesh] Thanks, we would also like to understand is there a way to > control crash/app consistent snapshots through REST APIs? > > > > Thanks & Regards, > Mahesh Falmari > > > > -- PAVAN KUMAR CHAVVA ENGINEERING PARTNER MANAGER Red Hat pchavva(a)redhat.com M: 4793219099 IM: pchavva

2 1

Parsing gwt rpc messages
by Anastasiya Ruzhanskaya 25 Oct '18

25 Oct '18

Hello everyone! I am trying to determine how the person who knows for example all necessary function calls and parameters can determine the content of the message sent. This is an example of the message I am trying to parse (I already separated it on some meaningful parts), numbers in braces just help to make correspondence between payload and strings: 7| 0| 14| (1)https://engine.localdomain/ovirt-engine/webadmin/| //URL (2)E8B2AD24442204349EF795039C3B87E5| // policy name (3)org.ovirt.engine.ui.frontend.gwtservices.GenericApiGWTService| service interface (4)runMultipleActions| name of the method (5)org.ovirt.engine.core.common.action.ActionType/12242454|, (6)java.util.ArrayList/4159755760|, (7)Z| ( two times)) // bool type (8)org.ovirt.engine.core.common.action.ShutdownVmParameters/1694554255| (9)org.ovirt.engine.core.compat.Guid/1992968158| (10)java.util.UUID/2940008275| (11)org.ovirt.engine.core.common.action.ActionParametersBase$EndProcedure/1568822488| (12)java.util.Collections$EmptyMap/4174664486| (13)org.ovirt.engine.core.common.businessentities.VDSStatus/1938301532| (14)org.ovirt.engine.core.compat.TransactionScopeOption/1475850853| (the following is the payload separated and commented in places where I can understand it) 1| 2| 3| 4| 4|- 4 method parameters 5|- first type = ActionType 6|- second type = arraylist 7|- third type = boolean 7|- fourth type = boolean 5(actionType)|9 (shutdown)| 6(arrayList)|1(??)| 8 (shutdown vm parameters, list object)|1|0|0|0|(??) 9 (guid, ?)|10(UUID)|J$m4mk9wVi3|MjeP460Xkpb (vm uuid)|0|5|0|0|0|11|1|0|6|0|0|0|0|0|0|12|0|-6|13|0|1|0|1|14|2|0|0|0|0|0| Until vm uuid parameter it is kind of clear what is happening, but I still wonder what do the parameters 1 and 0 mean in places marked as (??). I understand, that there is a method called runMultipleActions and it has four parameters. I found in source examples of calling this method (ovirt-engine/frontend/webadmin/modules/./frontend/src/test/java/org/ovirt/engine/ui/frontend/FrontendActionTest.java).Then I determine types of these parameters. Then the type of action performed ( I shut down the machine). Then there should be an ArrayList, which contains several objects. I assume that 8(shutdown vm parameters) should follow right after 6 (arraylist), but there a "1" which I can't explain. Also for shutdown parameters: I see in examples that there are not so many boolean parameters in constructor there. Here are four! (1|0|0|0) What do they mean? And how can I cope with the left payload? Thank you in advance for any help! P.S. Also vm ids have another format when for example I do the same actions from web - ui: c8de3f8e-b45e-4a5b-9fa6-e2693dc158b7. Why this is so?

2 3

jobs failure due to same package version with different checksum
by Dafna Ron 25 Oct '18

25 Oct '18

Hi, We have been having failure in master for different projects due to package ovirt-ansible-disaster-recovery-1.1.2-1.el7.noarch.rpm. It seems the package had been changed without a new version set which means we have the same exact package with two different checksum (one in 4.2 and one in master): ovirt-4.2: [dron@resources02 noarch]$ md5sum ovirt-ansible-disaster-recovery-1.1.2-1.el7.noarch.rpm 07b2c6c7ef94e48be3c197e2a1d45d81 ovirt-ansible-disaster-recovery-1.1.2-1.el7.noarch.rpm ovirt-master: [dron@resources02 noarch]$ md5sum ovirt-ansible-disaster-recovery-1.1.2-1.el7.noarch.rpm f6b2e88ae07b64d5071696ade510d961 ovirt-ansible-disaster-recovery-1.1.2-1.el7.noarch.rpm Can you please create a new package with version change to solve this problem? Thanks, Dafna

2 3

How does the host synchronizes existing storage domains when added to engine?
by Tianyuan Wang 25 Oct '18

25 Oct '18

hi all, We are developing for supporting ceph as a new storage domain type. It went well when creating and using. But we cannot add a new host to the engine when there is already a ceph-StorageDomain. The engine reports "VDSM node1 command ConnectStoragePoolVDS failed: Cannot find master domain" and set the node to "Non Operational" status. The vdsm log reports error like this: INFO (jsonrpc/0) [vdsm.api] FINISH connectStoragePool error=Cannot find master domain: u'spUUID=5bc95ba9-01f7-0307-0342-000000000033, msdUUID=a3d6903d-07d5-4794-9667-9dddc3c84fe6' from=::ffff:192.168.122.22,40166, flow_id=43b39e00, task_id=4128f9d4-3c92-46ed-a230-2505d3a8ddb9 (api:50) 2018-10-24 11:06:22,227+0800 ERROR (jsonrpc/0) [storage.TaskManager.Task] (Task='4128f9d4-3c92-46ed-a230-2505d3a8ddb9') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in connectStoragePool File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1032, in connectStoragePool spUUID, hostID, msdUUID, masterVersion, domainsMap) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1094, in _connectStoragePool res = pool.connect(hostID, msdUUID, masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 704, in connect self.__rebuild(msdUUID=msdUUID, masterVersion=masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1275, in __rebuild self.setMasterDomain(msdUUID, masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1488, in setMasterDomain raise se.StoragePoolMasterNotFound(self.spUUID, msdUUID) StoragePoolMasterNotFound: Cannot find master domain: u'spUUID=5bc95ba9-01f7-0307-0342-000000000033, msdUUID=a3d6903d-07d5-4794-9667-9dddc3c84fe6' After tracing back, I found that there is no local file path under /rhev/data-center/mnt for the storage domain, so it cannot find storage domain when ConnectStoargeSever runs. It only happens when adding a new host to engine and there is already a ceph-StroageDomain in ovirt. So how does the host synchronized the existing storage domains? And what can I do to fix this? Thanks in advance! Yours Sincerely, Tianyuan

3 2

Live merge of snapshot
by Abhay Marode 23 Oct '18

23 Oct '18

Hi, In case of snapshot creation and deletion of VM with chain of snapshots I observed following behavior while deleting the snapshot, * When VM is powered ON, I could see two events in event manager, 1) initiated snapshot deletion 2) snapshot deletion successful * When VM is powered OFF, I saw three events 1) initiated snapshot deletion 2) merge snapshot 'Active VM' into 'snap1' 3) snapshot deletion successful. Why there is difference in events based on power state of VM? Do we free up the storage in deletion of snapshot? Here are config details: Host OS Version: RHEL - 7.5 - 4.3.el7 OS Description: Red Hat Virtualization Host 4.2.4 (el7.5) Kernel Version: 3.10.0 - 862.6.3.el7.x86_64 KVM Version: 2.10.0 - 21.el7_5.4 LIBVIRT Version: libvirt-3.9.0-14.el7_5.6 VDSM Version: vdsm-4.20.31-1.el7ev SPICE Version: 0.14.0 - 2.el7_5.4 GlusterFS Version: glusterfs-3.8.4-54.10.el7rhgs CEPH Version: librbd1-0.94.5-2.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1 Regards, -Abhay

2 1

FOSDEM‘19 Virtualization & IaaS Devroom CfP
by Sandro Bonazzola 22 Oct '18

22 Oct '18

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2019, to be hosted on February 2nd 2019. This year will mark FOSDEM’s 19th anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. FOSDEM will be held once again in Brussels, Belgium, on February 2nd & 3rd, 2019. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, oVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 1st, 2018. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 1 December 2019 Acceptance notifications: 14 December 2019 Final schedule announcement: 21 December 2019 Devroom: 2nd February 2019 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Speaker Mentoring Program As a part of the rising efforts to grow our communities and encourage a diverse and inclusive conference ecosystem, we're happy to announce that we'll be offering mentoring for new speakers. Our mentors can help you with tasks such as reviewing your abstract, reviewing your presentation outline or slides, or practicing your talk with you. You may apply to the mentoring program as a newcomer speaker if you: - Never presented before or - Presented only lightning talks or - Presented full-length talks at small meetups (<50 ppl) Submission Guidelines Mentored presentations will have 25-minute slots, where 20 minutes will include the presentation and 5 minutes will be reserved for questions. The number of newcomer session slots is limited, so we will probably not be able to accept all applications. You must submit your talk and abstract to apply for the mentoring program, our mentors are volunteering their time and will happily provide feedback but won't write your presentation for you! If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. How to Apply In addition to agreeing to video recording and confirming that you can attend FOSDEM in case your session is accepted, please write "speaker mentoring program application" in the "Submission notes" field, and list any prior speaking experience or other relevant information for your application. Call for Mentors Interested in mentoring newcomer speakers? We'd love to have your help! Please email iaas-virt-devroom at lists.fosdem.org with a short speaker biography and any specific fields of expertise (for example, KVM, OpenStack, storage, etc.) so that we can match you with a newcomer speaker from a similar field. Estimated time investment can be as low as a 5-10 hours in total, usually distributed weekly or bi-weekly. Never mentored a newcomer speaker but interested to try? As the mentoring program coordinator, email Brian Proffitt[3] and he will be happy to answer your questions! Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance watching time for the speakers, and helping with video for the devroom. Please contact Brian Proffitt, for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://penta.fosdem.org/submission/FOSDEM17 [2] iaas-virt-devroom at lists.fosdem.org [3] bkp at redhat.com -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 14-09-2018 ] [ 002_bootstrap.add_hosts ]
by Dafna Ron 22 Oct '18

22 Oct '18

Hi, The previous regression was resolved and we now have a new regression. I don't think that the reported change is related so can someone from ovirt-engine take a look? The failure is add host on the upgrade suite. Please note that we have not had an engine-ovirt build for over 10 days due to several consecutive regressions and I would ask you to stop merging until we can stabilize the project and have a new package of engine. error: 2018-09-14 05:51:07,670-04 INFO [org.ovirt.engine.core.uutils.ssh.SSHDialog] (EE-ManagedThreadFactory-engine-Thread-1) [5c91fcbd] SSH execute 'root@lago-upgrade-from-release-suite-master-host-0' 'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar -b1 --warning=no-timestamp -C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True' 2018-09-14 05:51:08,550-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [5c91fcbd] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-upgrade-from-release-suite-master-host-0. Stage: Initializing. 2018-09-14 05:51:08,565-04 INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (VdsDeploy) [5c91fcbd] transaction rolled back 2018-09-14 05:51:08,574-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [5c91fcbd] Error during deploy dialog 2018-09-14 05:51:08,578-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (EE-ManagedThreadFactory-engine-Thread-1) [5c91fcbd] Error during host lago-upgrade-from-release-suite-master-host-0 install 2018-09-14 05:51:08,586-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [5c91fcbd] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host lago-upgrade-from-release-suite-master-host-0: CallableStatementCallback; SQL [{call insertauditlog(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}ERROR: invalid byte sequence for encoding "UTF8": 0x00; nested exception is org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00. 2018-09-14 05:51:08,586-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (EE-ManagedThreadFactory-engine-Thread-1) [5c91fcbd] Error during host lago-upgrade-from-release-suite-master-host-0 install, preferring first exception: CallableStatementCallback; SQL [{call insertauditlog(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}ERROR: invalid byte sequence for encoding "UTF8": 0x00; nested exception is org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 2018-09-14 05:51:08,586-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [5c91fcbd] Host installation failed for host 'e475e93a-63b3-4573-b242-162c2ed864f0', 'lago-upgrade-from-release-suite-master-host-0': CallableStatementCallback; SQL [{call insertauditlog(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}ERROR: invalid byte sequence for encoding "UTF8": 0x00; nested exception is org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 2018-09-14 05:51:08,615-04 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [5c91fcbd] START, SetVdsStatusVDSCommand(HostName = lago-upgrade-from-release-suite-master-host-0, SetVdsStatusVDSCommandParameters:{hostId='e475e93a-63b3-4573-b242-162c2ed864f0', status='InstallFailed', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 146cdc08 2018-09-14 05:51:08,626-04 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [5c91fcbd] FINISH, SetVdsStatusVDSCommand, return: , log id: 146cdc08 2018-09-14 05:51:08,639-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [5c91fcbd] EVENT_ID: VDS_INSTALL_FAILED(505), Host lago-upgrade-from-release-suite-master-host-0 installation failed. CallableStatementCallback; SQL [{call insertauditlog(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}ERROR: invalid byte sequence for encoding "UTF8": 0x00; nested exception is org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00. 2018-09-14 05:51:08,652-04 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [5c91fcbd] Lock freed to object 'EngineLock:{exclusiveLocks='[e475e93a-63b3-4573-b242-162c2ed864f0=VDS]', sharedLocks=''}' 2018-09-14 05:51:37,996-04 INFO [org.ovirt.engine.core.bll.quota.QuotaManager] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [] Quota Cache updated. (19 msec) (END) Thanks, Dafna

9 30

[VDSM] running tests locally
by Vojtech Juranek 20 Oct '18

20 Oct '18

Hi, beginner question: I'm trying to run some VDSM tests locally (e.g. blocksd_test.py), using PYTHON_EXE=python3 ./run_tests_local.sh storage/blocksd_test.py but I'm getting quite a lot of test failures. Most of the tests fail because of mokeypatch fixture is not injected (see error bellow). What I'm doing wrong and how I can run selected tests locally? Thanks in advance Vojta ERROR: storage.blocksd_test.test_meta_size_max_val ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) TypeError: test_meta_size_max_val() missing 1 required positional argument: 'monkeypatch'

3 4

[action required] install ovirt-engine-ui-extensions for "migrate" button and dashboard
by Greg Sheremeta 18 Oct '18

18 Oct '18

Hi, To proof-of-concept moving features from GWT to react, we moved the "migrate" functionality in admin portal from GWT to ovirt-engine-ui-extensions [1]. We also moved the dashboard there and dropped ovirt-engine-dashboard. Please install this new project in your dev environment and then follow the installation instructions in the README [2]. You can skip this in your dev environment if you don't need the dashboard or migrate. [1] https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-ui-extensions [2] https://github.com/oVirt/ovirt-engine-ui-extensions -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

1 0

oVirt 4.2.7 RC3 build blocked
by Sandro Bonazzola 17 Oct '18

17 Oct '18

hi, blocking 4.2.7 RC3 build due to jenkins jobs disappeared deleting the builds to be released. Affected build is: https://jenkins.ovirt.org/job/ovirt-provider-ovn_4.2_build-artifacts-el7-x8… Job has been deleted with: commit 54d376c3b98bf446725348ca6ebaefabdae891d8 (HEAD -> master, origin/master, origin/HEAD) Author: Dafna Ron <dron(a)redhat.com> Date: Tue Oct 16 11:43:57 2018 +0100 Removed ovirt-provider-ovn v1 jobs Jira-ticket: https://ovirt-jira.atlassian.net/browse/OVIRT-2543 Change-Id: I141cbce1a9faeffbd11b7377dd7992dc0cdbd5ea Signed-off-by: Dafna Ron <dron(a)redhat.com> I'm going to revert above patch and re-trigger the build for that package. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

2 2

[PTHREADING] No build for ppc64le and s390x, text fail on x86_64
by Nir Soffer 17 Oct '18

17 Oct '18

After adding Victor to jenkins whitelist, CI started to test https://gerrit.ovirt.org/#/c/94974/ But we have only x86_64 jobs. This kind of project must have jobs for all platforms. The last maintainer was Yaniv Bronhaim, so I guess nobody remember why we have only x86_64 builds. I hope someone can help to move the project to new stdci and add ppc64le and s390x builds. While I was writing this the build completed with this failure: 00:01:01.195 ========== Running the shellscript automation/check-patch.sh 00:01:01.204 ./automation/check-patch.sh: line 3: tox: command not found This worked when I added tox for fedora 25. Looks like we need a simple patch to get tox on el7/fc28. Nir

2 2

Re: List of Queries related to RHV
by Yaniv Lavi 16 Oct '18

16 Oct '18

YANIV LAVI SENIOR TECHNICAL PRODUCT MANAGER Red Hat Israel Ltd. <https://www.redhat.com/> 34 Jerusalem Road, Building A, 1st floor Ra'anana, Israel 4350109 ylavi(a)redhat.com T: +972-9-7692306/8272306 F: +972-9-7692223 IM: ylavi <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> On Tue, Oct 16, 2018 at 4:35 PM Mahesh Falmari <Mahesh.Falmari(a)veritas.com> wrote: > Hi Nir, > > We have few queries with respect to RHV which we would like to understand > from you. > > > > *1. Does RHV maintains the virtual machine configuration file in back end?* > > Just like we have configuration files for other hypervisors like for > VMware it is .vmx and for Hyper-V, it is .vmcx which captures most of the > virtual machine configuration information in that. On the similar lines, > does RHV also maintains such file? If not, what is the other way to get all > the virtual machine configuration information from a single API? > There is a OVF storage, but this is not meant for consumption. Please follow the first section in: *https://ovirt.org/develop/release-management/features/storage/backup-restore-disk-snapshots/ <https://ovirt.org/develop/release-management/features/storage/backup-restor…>* This explains how to use the API to get a OVF for a VM. > > > *2. Is VM UUID the only way to uniquely identify virtual machine in the > RHV infrastructure?* > > What we understand is that VM UUID is the way to identify virtual machine > uniquely in the RHV infrastructure. Would like to know any other way than > this? > UUID is the way to do this. > > > *3. Do we have any version associated with the virtual machine?* > > Just like we have hardware version in case of VMware and virtual machine > version in case of Hyper-V, does RHV also associate any such version with > virtual machine? > The HW version is based on the VM machine type. > > > *4. Is it possible to create virtual machines with QCOW2 as base disks > instead of RAW?* > > We would like to understand if there are any use cases customers prefer > creating virtual machines from QCOW2 as base disks instead of RAW ones. > That is a possibility in cases of thin disk on file storage. > > > *5. RHV Deployment* > > What kind of deployments you have come across in the field? Does customers > scale their infrastructure by adding more datacenters/clusters/nodes or > they add more RHV managers? What scenarios trigger having more than one RHV > manager? > We are all kind with oVirt. I depends on the use case. > > *6. Image transfer* > > We are trying to download disk chunks using multiple threads to improve > performance of reading data from RHV. Downloading 2 disk chunks > simultaneously via threads should take approximately the same time. But > from our observations this takes roughly 1.5 times. > Can RHVM server requests in parallel, if so are there any settings that > need to be tweaked? > > Here is an example: > Request 1 for chunk 1 from thread 1, Range: bytes=0-1023 > Request 2 for chunk 2 from thread 2, Range: bytes=1024-2047 > Takes roughly 1.5 seconds, whereas a single request would take 1 second. > Expecting it to take just around 1 second. > > > > *7. Free and Thaw operation* > > For cinder based VM, API recommended for FS consistent backup. > > - POST /api/vms/<ID>/freezefilesystems > - POST /api/vms/<ID>/thawfilesystems > > Why do we need this whereas it is not required for other storage? > Creating a snapshot does this for you in a case where you have the oVirt guest agent install on the guest. > > > Thanks & Regards, > Mahesh Falmari > > >

1 0

VDSM API schema inconsistencies
by Marcin Sobczyk 16 Oct '18

16 Oct '18

Hi, when I was working on BZ#1624306 it turned out, that even if I'd fix the help-printing code in vdsm-client, there's still a lot of inconsistencies in API's schema files. After some investigation, I found that there's a code for reporting schema inconsistencies, but it's turned off because it bloats the logs. There's also a "strict" mode that raises an exception each time an inconsistency is found, but it's also off because there's so many of them. I think that no one wants to maintain both: the actual code and schema files. My idea would be to make the schema derived from the code at build time as a long-term effort. Before we can do that though, we need to address the inconsistencies first. https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v… This is a series of patches that helps fixing schema issues. What it does, is it adds a bunch of information from stack to vastly ease the process of fixing them. The logging level is also changed from 'WARNING' to 'DEBUG'. Here's an example of a logged entry: Host.setKsmTune With message: Required property pages_to_scan is not provided when calling Host.setKsmTune With backtrace: [ [ "_verify_object_type", { "call_arg_keys":[ "merge_across_nodes", "run" ], "schema_type_name":"KsmTuneParams" } ], [ "_verify_complex_type", { "schema_type_type":"object" } ] ] To make it work, a patch for OST's 'basic-master-suite' is on the way that switches 'schema.inconsistency' logger's logging level do 'DEBUG'. That way, we can find all reported errors in 'vdsm-schema-error.log' files. An initial report that groups reported errors by namespaces/methods has also been made. Please note, that an implementation that completely avoids error duplicates is really hard and IMHO not worth the effort. You can find the results here: * Host: https://pastebin.com/YM2XnvTV * Image: https://pastebin.com/GRc1yErL * LVMVolumeGroup: https://pastebin.com/R1276gTu * SDM: https://pastebin.com/P3tfYEDD * StorageDomain: https://pastebin.com/Q0DxKgF5 * StoragePool: https://pastebin.com/VXFWpfRC * VM: https://pastebin.com/tDC60c29 * Volume: https://pastebin.com/TYkr9Zsd * |jobs|: https://pastebin.com/jeXpYyz9 * |virt|: https://pastebin.com/nRREuEub Regards, Marcin

2 4

vdsm has been tagged (v4.20.43)
by Milan Zamazal 16 Oct '18

16 Oct '18

Vdsm 4.20.43 for oVirt 4.2.7 rc3

1 0

vdsm has been tagged (v4.30.1)
by Milan Zamazal 15 Oct '18

15 Oct '18

Vdsm 4.30.1 for the first 4.3 build from master

1 0

Upgrade to WildFly 14.0.1
by Martin Perina 12 Oct '18

12 Oct '18

Hi, WildFly 14 packages are already available for both CentOS 7 and FC28, both oVirt engine master and 4.2 already contain fixes for compatibility with both WildFly 13 and 14, but please update your development machines to contain both ovirt-engine-wildfly-14.0.1 and ovirt-engine-wildfly-overlay-14.0.1 packages. Patch adding requirement for WildFly 14 is prepared [1], it should be merged tomorrow (Thursday), backport to 4.2 will follow immediately. Anyway if you find any issues related to this WildFly upgrade, please report a bug on it asap, we need to have everything fixed in 4.2.7. Thanks Martin [1] https://gerrit.ovirt.org/94824 -- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o.

1 1

diskunmap hooks and oVirt Node
by Sandro Bonazzola 11 Oct '18

11 Oct '18

Hi, we just got Bug 1638317 <https://bugzilla.redhat.com/show_bug.cgi?id=1638317> - "missing VDSM hook diskunmap in Node NG releases" opened as a bug, not an RFE, because "Pass discard from guest to underlying storage <https://www.ovirt.org/develop/release-management/features/storage/pass-disc…>" features introduced in oVirt 4.1 is not yet implemented for Cinder storage, for which Bug 1440230 <https://bugzilla.redhat.com/show_bug.cgi?id=1440230> - "[RFE] Allow "Pass discard from guest to underlying storage" for Cinder. " has been opened. I'm writing to people involved in the hook introduction ( https://gerrit.ovirt.org/#/c/29770/) to understand how safe is to include the hook in oVirt Node as default installed hook. I understand that the hook is going to add "discard=unmap" always, not only on Cinder. I don't know the implications of it being enabled other than supposedly fix the issue with Cinder storage. Looking at the feature page looks like this won't work with NFS storage, but other than not working, will it cause issues? I see Bug 1440230 <https://bugzilla.redhat.com/show_bug.cgi?id=1440230> is un-targeted, is there any plan to get it into oVirt 4.3? We support Cinder/Ceph since 3.6 and pass discard is supported since 4.1, not sure about what prevented the pass discard to be implemented for Cinder as well in 4.1. Can someone elaborate? Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

2 1

discussing the future of the upgrade suite in ost
by Dafna Ron 11 Oct '18

11 Oct '18

Hi All, I was reviewing the upgrade suites in ost and there are some issues that I am seeing in the suite tests-scenarios which I want to discuss and decide the future of. At it current state, I think we should remove the upgrade suite or most of the post test-scenarios as it is not testing what it should. The tests currently only test engine upgrade and basic sanity after the upgrade. This is problematic in a few ways: 1. upgrade should test the upgrade of rhv and not just a clean engine upgrade (i.e host, storage, vm). 2. as we have limited resources I do not think that the upgrade suite should be longer then the basic suite (and as we are currently running the basic suite after the upgrade it is longer) That brings me to question what should be essential to test in upgrade in the CI? I would also need someone in dev to volunteer and take ownership of the testing scenarios for upgrade - is there anyone that can help? Thanks, Dafna

4 4

Fwd: VDSM API schema inconsistencies
by Nir Soffer 11 Oct '18

11 Oct '18

Adding devel. ---------- Forwarded message --------- From: Nir Soffer <nsoffer(a)redhat.com> Date: Wed, 10 Oct 2018, 11:07 Subject: Re: VDSM API schema inconsistencies To: Piotr Kliczewski <pkliczew(a)redhat.com> Cc: Dan Kenigsberg <danken(a)redhat.com>, Edward Haas <ehaas(a)redhat.com>, Milan Zamazal <mzamazal(a)redhat.com>, Tomasz Baranski <tbaransk(a)redhat.com>, Francesco Romani <fromani(a)redhat.com>, Irit Goihman <igoihman(a)redhat.com>, Marcin Sobczyk <msobczyk(a)redhat.com> On Wed, 10 Oct 2018, 10:21 Piotr Kliczewski, <pkliczew(a)redhat.com> wrote: > +Nir > > On Wed, Oct 10, 2018 at 8:39 AM Marcin Sobczyk <msobczyk(a)redhat.com> > wrote: > >> Hi, >> I would love to get some feedback from you about it on the VDSM call >> today so if you have a moment, please take a look. >> Marcin >> >> ---------- Forwarded message --------- >> From: Marcin Sobczyk <msobczyk(a)redhat.com> >> Date: Mon, Oct 8, 2018 at 2:40 PM >> Subject: VDSM API schema inconsistencies >> To: devel <devel(a)ovirt.org> >> >> >> Hi, >> >> when I was working on BZ#1624306 it turned out, that even if I'd fix the >> help-printing code in vdsm-client, there's still a lot of inconsistencies >> in API's schema files. >> >> After some investigation, I found that there's a code for reporting >> schema inconsistencies, but it's turned off because it bloats the logs. >> > Right, an it should remain like this. In runtime we never want these warnings. There's also a "strict" mode that raises an exception each time an >> inconsistency is found, but it's also off because there's so many of them. >> > Same. Both are debugging aids for developers, to make it easy to check the schema. > I think that no one wants to maintain both: the actual code and schema >> files. >> > This is not a big issue. We rarely add or change APIs. But it is nice if we don't need to manualy make the schema correct. > My idea would be to make the schema derived from the code at build time as >> a long-term effort. >> > This cannot work, since clients depend on the schema, it should not change if when someone makes uintended change in the code. It should work in the opposite way, you change the schema, and generate new code frome schema. Threre are existing tools like grpc and thrift that work in this way. For long term we should drop our jsonrpc/stomp stack and move to grpc. For short term we can just fix the schema to reflect actual engine interaction. when engine and schema do not match, engine is usualy right. For responses, if engine can handle the response the code is right. Please do not make RPC code more complex and inefficient for improving schema issues detection. I would rather remove this code instead. Before we can do that though, we need to address the inconsistencies first. >> >> >> https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v… >> >> This is a series of patches that helps fixing schema issues. What it >> does, is it adds a bunch of information from stack to vastly ease the >> process of fixing them. The logging level is also changed from 'WARNING' to >> 'DEBUG'. Here's an example of a logged entry: >> >> Host.setKsmTune >> With message: Required property pages_to_scan is not provided when >> calling Host.setKsmTune >> With backtrace: [ >> [ >> "_verify_object_type", >> { >> "call_arg_keys":[ >> "merge_across_nodes", >> "run" >> ], >> "schema_type_name":"KsmTuneParams" >> } >> ], >> [ >> "_verify_complex_type", >> { >> "schema_type_type":"object" >> } >> ] >> ] >> >> To make it work, a patch for OST's 'basic-master-suite' is on the way >> that switches 'schema.inconsistency' logger's logging level do 'DEBUG'. >> That way, we can find all reported errors in 'vdsm-schema-error.log' files. >> >> An initial report that groups reported errors by namespaces/methods has >> also been made. Please note, that an implementation that completely avoids >> error duplicates is really hard and IMHO not worth the effort. You can find >> the results here: >> >> - Host: https://pastebin.com/YM2XnvTV >> - Image: https://pastebin.com/GRc1yErL >> - LVMVolumeGroup: https://pastebin.com/R1276gTu >> - SDM: https://pastebin.com/P3tfYEDD >> - StorageDomain: https://pastebin.com/Q0DxKgF5 >> - StoragePool: https://pastebin.com/VXFWpfRC >> - VM: https://pastebin.com/tDC60c29 >> - Volume: https://pastebin.com/TYkr9Zsd >> - |jobs|: https://pastebin.com/jeXpYyz9 >> - |virt|: https://pastebin.com/nRREuEub >> >> File a bug per vertical (infra, storage, virt) for these issues. Since we don't know about real user issues with these apis this must be incorrect schema. Nir

2 2

[VDSM] Do not use commands.execCmd(cmd, sync=False) or AsyncProcessOperation
by Nir Soffer 10 Oct '18

10 Oct '18

I just found that this patch was merged last month: https://gerrit.ovirt.org/c/94269/ Adding another use of commands.execCmd(cmd, sync=False) and AsyncProcessOperation. These APIs are deprecated and will be removed soon, please do merge any code using them. Also running commands anachronistically with a timeout is a bad idea in general. If the command is stuck on storage, we will created huge amount of commands. We have the same bad pattern in storage (iscsi/fcp rescan), it should be replaced by running command synchronically (sync=False) in a dedicated thread, and never running more then one command if the command get stuck. Marcin is working on the new improved infrastructure for running commands, based on https://gerrit.ovirt.org/c/83923. Nir

1 0

[ OST Failure Report ] [ oVirt master (vdsm) ] [ 09-10-2018 ] [ 005_network_by_label ]
by Daniel Belenky 10 Oct '18

10 Oct '18

Hi, The following patch is suspected to be failing OST: https://gerrit.ovirt.org/#/c/94754/2 Error snippet from vdsm log: 2018-10-09 08:51:50,799-0400 ERROR (Thread-7) [root] Shutdown by QEMU Guest Agent failed (vm:5269) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5260, in qemuGuestAgentShutdown self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT) File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 100, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2482, in shutdownFlags if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed', dom=self) libvirtError: Guest agent is not responding: QEMU guest agent is not connected -- DANIEL BELENKY

2 1

BUG - Cannot install Host with empty password.
by Shawn Weeks 05 Oct '18

05 Oct '18

Is there a current open bug for https://bugzilla.redhat.com/show_bug.cgi?id=1057575. It's still happening in the current release but it should have been fixed back in 2016. Guide me fails with this error but add host works fine. Thanks Shawn

1 0

Adding Fedora 28 host fail with "NotImplementedError: Packager install not implemented"
by Nir Soffer 04 Oct '18

04 Oct '18

Trying to add Fedora 28 host to engine master, host installation fails immediately with: 2018-10-02 20:34:45,440+0300 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE internal_packages METHOD otopi.plugins.ovirt_host_deploy.vd sm.vdsmid.Plugin._packages (None) 2018-10-02 20:34:45,443+0300 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/tmp/ovirt-qh2D5sbRmG/pythonlib/otopi/context.py", line 133, in _executeMethod method['method']() File "/tmp/ovirt-qh2D5sbRmG/otopi-plugins/ovirt-host-deploy/vdsm/vdsmid.py", line 84, in _packages self.packager.install(('dmidecode',)) File "/tmp/ovirt-qh2D5sbRmG/pythonlib/otopi/packager.py", line 102, in install raise NotImplementedError(_('Packager install not implemented')) NotImplementedError: Packager install not implemented 2018-10-02 20:34:45,444+0300 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Environment packages setup': Packager install not implemented engine version: 4.3.0_master (efabde5a36cbf85b43a60ead37e42943c35c2741) Is this a known issue? any workaround? Nir

5 8

random failures on test 004_basic_sanity.check_snapshot_with_memory
by Dafna Ron 04 Oct '18

04 Oct '18

Hi, I have been noticing random failures for test 004_basic_sanity.check_snapshot_with_memory The failure is not connected directly to any of the failed changes and its either a problem with the test or a problem in vdsm which is causing the failure of this test randomly. the error we are getting is: Fault reason is "Operation Failed". Fault detail is "[Cannot run VM. Low disk space on Storage Domain iscsi.]". HTTP response code is 409. I think that its related the sparsify failure we have seen in the past [1] but it has been happening more often now. Tal, can someone in your team review this again? I think that if this is not resolved soon I will skip the test so that it does not fail changes for no reason. You can see failed build here: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3277/ You can see the logs for the failed test here: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3277/artifact/b… [1] https://ovirt-jira.atlassian.net/browse/OVIRT-2024 Thanks, Dafna

1 0

vdsm has been tagged (v4.20.42)
by Milan Zamazal 03 Oct '18

03 Oct '18

Vdsm 4.20.42 for oVirt 4.2.7 rc2

1 0

Re: Issue with vdsm-hook-vmfex-dev = 4.20.40-11.git6d99cc8.el7 shipping on u/s 4.2
by Eyal Edri 03 Oct '18

03 Oct '18

Adding devel and infra as well. On Wed, Oct 3, 2018 at 3:10 PM Michael Burman <mburman(a)redhat.com> wrote: > Hi > > I think we have an issue with vdsm-hook-vmfex-dev on 4.2 u/s > > When i try to update i get this Dependency Resolution > > Error: Package: vdsm-4.20.40-11.git6d99cc8.el7.x86_64 (ovirt-4.2-snapshot) > Requires: vdsm-hook-vmfex-dev = 4.20.40-11.git6d99cc8.el7 > Installed: vdsm-hook-vmfex-dev-4.20.40-10.giteffb1ef.el7.noarch > (@ovirt-4.2-snapshot) > vdsm-hook-vmfex-dev = 4.20.40-10.giteffb1ef.el7 > Available: vdsm-hook-vmfex-dev-4.20.23-1.el7.noarch > (ovirt-4.2-centos-ovirt42) > vdsm-hook-vmfex-dev = 4.20.23-1.el7 > Available: vdsm-hook-vmfex-dev-4.20.39.1-1.el7.noarch > (ovirt-4.2-centos-ovirt42) > vdsm-hook-vmfex-dev = 4.20.39.1-1.el7 > Error: Package: vdsm-hook-vmfex-dev-4.20.40-10.giteffb1ef.el7.noarch > (@ovirt-4.2-snapshot) > Requires: vdsm = 4.20.40-10.giteffb1ef.el7 > Removing: vdsm-4.20.40-10.giteffb1ef.el7.x86_64 > (@ovirt-4.2-snapshot) > vdsm = 4.20.40-10.giteffb1ef.el7 > Updated By: vdsm-4.20.40-11.git6d99cc8.el7.x86_64 > (ovirt-4.2-snapshot) > vdsm = 4.20.40-11.git6d99cc8.el7 > Available: vdsm-4.20.23-1.el7.x86_64 (ovirt-4.2-centos-ovirt42) > vdsm = 4.20.23-1.el7 > Available: vdsm-4.20.39.1-1.el7.x86_64 > (ovirt-4.2-centos-ovirt42) > vdsm = 4.20.39.1-1.el7 > > > https://resources.ovirt.org/pub/ovirt-4.2-snapshot/rpm/el7Server/noarch/ > > Is missing the correct version and this is the problem > > Thanks, > -- > > Michael Burman > > Senior Quality engineer - rhv network - redhat israel > > Red Hat > > <https://www.redhat.com> > > mburman(a)redhat.com M: 0545355725 IM: mburman > <https://red.ht/sig> > -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

3 3

[ENGINE] make install-dev fails, trying to install outside of ENGINE_PREFIX
by Nir Soffer 03 Oct '18

03 Oct '18

Trying to make install-dev with engine master: $ git clean -dxf $ git log | head -1 commit efabde5a36cbf85b43a60ead37e42943c35c2741 The build failes, trying to install stuff out of ENGINE_PREFIX: $ make install-dev ENGINE_PREFIX=/home/nsoffer/ovirt-engine ... make copy-recursive SOURCEDIR=packaging/sys-etc TARGETDIR="/usr/local/etc"... make[2]: Entering directory `/home/nsoffer/src/ovirt-engine' ( cd "packaging/sys-etc" && find . -type d -printf '%P\n' ) | while read d; do \ install -d -m 755 "/usr/local/etc/${d}"; \ done install: cannot change permissions of ‘/usr/local/etc/logrotate.d’: No such file or directory Is this know issue? any workaround? Thanks, Nir

1 1

increasingly common OST failure: Cannot setup Networks. Another Setup Networks or Host Refresh process in progress on the host. Please try later.
by Dan Kenigsberg 02 Oct '18

02 Oct '18

FYI, Ales is working on retrying setupNetwork in case there is an async getCapabilities going on the host. https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… However, the real bug is partially hidden by Lago complaining about ExtractPathNoPathError: scp: /root/fluentd: No such file or directory What is it? Is it already tracked by someone?

4 4

ovirt-engine has been tagged (ovirt-engine-4.2.7.2)
by Piotr Kliczewski 02 Oct '18

02 Oct '18

1 0

vdsm has been tagged (v4.20.41)
by Milan Zamazal 02 Oct '18

02 Oct '18

Vdsm 4.20.41 for oVirt 4.2.7 rc2

1 0

Help understanding vdsHeartbeatInSeconds relation to Heartbeat exceeded
by Germano Veit Michel 02 Oct '18

02 Oct '18

Hi, I've been trying to understand why we see some heartbeat exceeded messages with a last response a very short time ago, while the vdsHeartbeatInSeconds option would allow for much more before triggering the disconnect. The vdc_option vdsHeartbeatInSeconds is set to 30 by default. It is used here in the engine, the propagates to vdsm-jsonrpc-java int heartbeat = Config.<Integer> getValue(ConfigValues.vdsHeartbeatInSeconds) * 1000; TransportFactory.createVdsServer() -> JsonRpcUtils.createStompClient() -> StompClientPolicy ClientPolicy -> createClient() -> getJsonClient() -> setClientPolicy() -> setRetryPolicy() So I understand ClientPolicy.incomingHearbeat = vdsHeartbeatInSeconds*1000 = 30000ms If this is the case, why do we see messages such as this, if isIncomingHeartbeatExceeded() shouldn't return True in case the last heartbeat was less than 30000ms ago? 2018-09-17 10:46:49,891+03 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Heartbeat exceeded for host '192.168.7.235', last response arrived 1702 ms ago. if (!this.isInInit() && this.policy.isIncomingHeartbeat() && this.isIncomingHeartbeatExceeded()) { String msg = String.format("Heartbeat exceeded for host '%s', last response arrived %s ms ago.", getHostname(), getHeartbeatTime()); log.error(msg); this.disconnect(msg); } private long getHeartbeatTime() { return System.currentTimeMillis() - this.lastIncomingHeartbeat; } private boolean isIncomingHeartbeatExceeded() { return this.lastIncomingHeartbeat + this.policy.getIncomingHeartbeat() < System.currentTimeMillis(); } public ClientPolicy(int retryTimeOut, int retryNumber, int incomingHeartbeat, int outgoingHeartbeat, List<Class<? extends Exception>> retryableExceptions) { this.retryNumber = retryNumber; this.retryTimeOut = retryTimeOut; setIncomingHeartbeat(incomingHeartbeat); setOutgoingHeartbeat(outgoingHeartbeat); this.exceptions = Collections.unmodifiableList(retryableExceptions); } I used byteman to print the value stored in policy.incomingHeartbeat and it is: If vdsHeartbeatInSeconds = 45 2018-09-27 15:17:13,673+10 INFO [stdout] (SSL Stomp Reactor) policy.incomingHeartbeat: 33750 If vdsHeartbeatInSeconds = 30 (default) 2018-09-27 15:21:51,099+10 INFO [stdout] (SSL Stomp Reactor) policy.incomingHeartbeat: 22500 I was expecting 45000 and 30000. But even with 33750 and 22500, I dont understand why we see "Heartbeat exceeded" and disconnection if the last heartbeat arrived just 1700ms ago. I'm clearly missing something. Could someone please put some light on what is the missing piece? Thanks, Germano

1 1

Fwd: Orphaning some Java packages
by Sandro Bonazzola 01 Oct '18

01 Oct '18

FYI, some of the packages going to be orphaned are used by ovirt-engine. Please check if you can help maintaining them. ---------- Forwarded message --------- From: Mikolaj Izdebski <mizdebsk(a)redhat.com> Date: lun 24 set 2018 alle ore 19:11 Subject: Orphaning some Java packages To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org > TL;DR I am planning to orphan Java packages listed below soon after Fedora 29 GA. Let me know if you want to adopt any of them. I'm in the process of transitioning maintenance of all software to modules only. The reason is that module maintenance is much easier compared to maintenance of non-modular, "ursine" packages. Starting from Fedora 29 modules are first-class citizens, so I am finally able to orphan ursine packages that are already available in modules. Ideally these packages should be retired instead of orphaning them, but these packages are build-required by a lot of other things. Unfortunately as of today modules can't be used as build-requires of ursine packages and I'm not aware of any plans to change that. Therefore I will let interested parties take maintenance of orphaned packages, or else let release engineering figure out how to retire them without breaking the whole distro. I decided to start with the following subset of ursine packages for which I am listed as PoC. Until Fedora 29 GA I will be providing all updates and fixes to these packages in all active +*release branches. After Fedora 29 GA I will orphan these packages, but I will keep providing important bugfixes for Fedora 27 and Fedora 28. After Fedora 28 EOL I will not maintain these packages in release (non-arbitrary) branches at all - I will maintain only corresponding modules. If you want to adopt any of these packages, please let me know and I will happily transfer them to you. Packages orphan: ant ant-contrib aopalliance apache-commons-beanutils apache-commons-collections apache-commons-compress apache-commons-io apache-commons-jxpath apache-commons-lang apache-commons-lang3 apache-commons-logging apache-commons-net apache-ivy apache-parent apache-resource-bundles aqute-bnd atinject bcel beust-jcommander bsf bsh byaccj cal10n easymock exec-maven-plugin felix-osgi-core felix-utils geronimo-jms geronimo-jpa geronimo-parent-poms glassfish-jsp-api google-guice guava20 hawtjni httpcomponents-client httpcomponents-core httpcomponents-project jakarta-commons-httpclient jansi jansi-native javacc javacc-maven-plugin javamail javapackages-tools javassist jaxen jdepend jdependency jflex jsoup junit jvnet-parent maven maven-antrun-plugin maven-archiver maven-artifact-resolver maven-artifact-transfer maven-assembly-plugin maven-clean-plugin maven-compiler-plugin maven-dependency-analyzer maven-dependency-plugin maven-dependency-tree maven-doxia maven-doxia-sitetools maven-enforcer maven-file-management maven-filtering maven-invoker maven-jar-plugin maven-parent maven-plugin-build-helper maven-plugin-bundle maven-plugins-pom maven-plugin-testing maven-plugin-tools maven-reporting-api maven-reporting-impl maven-resolver maven-script-interpreter maven-shade-plugin maven-shared-incremental maven-shared-io maven-shared-utils maven-source-plugin maven-surefire maven-verifier maven-wagon modello mojo-parent munge-maven-plugin objectweb-pom osgi-compendium osgi-core os-maven-plugin plexus-ant-factory plexus-archiver plexus-bsh-factory plexus-classworlds plexus-cli plexus-compiler plexus-component-factories-pom plexus-components-pom plexus-containers plexus-i18n plexus-interactivity plexus-interpolation plexus-io plexus-languages plexus-resources plexus-utils plexus-velocity qdox regexp sisu sisu-mojos slf4j sonatype-oss-parent sonatype-plugins-parent velocity xalan-j2 xbean xmvn xz-java Maintainers by package: ant akurtakov jcapik kdaniel mizdebsk msrb ant-contrib davidcl mizdebsk aopalliance mizdebsk apache-commons-beanutils fnasser mizdebsk spike apache-commons-collections jcapik mizdebsk apache-commons-compress mizdebsk spike apache-commons-io mizdebsk spike apache-commons-jxpath fnasser mizdebsk spike apache-commons-lang mizdebsk spike apache-commons-lang3 mizdebsk apache-commons-logging kdaniel mizdebsk spike apache-commons-net mizdebsk spike apache-ivy mizdebsk apache-parent mizdebsk apache-resource-bundles mizdebsk aqute-bnd jcapik mizdebsk atinject kdaniel mizdebsk bcel mizdebsk beust-jcommander jcapik mizdebsk bsf choeger mizdebsk bsh mizdebsk byaccj akurtakov dbhole mizdebsk cal10n mizdebsk easymock akurtakov ctubbsii dbhole fnasser mizdebsk exec-maven-plugin mizdebsk felix-osgi-core jcapik mizdebsk felix-utils jcapik mizdebsk geronimo-jms mizdebsk geronimo-jpa lef mizdebsk geronimo-parent-poms mizdebsk glassfish-jsp-api kdaniel mizdebsk google-guice mizdebsk guava20 mizdebsk hawtjni gil goldmann mizdebsk httpcomponents-client jerboaa kdaniel mizdebsk httpcomponents-core jerboaa kdaniel mizdebsk httpcomponents-project mizdebsk jakarta-commons-httpclient dbhole ke4qqq mizdebsk jansi goldmann mizdebsk jansi-native goldmann mizdebsk javacc jcapik mizdebsk javacc-maven-plugin jcapik mizdebsk javamail mizdebsk javapackages-tools mizdebsk msrb javassist john5342 mizdebsk jaxen mizdebsk jdepend goldmann jcapik mizdebsk jdependency mizdebsk jflex jcapik mizdebsk jsoup jcapik mizdebsk junit kdaniel mizdebsk jvnet-parent mizdebsk maven akurtakov jamielinux mizdebsk msrb maven-antrun-plugin mizdebsk maven-archiver akurtakov mizdebsk maven-artifact-resolver mizdebsk maven-artifact-transfer mizdebsk maven-assembly-plugin gil huwang jcapik mizdebsk maven-clean-plugin mizdebsk maven-compiler-plugin mizdebsk maven-dependency-analyzer mizdebsk maven-dependency-plugin mizdebsk maven-dependency-tree mizdebsk maven-doxia akurtakov mef mizdebsk maven-doxia-sitetools akurtakov dbhole mizdebsk maven-enforcer jcapik mizdebsk maven-file-management mizdebsk maven-filtering mizdebsk maven-invoker mizdebsk maven-jar-plugin mizdebsk maven-parent mizdebsk maven-plugin-build-helper mizdebsk maven-plugin-bundle jcapik mizdebsk maven-plugin-testing jcapik mizdebsk yyang maven-plugin-tools jcapik mizdebsk yyang maven-plugins-pom mizdebsk maven-reporting-api mizdebsk maven-reporting-impl mizdebsk maven-resolver mizdebsk maven-script-interpreter mizdebsk maven-shade-plugin jcapik mizdebsk pingou maven-shared-incremental mizdebsk maven-shared-io mizdebsk maven-shared-utils mizdebsk maven-source-plugin mizdebsk maven-surefire akurtakov jcapik mizdebsk maven-verifier mizdebsk maven-wagon akurtakov dbhole fnasser jcapik mizdebsk yyang modello fnasser mizdebsk yyang mojo-parent mizdebsk munge-maven-plugin mizdebsk objectweb-pom mizdebsk os-maven-plugin ctubbsii mizdebsk osgi-compendium mizdebsk osgi-core mizdebsk plexus-ant-factory mizdebsk plexus-archiver dbhole jcapik mizdebsk plexus-bsh-factory mizdebsk plexus-classworlds dbhole fnasser mizdebsk plexus-cli mizdebsk plexus-compiler mizdebsk plexus-component-factories-pom mizdebsk plexus-components-pom mizdebsk plexus-containers dbhole fnasser mizdebsk yyang plexus-i18n dbhole jcapik mizdebsk plexus-interactivity mizdebsk plexus-interpolation gil jcapik mizdebsk plexus-io jcapik mizdebsk plexus-languages mizdebsk plexus-resources jcapik mizdebsk plexus-utils fnasser mizdebsk plexus-velocity jcapik mizdebsk qdox mizdebsk regexp mizdebsk sisu mizdebsk sisu-mojos mizdebsk slf4j mizdebsk sonatype-oss-parent mizdebsk sonatype-plugins-parent mizdebsk velocity devrim mizdebsk xalan-j2 kdaniel mizdebsk xbean kdaniel mizdebsk xmvn mizdebsk msrb xz-java kdaniel mizdebsk Packages by maintainer: akurtakov ant byaccj easymock maven maven-archiver maven-doxia maven-doxia-sitetools maven-surefire maven-wagon choeger bsf ctubbsii easymock os-maven-plugin davidcl ant-contrib dbhole byaccj easymock jakarta-commons-httpclient maven-doxia-sitetools maven-wagon plexus-archiver plexus-classworlds plexus-containers plexus-i18n devrim velocity fnasser apache-commons-beanutils apache-commons-jxpath easymock maven-wagon modello plexus-classworlds plexus-containers plexus-utils gil hawtjni maven-assembly-plugin plexus-interpolation goldmann hawtjni jansi jansi-native jdepend huwang maven-assembly-plugin jamielinux maven jcapik ant apache-commons-collections aqute-bnd beust-jcommander felix-osgi-core felix-utils javacc javacc-maven-plugin jdepend jflex jsoup maven-assembly-plugin maven-enforcer maven-plugin-bundle maven-plugin-testing maven-plugin-tools maven-shade-plugin maven-surefire maven-wagon plexus-archiver plexus-i18n plexus-interpolation plexus-io plexus-resources plexus-velocity jerboaa httpcomponents-client httpcomponents-core john5342 javassist kdaniel ant apache-commons-logging atinject glassfish-jsp-api httpcomponents-client httpcomponents-core junit xalan-j2 xbean xz-java ke4qqq jakarta-commons-httpclient lef geronimo-jpa mef maven-doxia mizdebsk ant ant-contrib aopalliance apache-commons-beanutils apache-commons-collections apache-commons-compress apache-commons-io apache-commons-jxpath apache-commons-lang apache-commons-lang3 apache-commons-logging apache-commons-net apache-ivy apache-parent apache-resource-bundles aqute-bnd atinject bcel beust-jcommander bsf bsh byaccj cal10n easymock exec-maven-plugin felix-osgi-core felix-utils geronimo-jms geronimo-jpa geronimo-parent-poms glassfish-jsp-api google-guice guava20 hawtjni httpcomponents-client httpcomponents-core httpcomponents-project jakarta-commons-httpclient jansi jansi-native javacc javacc-maven-plugin javamail javapackages-tools javassist jaxen jdepend jdependency jflex jsoup junit jvnet-parent maven maven-antrun-plugin maven-archiver maven-artifact-resolver maven-artifact-transfer maven-assembly-plugin maven-clean-plugin maven-compiler-plugin maven-dependency-analyzer maven-dependency-plugin maven-dependency-tree maven-doxia maven-doxia-sitetools maven-enforcer maven-file-management maven-filtering maven-invoker maven-jar-plugin maven-parent maven-plugin-build-helper maven-plugin-bundle maven-plugin-testing maven-plugin-tools maven-plugins-pom maven-reporting-api maven-reporting-impl maven-resolver maven-script-interpreter maven-shade-plugin maven-shared-incremental maven-shared-io maven-shared-utils maven-source-plugin maven-surefire maven-verifier maven-wagon modello mojo-parent munge-maven-plugin objectweb-pom os-maven-plugin osgi-compendium osgi-core plexus-ant-factory plexus-archiver plexus-bsh-factory plexus-classworlds plexus-cli plexus-compiler plexus-component-factories-pom plexus-components-pom plexus-containers plexus-i18n plexus-interactivity plexus-interpolation plexus-io plexus-languages plexus-resources plexus-utils plexus-velocity qdox regexp sisu sisu-mojos slf4j sonatype-oss-parent sonatype-plugins-parent velocity xalan-j2 xbean xmvn xz-java msrb ant javapackages-tools maven xmvn pingou maven-shade-plugin spike apache-commons-beanutils apache-commons-compress apache-commons-io apache-commons-jxpath apache-commons-lang apache-commons-logging apache-commons-net yyang maven-plugin-testing maven-plugin-tools maven-wagon modello plexus-containers -- Mikolaj Izdebski Senior Software Engineer, Red Hat IRC: mizdebsk _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

1 0

/root/fluentd no longer exists
by Anton Marchukov 01 Oct '18

01 Oct '18

Hello Shirly, All. We used to collect fluentd artifacts in OST from /root/fluentd, but starting from around mid night today Fri Aug 31 (or maybe late evening Thu Aug 30) the tests started to fail to locate /root/fluentd. We merged a patch to disable its collection [1] so we can let other tests run, but we need to find what happened and restore fluentd collection. I open a JIRA issue [2] on this. Do you have any idea? Thanks. [1] https://gerrit.ovirt.org/#/c/94067/ [2] https://ovirt-jira.atlassian.net/browse/OVIRT-2464 -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

4 9

new dependency for vdsm 4.2
by Marcin Sobczyk 01 Oct '18

01 Oct '18

Hi, "python-enum34" has been added as a new dependency for vdsm-4.2 after merging https://gerrit.ovirt.org/#/q/topic:vdsm-api-schema-pickle+(status:open+OR+s… . Regards, Marcin

2 2

[ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 01-10-2018 ] [ 002_bootstrap.download_engine_certs ]
by Dafna Ron 01 Oct '18

01 Oct '18

Hi, We are failing project ovirt-engine on master branch. The issue seems to be related to the reported patch Dominik, can you please take a look? https://gerrit.ovirt.org/#/c/94582/ - packaging: Add MAC Pool range only if MAC Pool exists full logs can be found here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10442/artifa… Error: >>>> 2018-09-29 12:37:58,209-04 INFO [org.ovirt.engine.core.bll.network.macpool.MacPoolUsingRanges] (ServerService Thread Pool -- 43) [] Initializing MacPoolUsingRanges:{id='58ca604b-017d-0374-0220-00000000014e'} 2018-09-29 12:37:58,220-04 ERROR [org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster] (ServerService Thread Pool -- 43) [] Error initializing: EngineException: MAC_POOL_INITIALIZATION_FAILED (Failed with error MAC_POOL_INITIALIZATION_FAILED and code 5010) 2018-09-29 12:37:58,237-04 ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool -- 43) [] Error during initialization: javax.ejb.EJBException: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:362) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:144) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:72) [weld-ejb-3.0.4.Final.jar:3.0.4.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.ejb3.component.singleton.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:106) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) 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.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) at org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster$$$view6.logFreeMacs(Unknown Source) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_181] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_181] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_181] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_181] at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:411) [weld-core-impl-3.0.4.Final.jar:3.0.4.Final] at org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:134) [weld-ejb-3.0.4.Final.jar:3.0.4.Final] at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) [weld-core-impl-3.0.4.Final.jar:3.0.4.Final] at org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) [weld-ejb-3.0.4.Final.jar:3.0.4.Final] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) [weld-core-impl-3.0.4.Final.jar:3.0.4.Final] at org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster$Proxy$_$$_Weld$EnterpriseProxy$.logFreeMacs(Unknown Source) [bll.jar:] at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:253) [bll.jar:] at org.ovirt.engine.core.bll.Backend.create(Backend.java:179) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_181] : at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_181] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_181] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_181] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:78) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:125) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:111) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) [weld-ejb-3.0.4.Final.jar:3.0.4.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:53) [wildfly-weld-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) [wildfly-weld-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.ComponentInstantiatorInterceptor.processInvocation(ComponentInstantiatorInterceptor.java:74) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.interceptors.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:105) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:216) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:418) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:70) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) [wildfly-weld-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:127) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_181] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_181] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_181] at org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) : at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:127) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:48) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:237) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] ... 103 more Caused by: javax.ejb.EJBException: org.ovirt.engine.core.common.errors.EngineException: EngineException: MAC_POOL_INITIALIZATION_FAILED (Failed with error MAC_POOL_INITIALIZATION_FAILED and code 5010) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:380) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) [wildfly-weld-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) ... 109 more Caused by: org.ovirt.engine.core.common.errors.EngineException: EngineException: MAC_POOL_INITIALIZATION_FAILED (Failed with error MAC_POOL_INITIALIZATION_FAILED and code 5010) at org.ovirt.engine.core.bll.network.macpool.MacPoolUsingRanges.createMacsStorage(MacPoolUsingRanges.java:86) [bll.jar:] at org.ovirt.engine.core.bll.network.macpool.MacPoolUsingRanges.initialize(MacPoolUsingRanges.java:45) [bll.jar:] at org.ovirt.engine.core.bll.network.macpool.MacPoolFactory.createMacPool(MacPoolFactory.java:24) [bll.jar:] at org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster.createPoolInternal(MacPoolPerCluster.java:147) [bll.jar:] at org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster.initialize(MacPoolPerCluster.java:63) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_181] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_181] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_181] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_181] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:122) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:111) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:72) [weld-ejb-3.0.4.Final.jar:3.0.4.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:53) [wildfly-weld-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) [wildfly-weld-13.0.0.Final.jar:13.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.interceptors.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:105) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:237) [wildfly-ejb3-13.0.0.Final.jar:13.0.0.Final] ... 122 more 2018-09-29 12:38:20,061-04 DEBUG [org.ovirt.engine.core.utils.servlet.LocaleFilter] (default task-1) [] Incoming locale 'en-US'. Filter determined locale to be 'en-US' 2018-09-29 12:38:20,090-04 DEBUG [org.ovirt.engine.core.utils.servlet.LocaleFilter] (default task-1) [] Incoming locale 'en-US'. Filter determined locale to be 'en-US' 2018-09-29 12:38:20,092-04 DEBUG [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-1) [] Exponent is 65537 (010001). 2018-09-29 12:38:20,093-04 DEBUG [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-1) [] Modulus is 26698611349489366587526856180583725653991729505965533703437849591864173212373800632077468566272232268009727951221325650736180402095270744479922503726199150458580804280850490476781273803476337202574331221849445435803681491738287639596211779806993602290234479517449922393140563915459391275104665984414876289985509308168879855274164947583935056664325395920398783112858802135360088161644622992238367697860828891879961652134900396077428122589742961659240896459689353656993792940130794763441318408623199091823007155684932095651446362204139436538693552007492420615692487714029971117240812932518523209400090956655452498597861 (010001). 2018-09-29 12:38:20,093-04 DEBUG [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-1) [] Key bytes are 000000077373682d727361000000030100010000010100d37e65cc0b8ee0131a9264c0b1fd46ccf2e3725d83667322bdbb0bac040f80c736247f33476ccdc554d16e81a6df4854fdf1d596ee03160b9c639a5dbb68fd3fa08f0981b71e69a6bea5a6e901bc26ba9b334b652f82a0d8efd498b7afe3cb12dc5c464ea3300254d619c157a8b5d13b3e565b12c8161206afbda432dbb1c2ec449681f715f2f5ff3b6b8615c5a42ecb32519dc2feb6f2d4bd89213be2459edb3d9db9f7b687e45c3ef866f7581e84298e7d375830b2535e7e88556145b931c1b974dd56075d2103a90293686a679615ca4d6d99b7b2edc17b7b8bc627bb11a96ce22950043b099444b3a166866b17ac4ba71bb1e238d9d5d1af4ef95ec697e5. 2018-09-29 12:38:20,093-04 DEBUG [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-1) [] Key encoding is 'AAAAB3NzaC1yc2EAAAADAQABAAABAQDTfmXMC47gExqSZMCx/UbM8uNyXYNmcyK9uwusBA+AxzYkfzNHbM3FVNFugabfSFT98dWW7gMWC5xjml27aP0/oI8Jgbceaaa+pabpAbwmupszS2UvgqDY79SYt6/jyxLcXEZOozACVNYZwVeotdE7PlZbEsgWEgavvaQy27HC7ESWgfcV8vX/O2uGFcWkLssyUZ3C/rby1L2JITviRZ7bPZ2597aH5Fw++Gb3WB6EKY59N1gwslNefohVYUW5McG5dN1WB10hA6kCk2hqZ5YVyk1tmbey7cF7e4vGJ7sRqWziKVAEOwmURLOhZoZrF6xLpxux4jjZ1dGvTvlexpfl'. 2018-09-29 12:38:20,093-04 DEBUG [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-1) [] Key string is 'ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDTfmXMC47gExqSZMCx/UbM8uNyXYNmcyK9uwusBA+AxzYkfzNHbM3FVNFugabfSFT98dWW7gMWC5xjml27aP0/oI8Jgbceaaa+pabpAbwmupszS2UvgqDY79SYt6/jyxLcXEZOozACVNYZwVeotdE7PlZbEsgWEgavvaQy27HC7ESWgfcV8vX/O2uGFcWkLssyUZ3C/rby1L2JITviRZ7bPZ2597aH5Fw++Gb3WB6EKY59N1gwslNefohVYUW5McG5dN1WB10hA6kCk2hqZ5YVyk1tmbey7cF7e4vGJ7sRqWziKVAEOwmURLOhZoZrF6xLpxux4jjZ1dGvTvlexpfl '. >>>> Thanks. Dafna

2 1