August 2018 - Devel - oVirt List Archives

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

01 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

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

/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

ovirt.org documentation refresh
by Greg Sheremeta 27 Sep '18

27 Sep '18

Hi all, Brian Proffitt has kindly offered to refresh the documentation on ovirt.org to version 4.2 (it's currently a mix of 4.0 + whatever people have updated since.) Other than the main 'official' documentation, I noticed that there is a lot of documentation on separate sites. For example, imageio, mom, all of the OST stuff, etc. For now there are no plans for any of this extra stuff, but in the future it should probably all look the same. Can you share ovirt documentation sites that you know of? Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

5 4

Failing OST Suites
by Anton Marchukov 04 Sep '18

04 Sep '18

Hello All. This is a reminder to corresponding maintainers to check the OST suits [1], there are failing ones such as: ovirt-system-tests_ansible-suite-master ovirt-system-tests_compat-3.6-suite-master ovirt-system-tests_compat-4.0-suite-master ovirt-system-tests_compat-4.1-suite-master ovirt-system-tests_compat-4.2-suite-master ovirt-system-tests_hc-basic-suite-4.2 ovirt-system-tests_he-node-ng-suite-master If everything is not needed we might also consider disabling/deleting. Thanks. [1] https://jenkins.ovirt.org/view/oVirt%20system%20tests/

3 4

[ OST Failure Report ] [ oVirt master (ovirt-ansible-engine-setup) ] [ Aug 31 ] [ 001_upgrade_engine.test_initialize_engine ]
by Anton Marchukov 31 Aug '18

31 Aug '18

Hello All. We have a failure in OST master. The link to job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9255/ and to the output: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9255/testRepo… It seems like schema fails to apply during upgrade: File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 437, in _misc raise RuntimeError(_('Engine schema refresh failed')) RuntimeError: Engine schema refresh failed I think the patch referred by the job is not the cause as ovirt-ansible-engine-setup has only release bumps recently as I see. I will reply here if I find a probably cause. -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

2 2

ovirt-guest-agent_master_build-artifacts-fc28-x86_64 Fails to Build
by Anton Marchukov 31 Aug '18

31 Aug '18

Hello All. Looks like ovirt-guest-agent_master_build-artifacts-fc28-x86_64 nolonger works, as I see it fails to build with the following error: *10:53:41* 0009:fixme:module:find_dll_file skipping L"C:\\windows\\system32\\dbghelp.dll" because of wrong architecture*10:53:42* 004a:err:msiexec:custom_action_server Failed to create custom action server pipe: 2 than it fails to recognize that and the whole job fails on a time out: *16:41:14* Build timed out (after 360 minutes). Marking the build as failed. As a result, OST for guest-agent also fails. I tried to rerun the job and got the same problem. The failing job is at [1] and I also opened JIRA issue [2] to track it. [1] http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc28-… [2] https://ovirt-jira.atlassian.net/browse/OVIRT-2466 -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

3 2

s390x (mainframe) CI node is currently not available
by Barak Korren 30 Aug '18

30 Aug '18

Hi all, Unfortunately, the s390x build host we've been using had gone off-line a couple of days ago, and the ETA for having it back up is unknown. The implication of having the host down is that projects that build on s390x have their builds be stuck forever waiting for the s390x node to become available. Sine the s390x builds are missing, builds for other platforms, while being successful do not get passed to the change queue and as a result are not being released to the nightly repos. As a work around for the current situation, we need to disable the s390x builds. Here is a patch that does this for vdsm: https://gerrit.ovirt.org/c/93316/ For V2 projects the change should be done in the projects own repo, for example here is how we did it for the CI jobs of the 'jenkins' repo itself: https://gerrit.ovirt.org/c/93288/ -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 1

Failing Build On vdsm_master_check-patch
by Shani Leviim 29 Aug '18

29 Aug '18

Hello All, I got into the following failure during the CI build for a patch I did: 14:33:56 ====================================================================== 14:33:56 FAIL: test_sourceroute_add_remove_and_read (network.sourceroute_test.TestSourceRoute) 14:33:56 ---------------------------------------------------------------------- 14:33:56 Traceback (most recent call last): 14:33:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/tests/testValidation.py", line 193, in wrapper 14:33:56 return f(*args, **kwargs) 14:33:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/tests/network/sourceroute_test.py", line 80, in test_sourceroute_add_remove_and_read 14:33:56 self.assertEqual(2, len(routes), routes) 14:33:56 AssertionError: 2 != 0 My patch is [1] and its build is [2] [1] https://gerrit.ovirt.org/#/c/92416/ [2] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/747/ Can you please assist? Thanks! *Regards,* *Shani Leviim*

3 4

OST compatibility check failing on backup snapshot removal
by Milan Zamazal 29 Aug '18

29 Aug '18

Hi, when basic-suite-master OST is run with cluster level < 4.2, verify_backup_snapshot_removed test fails. Indeed, the snapshot removal fails, with error such as: [c784a2c3-a700-41f7-80bd-2d1e25a712c5] Failed to live merge. Top volume 15b82854-c9dd-44aa-83c9-aebe273ac6a4 is still in qemu chain [15b82854-c9dd-44aa-83c9-aebe273ac6a4, 3c21269c-e71b-4e96-977e-a9168bbba9bf] See e.g. https://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/52… Does anybody have an idea what might be wrong? Thanks, Milan

3 6

Re: Image Transfer mechanism queries/API support
by Ranjit DSouza 28 Aug '18

28 Aug '18

Hello oVirt Development team Not sure you got a chance to see this email, resending it. Thanks Ranjit From: Ranjit DSouza Sent: Monday, July 9, 2018 1:16 PM To: 'Nir Soffer' <nsoffer(a)redhat.com> Cc: devel <devel(a)ovirt.org>; DL-VTAS-ENG-NBU-EverestFalcons <DL-VTAS-ENG-NBU-EverestFalcons(a)veritas.com>; Navin Tah <Navin.Tah(a)veritas.com>; Sudhakar Paulzagade <Sudhakar.Paulzagade(a)veritas.com>; Pavan Chavva; Yaniv Lavi (Dary) <ylavi(a)redhat.com>; Nisan, Tal <tnisan(a)redhat.com>; Daniel Erez <derez(a)redhat.com> Subject: RE: [EXTERNAL] Re: [ovirt-devel] Image Transfer mechanism queries/API support Hi Nir Thanks for getting back! We have few follow up questions: 1. On the new ‘Allocated extents API’: Can you share the release timeline for 4.2.z? From the link below it seems like it will be available on 7/30/2018. https://www.ovirt.org/develop/release-management/releases/4.2.z/release-man… However, we thought we would double check on this. 2. If this will be available in 4.2.z, does It mean, we can assume it will be backported to 4.3 also? 3. When we downloaded the snapshot disk using Image Transfer API, the resulting format of the disk is “raw”. However, for upload, we must upload a qcow2 disk (to enable further snapshots). It means, we need to convert it first using qemu-img convert. Or is there a way we directly ask via API for a qcow2 instead? Portion of the response of “GET /storagedomains/{storagedomain:id}/disksnapshots” "format" : "raw", "shareable" : "false", "sparse" : "true", "status" : "ok", "snapshot" : { "id" : "4756036e-92aa-4ebb-ae4b-052a30cd5109" }, "actual_size" : "1345228800", "content_type" : "data", "propagate_errors" : "false", "provisioned_size" : "21474836480", "storage_type" : "image", "total_size" : "0", "wipe_after_delete" : "false", 4. When downloading a snapshot in chunks, Is there any recommended chunk size? For our study we used 512 KB. Checked the documentation too. 5. Regarding your ask on ‘Can you file RFE for this, explaining the use case and the current performance’. Since you do not recommend direct access to NFS storage, we will consider it only if we see significant performance degradation using http download. Also, if time permits, we may check if there is a significant performance benefit using Unix socket, over http download (via Rest API). But as it stands now, getting the allocated extents support (soon), will alleviate most of our performance concerns. Thanks Ranjit From: Nir Soffer [mailto:nsoffer@redhat.com] Sent: Tuesday, July 3, 2018 4:29 PM To: Ranjit DSouza <Ranjit.DSouza(a)veritas.com<mailto:Ranjit.DSouza@veritas.com>> Cc: devel <devel(a)ovirt.org<mailto:devel@ovirt.org>>; DL-VTAS-ENG-NBU-EverestFalcons <DL-VTAS-ENG-NBU-EverestFalcons(a)veritas.com<mailto:DL-VTAS-ENG-NBU-EverestFalcons@veritas.com>>; Navin Tah <Navin.Tah(a)veritas.com<mailto:Navin.Tah@veritas.com>>; Sudhakar Paulzagade <Sudhakar.Paulzagade(a)veritas.com<mailto:Sudhakar.Paulzagade@veritas.com>>; Pavan Chavva; Yaniv Lavi (Dary) <ylavi(a)redhat.com<mailto:ylavi@redhat.com>>; Nisan, Tal <tnisan(a)redhat.com<mailto:tnisan@redhat.com>>; Daniel Erez <derez(a)redhat.com<mailto:derez@redhat.com>> Subject: [EXTERNAL] Re: [ovirt-devel] Image Transfer mechanism queries/API support On Tue, Jul 3, 2018 at 11:32 AM Ranjit DSouza <Ranjit.DSouza(a)veritas.com<mailto:Ranjit.DSouza@veritas.com>> wrote: ... We had a conversation with Pavan Chavva for supporting RHV. He had suggested to contact you with queries related to oVirt APIs we plan to use. We have following queries: 1. While downloading a snapshot disk, can we identify allocated extents and download only those using oVirt API? We are able to download the disk using the Image Transfer API mechanism. However, this method downloads the entire disk including the non-allocated extents, which is a performance overhead. If this functionality does not exist at this point will it be available in near future? Hi Ranjit, There is no way to do this in current 4.2, but we plan to introduce in in 4.2.z. The API will be something like: GET /images/xxx-yyy/map ... [{ "start": 0, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 0}, { "start": 65536, "length": 983040, "depth": 0, "zero": true, "data": false, "offset": 65536}, { "start": 1048576, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 1048576}, { "start": 1114112, "length": 983040, "depth": 0, "zero": true, "data": false, "offset": 1114112}, ... { "start": 5465571328, "length": 22675456, "depth": 0, "zero": false, "data": true, "offset": 5465571328}, { "start": 5488246784, "length": 954138624, "depth": 0, "zero": true, "data": false, "offset": 5488246784}, { "start": 6442385408, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 6442385408}] This is basically what you get using qemu-img map. You can test play this with this using: virt-builder Fedora-27 -o /var/tmp/fedora-27.img qemu-img map -f raw --output json /var/tmp/fedora-27.img This is the first data segment: { "start": 0, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 0} This is a hole between the first data segment and the second: { "start": 65536, "length": 983040, "depth": 0, "zero": true, "data": false, "offset": 65536} This is the second data segment: { "start": 1048576, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 1048576} Based on this output, you will be able to get the allocated parts of the image using: Request: GET /image/xxx-yyy HTTP/1.1 Range: bytes=0-65535 Response: HTTP/1.1 206 Partial Content Content-Range: bytes 0-65535/6442450944 <data of first segment> Request: GET /image/xxx-yyy HTTP/1.1 Range: bytes=1048576-1114111 Response: HTTP/1.1 206 Partial Content Content-Range: bytes 1048576-1114111/6442450944 <data of second segment> And so on. If you create a sparse file on your backup media, and download and write the data segments at the correct offset, you will get the a sparse version of the image as on the server side. This will work for raw or qcow2 images on NFS >= 4.2, or for qcow2 images on block storage. For older NFS versions, or raw images on block storage, we can solve the issue by reading the entire image and detecting zeroes - which is quite expensive, so I'm not sure we will implement this, maybe it will be done later. We have experimental patch using special sparse format, that can support this use case, downloading entire image in one pass. This commit message explain the format: https://gerrit.ovirt.org/#/c/85413/12//COMMIT_MSG For more info on using random I/O APIs, see: http://ovirt.github.io/ovirt-imageio/random-io (available since 4.2.3) For example code uploading sparse images see: https://github.com/oVirt/ovirt-imageio/blob/master/examples/upload For best performance, you should run your application on a oVirt host, using unix socket to communicate with imageio. See: http://ovirt.github.io/ovirt-imageio/unix-socket (will be available in 4.2.5) All this will work only for the non-active layer in a qcow2 chain. We are working now on incremental backup which will allow the same for the active layer with a running vm. This is expected in 4.3, and we may have a tech preview at some point in 4.2.z. Incremantal backup will use the similar API, allowing detection of dirty parts of an image, so you can download only the data that was changed since the last backup. Please watch and comment on the feature page: https://ovirt.org/develop/release-management/features/storage/incremental-b… We are also considering exposing images using NBD. This will allow downloading and uploading images using qemu-img from any host. This work depends on TLS-PSK support in qemu-img and qemu-nbd. You can follow this work here: https://lists.nongnu.org/archive/html/qemu-devel/2018-06/threads.html#08491 2. Is there an alternate method to transfer a snapshot to and from RHV storage? Are there other methods such as NFS share where we can download snapshot image to and from RHV storage? We don't support direct access to storage by 3rd party. You should use imageio API. Can you file RFE for this, explaning the use case and the current performance issues you experience? Nir

4 4

vdsm has been tagged (v4.20.39)
by Milan Zamazal 28 Aug '18

28 Aug '18

Vdsm 4.20.39 for oVirt 4.2.6 rc3

1 0

new storage domain question
by Hetz Ben Hamo 27 Aug '18

27 Aug '18

Hi, I just found something very interesting. While installing latest ovirt, I've created the shared_storage on my nas1 share folder (NFS). So far, so good. However, when trying to create additional 2 new storage domains, I can only create 1 (which means the shared_storage is 1 and a new one is 2, I cannot create a 3rd storage domain, 4th etc..). When I try, it shows an error (I don't remember which error right now). Why is that? and why this strange (IMHO) shared_storage thing? in a corporate, if I want to set up a virtualized environment, the storage administrator asks me which one I want (NFS, or an iSCSI LUN), do I need one or more, and then I'm adding them as a datastore (in VMWare, for example) and on top of that I'm installing the management software (for example, vCenter). with oVirt method, it will confuse VMware admins. Thanks

2 5

ovirt-engine has been tagged (ovirt-engine-4.2.6.4)
by Tal Nisan 26 Aug '18

26 Aug '18

1 0

vdsm has been tagged (v4.20.38)
by Milan Zamazal 24 Aug '18

24 Aug '18

Vdsm 4.20.38 for oVirt 4.2.6 rc3

1 0

Fwd: [CentOS-announce] Release for CentOS Linux 7 (1804) on POWER9 (ppc64le)
by Sandro Bonazzola 22 Aug '18

22 Aug '18

FYI ---------- Forwarded message ---------- From: James O'Connor <jpoc(a)linux.vnet.ibm.com> Date: 2018-08-15 20:26 GMT+02:00 Subject: [CentOS-announce] Release for CentOS Linux 7 (1804) on POWER9 (ppc64le) To: centos-announce(a)centos.org I am pleased to announce the general availability of CentOS Linux 7 (1804) for POWER9 processors (ppc64le - powerpc 64-bit little endian). This release is derived from Red Hat Enterprise Linux 7.5 ALT. Note this release is 99% equivalent to the existing CentOS 7 Linux 7 (1804) for POWER8 processors (ppc64le - powerpc 64-bit little endian). The key difference being that kernel-4.14.0 is used for POWER9 enablement and kernel-3.10.0 is used for POWER8 enablement. You will find the CentOS 7 (1804) Power9 installation images here: http://mirror.centos.org/altarch/7.5.1804/isos/power9/ sha256sum power9: 753c5b55c9ff681c925ec7d7c5295890284f40ec981f4da35b1f36f1ecbad95a CentOS-7-Power9-Everything-1804.iso 58d9af172656db71947b5db2d0d1f577217bbc1a86eada7ca3ce7bfcf7d7d9b4 CentOS-7-Power9-NetInstall-1804.iso CentOS 7 (1804) Power9 repositories: http://mirror.centos.org/altarch/7.5.1804/os/power9/ http://mirror.centos.org/altarch/7.5.1804/updates/power9/ http://mirror.centos.org/altarch/7.5.1804/extras/power9/ A special thank you to Johnny Hughes and Pablo Greco for their assistance making this release possible. -James O’Connor _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce -- 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

planned Jenkins restart
by Evgheni Dereveanchin 22 Aug '18

22 Aug '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

Is using CompensationContext in child commands broken?
by Andrej Krejcir 21 Aug '18

21 Aug '18

Hi, I'm changing UpdateClusterCommand to be non-transactive, and it would use CompensationContext for reverting DB operations. Reading through CommandBase code, I noticed the following flow seems to be broken: 1. A command without transaction is executed. 2. It executes a child command, with the compensation context of the current command. So that the result of the child command can be reverted if the parent fails. 3. Once the child command successfully finishes, it removes all entity snapshots from the DB (it calls CommandContext::cleanupCompensationDataAfterSuccessfulCommand), even if the snapshots were made by the parent command. See code at [1] and [2]. 4. The parent command then fails for some other reason, but its compensation context is empty, so the DB operations are not reverted correctly. Am I missing something or is this flow broken? Thanks, Andrej [1] - https://github.com/oVirt/ovirt-engine/blob/31fbb4cb48c7208e6b37c5c0e2756059… [2] - https://github.com/oVirt/ovirt-engine/blob/31fbb4cb48c7208e6b37c5c0e2756059…

3 2

Fwd: Fedora 30 System-Wide Change proposal: Mass Python 2 Package Removal
by Sandro Bonazzola 21 Aug '18

21 Aug '18

FYI ---------- Forwarded message ---------- From: Ben Cotton <bcotton(a)redhat.com> Date: 2018-08-20 22:41 GMT+02:00 Subject: Fedora 30 System-Wide Change proposal: Mass Python 2 Package Removal To: devel(a)lists.fedoraproject.org, devel-announce(a)lists.fedoraproject.org https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal == Summary == (Sub-)packages only providing python2 importable modules without additional functionality will be removed from Fedora unless some other package(s) depends on them. Python 2 will be deprecated in Fedora. Packagers can mark any other Python 2 packages as deprecated as well. == Owner == * Miro Hrončok (Churchyard) * Petr Viktorin (Pviktori) * Charalampos Stratakis (Cstratak) * Zbigniew Jędrzejewski-Szmek (Zbyszek) * Igor Gantenko (Ignatenkobrain) * Neal Gompa (Ngompa) == Detailed Description == Python 2 reaches End of Life on 2020-01-01. Its current maintainers would like to orphan it before that date, and so far no one else has stepped up to maintain Python 2 (with the full ecosystem) past 2020. Since thousands of packages still depend on python2, we need a more careful approach than normal orphaning. Some of those packages are abandoned and/or the Python 2 version is unnecessary. Others are useful and just need more time to port to Python 3. Hence we set up criteria for python2 packages that can remain in the distribution and we remove everything else. This should allow us to keep python2 for limited use, not break everything, but should also send a strong message that it is no longer a first class citizen, and filter packages we need to focus Python 3 porting efforts on. (Sub-)packages that only provide a python2 importable module, and are not required for other packages, will be removed. Examples of situations where a (sub-)package does not provide only the importable module: * A package also provides an application, mostly likely in /usr/bin, /usr/libexec... ** (Note that according to current guidelines, if the Python 3 version of a package provides the same functionality, the Python 3 package should provide the application.) ** (In certain situations the provided application is only useful to boostrap or manage projects using the module. Such applications don't count.) * A package provides a plugin for another application, most likely trough a setuptools entrypoint interface or some custom location on disk. Our process will be: * File bugs for all packages that look like they only provide a Python 2 importable module. (This includes those needed by other packages we plan to remove.) * Leave at least a week for packagers to respond to the bugs. * If the packager approves or there is no response for a week, we will remove the package. There are currently ~3000 source packages that generate python2 dependent RPMs. Automation is being created to be able to provide us a rough list of packages to remove. === Packages to remove === The list is at https://fedoraproject.org/wiki/Changes/Mass_Python_2_ Package_Removal/List not to disturb the reading experience of this page. Packagers can block some packages from removal by responding on Bugzilla and providing reasons. If no general consensus is reached, FESCo will decide (as Python SIG does not have a formal process for such decisions). We'll also actively try to remove unused or optional dependencies to reduce the number of packages that need to be kept because other packages depend on them. As dependencies evolve over time, we will regularly repeat this proces on rawhide from now on even on future releases. Packagers are strongly encouraged to help port their applications to Python 3. Removing old Python 2 only applications from Fedora is also encouraged, especially if the upstream is dead. Python SIG is available to help with porting. Packaging guidelines will be updated to reflect that packaging for Python 3 only is the default. Instructions for Python 2 and dual-support will be moved to the Appendix. Python 2 will be marked deprecated (see https://fedoraproject.org/wiki/Packaging:Deprecating_Packages) Any package that only provides a Python 2 importable module may be marked as deprecated as well if the maintainer(s) want to. == Benefit to Fedora == A giant pile of unneeded software running on a legacy interperter will be removed from Fedora before the interpreter stops being supported upstream. While we would very much like to remove Python 2 entirely, this way we are not breaking Fedora, and we can accomodate some exceptions. == Scope == * Proposal owners: ** Provide a list of packages to remove ** Collect feedback from affected packagers ** Retire the python2 only packages ** Remove python2 subpackages from dual-python packages * Other developers: ** Ask for packages to be removed from the list if needed (with reasons). ** Remove python2 subpackages from dual-python packages (not needed, but helpful) ** Optionaly mark remainign python2 packages deprecated * Policies and guidelines: ** Python packaging guidelines will be changed to only describe Python 3 ** Python 2 and dual-support packaging will be moved to the appendix ** Only packages providing additional features different than importable modules will be allowed to be added in Fedora (with exception for dependenecies of other packages) ** Python 2 will be marked deprecated https://fedoraproject.org/wiki/Packaging:Deprecating_Packages * Trademark approval: not needed for this Change == Upgrade/compatibility impact == Packages removed form Fedora repos will remain on the installed OS until explicitly removed by the user or obsoleted by the packagers. We'll only obsolete packages that would break upgrade (from fedora-obsolete-packages). == How To Test == Any program written in Python and any program that has Python plugins could potentially be influenced by this change. Testing is different for software that is still using Python 2 and for software that has been switched to Python 3. For any ''python2'' programs, make sure those programs are still functional after the package removal. Since various packages that are no longer built will not be removed from an existing system, just upgrading and checking packages is not enough. Either a new installation should be used, or after a branching point, any packages which haven't been rebuilt for F30, so any packages with .fc29 or lower release suffix should be removed from the system before testing. For the ''python3'' programs, install all upgrades and check if the software works. Upgrade failures because of missing dependencies should be treated as bugs. Any removed python2 subpackages which break upgrades need to be added to Obsoletes in fedora-obsolete-packages. == User Experience == There will be less Python 2 RPMs in Fedora repos. Users are encouraged to switch to Python 3 and/or use Python 2 virtual environments and pip for development. == Dependencies == Ideally, all programs that use python2 would be switched to use python3. Although we don't expect everything to be switched over, as much as possible should be, so that the set of remaining python2 subpackages is as small as possible. == Contingency Plan == * Contingency mechanism: ** If for some reason not everything is removed, nothing happens, it can be removed later. If for some reason something breaks, some packages can be unretired or restored. ** If someone steps up to maintain Python 2 (including the full ecosystem of packages now in Fedora), they can decide to discontinue removing packages, revert the Change, or come up with another plan. (Note that in this case, current maintainers will most likely orphan many fundamental python2 packages.) == Documentation == This page is the main documentation. Also see: https://pythonclock.org/ -- 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/message/QRXWWZ2QG7JSZMAXNI6M6QMWV2XPCINM/ -- 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

Question about ovirt python sdk4，gluster volume rebalance return none
by chokko＠126.com 21 Aug '18

21 Aug '18

when in version 3 sdk ,i use: req_cluster = api.clusters.get(id=c_uid) req_volume = req_cluster.glustervolumes.get(id=volume_id) req_volume.rebalance().job.get_id() to get a rebalance job id to trace if the job is finished. Now I use ovirt python sdk4 for develop: cluster = clustersservice.cluster_service(clusterid) volume = cluster.gluster_volumes_service().volume_service(volumeid) response=volume.rebalance() the response is none,how can i get the rebalance job id?

5 8

Please use package versions when building rpms
by Dafna Ron 16 Aug '18

16 Aug '18

Hi All, As some of you may have noticed, we have been having failures for some of the tests in master in the past 24 hours with the following yum error: https://pastebin.com/vqJCLgrP After some debugging we found that the issue is caused because the package which is failing had two different commits and no version set which caused two different packages with exactly the same name to be created. To solve this issue we would need the package to be re-build with a new version set. Here are the details on the package and how it failed. As you can see below we had two different commits creating two different packages by the same name: https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image- template_standard-on-ghpush/30/ which was triggered by push: 00f5ffd4-a06e-11e8-8fc7-fa3846728ab0 https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image- template_standard-on-ghpush/31/ which was triggered by push: 3dfc5996-a09b-11e8-856c-ec86908871c4 checking the packages that exist in the 4.2 and master tested repos I can see that we have the same exact name for two different packages: 4.2: ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (0033d83c3d8b6b0506767de3a4e44ffd64b2605c) MD5 digest: OK (2b6e87e53a51175aeac61662561c0e20) master: ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (597577a11775a7fc21207f3e76fe4df8a5030912) MD5 digest: OK (74bafadf2afae5f7797a90c982ad2767) This would cause yum to fail because we cannot have the same package name with different checksums. If anyone needs help in setting up versioning please contact myself or anyone from the CI team and we would be happy to assist. Thanks, Dafna

3 2

bugzilla priority?
by Hetz Ben Hamo 16 Aug '18

16 Aug '18

Hi, I've created this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1609029 This bug, IMHO, is *critical* - I want to build a PoC to a customer (before he decides to buy or not RHV) and this is embarrassing... Any chance this bug could get a higher prioritizing please? Thanks

2 1

ovirt-engine has been tagged (ovirt-engine-4.2.5.4)
by Tal Nisan 15 Aug '18

15 Aug '18

1 0

ovirt-engine has been tagged (ovirt-engine-4.2.6.3)
by Tal Nisan 14 Aug '18

14 Aug '18

1 0

[URGENT] Blocking ovirt 4.2.6 RC2 release on VDSM
by Sandro Bonazzola 14 Aug '18

14 Aug '18

Hi, started preparing for 4.2.6 RC2 release and stumbled upon: https://bugzilla.redhat.com/show_bug.cgi?id=1615391 basically, vdsm from latest tag can't be installed anymore, thus blocking the release until this is fixed. Please handle with maximum priority. 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…>

1 1

who owns ovirt copr?
by Greg Sheremeta 13 Aug '18

13 Aug '18

Hi, I'd like to move https://copr.fedorainfracloud.org/coprs/mlibra/ovirt-web-ui/ to https://copr.fedorainfracloud.org/coprs/ovirt/ Who owns this / can share the password? Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

6 11

how do I setup LDAP for dev server?
by Greg Sheremeta 12 Aug '18

12 Aug '18

Hi, I'm trying to tie my 389ds server to my dev engine built from source. I followed the instructions [ https://www.ovirt.org/documentation/admin-guide/chap-Users_and_Roles/] for configuring LDAP (which assume an RPM installation, I think), and then copied the /etc config files to ~greg/ovirt-engine/etc/ovirt-engine ERROR [org.ovirt.engine.core.sso.utils.SsoExtensionsManager] (ServerService Thread Pool -- 44) [] Could not load extension based on configuration file '/home/greg/ovirt-engine/etc/ovirt-engine/extensions.d/lan-authn.properties'. Please check the configuration file is valid. Exception message is: Error loading extension 'lan-authn': The module 'org.ovirt.engine-extensions.aaa.ldap' cannot be loaded: org.ovirt.engine-extensions.aaa.ldap ERROR [org.ovirt.engine.core.sso.utils.SsoExtensionsManager] (ServerService Thread Pool -- 44) [] Could not load extension based on configuration file '/home/greg/ovirt-engine/etc/ovirt-engine/extensions.d/lan.properties'. Please check the configuration file is valid. Exception message is: Error loading extension 'lan': The module 'org.ovirt.engine-extensions.aaa.ldap' cannot be loaded: org.ovirt.engine-extensions.aaa.ldap What am I missing? Are there developer instructions for this somewhere? Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

2 1

ovirt-engine has been tagged (ovirt-engine-4.2.6.2)
by Tal Nisan 12 Aug '18

12 Aug '18

1 0

ovirt-engine has been tagged (ovirt-engine-4.2.6.1)
by Tal Nisan 12 Aug '18

12 Aug '18

2 1

[ OST Failure Report ] [ oVirt 4.2 (imgbased) ] [ 09-08-2018 ] [ 004_basic_sanity.check_snapshot_with_memory ]
by Dafna Ron 10 Aug '18

10 Aug '18

Hi, We have a failure in 4.2 which I think may be related to the patch itself. Jira opened with additional info: https://ovirt-jira.atlassian.net/browse/OVIRT-2418 *Link and headline of suspected patches: * *We failed patch https://gerrit.ovirt.org/#/c/93545/ <https://gerrit.ovirt.org/#/c/93545/> - core: remove lvs after a failed upgrade on ovirt-4.2Link to Job:* * https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2819/ <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2819/>Link to all logs:* * https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2819/artifact/b… <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2819/>(Relevant) error snippet from the log: <error>* Error Message Fault reason is "Operation Failed". Fault detail is "[Cannot run VM. Low disk space on Storage Domain iscsi.]". HTTP response code is 409. Stacktrace Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/004_basic_sanity.py", line 589, in check_snapshot_with_memory vm_service.start() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 30074, in start return self._internal_action(action, 'start', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Cannot run VM. Low disk space on Storage Domain iscsi.]". HTTP response code is 409. *</error>*

3 2

vdsm has been tagged (v.4.20.37)
by Petr Horacek 10 Aug '18

10 Aug '18

Vdsm 4.20.37 for oVirt 4.2.6 rc2.

1 0

[VDSM] Fedora rawhide status
by Nir Soffer 09 Aug '18

09 Aug '18

We did not update the Fedora rawhide for few month since a package was missing. Now that this issue was solved, we have new errors, 1. async is a keywoard in python 3.7 Compiling './tests/storage/fakesanlock.py'... *** File "./tests/storage/fakesanlock.py", line 65 async=False): ^ SyntaxError: invalid syntax We have many of these. The issue is sanlock api uses the kwarg "async", and python 3.7 made this invalid syntax. $ ./python Python 3.7.0+ (heads/3.7:426135b674, Aug 9 2018, 22:50:16) [GCC 8.1.1 20180712 (Red Hat 8.1.1-5)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> def foo(async=False): File "<stdin>", line 1 def foo(async=False): ^ SyntaxError: invalid syntax >>> async = True File "<stdin>", line 1 async = True ^ SyntaxError: invalid syntax Thank you python developers for making our life more interesting :-) So we will have to change sanlock python binding to replace "async" with something else. I'll file sanlock bug for this. 2. test_sourceroute_add_remove_and_read fails No idea why it fails, hopefully Dan or Edward have a clue. FAIL: test_sourceroute_add_remove_and_read (network.sourceroute_test.TestSourceRoute) ---------------------------------------------------------------------- Traceback (most recent call last): File "/vdsm/tests/testValidation.py", line 193, in wrapper return f(*args, **kwargs) File "/vdsm/tests/network/sourceroute_test.py", line 80, in test_sourceroute_add_remove_and_read self.assertEqual(2, len(routes), routes) AssertionError: 2 != 0 -------------------- >> begin captured logging << -------------------- 2018-08-09 19:36:31,446 DEBUG (MainThread) [root] /sbin/ip link add name dummy_UTpMy type dummy (cwd None) (cmdutils:151) 2018-08-09 19:36:31,455 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 2018-08-09 19:36:31,456 DEBUG (netlink/events) [root] START thread <Thread(netlink/events, started daemon 140332374083328)> (func=<bound method Monitor._scan of <vdsm.network.netlink.monitor.Monitor object at 0x7fa1b18dc6d0>>, args=(), kwargs={}) (concurrent:193) 2018-08-09 19:36:31,456 DEBUG (MainThread) [root] /sbin/ip link set dev dummy_UTpMy up (cwd None) (cmdutils:151) 2018-08-09 19:36:31,463 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 2018-08-09 19:36:31,464 DEBUG (netlink/events) [root] FINISH thread <Thread(netlink/events, started daemon 140332374083328)> (concurrent:196) 2018-08-09 19:36:31,471 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 2018-08-09 19:36:31,471 DEBUG (MainThread) [root] Adding source route for device dummy_UTpMy (sourceroute:195) 2018-08-09 19:36:31,472 DEBUG (MainThread) [root] /sbin/ip -4 route add 0.0.0.0/0 via 192.168.99.2 dev dummy_UTpMy table 3232260865 (cwd None) (cmdutils:151) 2018-08-09 19:36:31,478 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 2018-08-09 19:36:31,479 DEBUG (MainThread) [root] /sbin/ip -4 route add 192.168.99.0/29 via 192.168.99.1 dev dummy_UTpMy table 3232260865 (cwd None) (cmdutils:151) 2018-08-09 19:36:31,485 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 2018-08-09 19:36:31,485 DEBUG (MainThread) [root] /sbin/ip rule add from 192.168.99.0/29 prio 32000 table 3232260865 (cwd None) (cmdutils:151) 2018-08-09 19:36:31,492 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 2018-08-09 19:36:31,492 DEBUG (MainThread) [root] /sbin/ip rule add from all to 192.168.99.0/29 dev dummy_UTpMy prio 32000 table 3232260865 (cwd None) (cmdutils:151) 2018-08-09 19:36:31,498 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 2018-08-09 19:36:31,499 DEBUG (MainThread) [root] /sbin/ip rule (cwd None) (cmdutils:151) 2018-08-09 19:36:31,505 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 2018-08-09 19:36:31,505 WARNING (MainThread) [root] Could not parse rule 32000: from all to 192.168.99.0 /29 iif dummy_d3SHQ [detached] lookup 3232260865 (iproute2:60) 2018-08-09 19:36:31,505 WARNING (MainThread) [root] Could not parse rule 32000: from all to 192.168.99.0 /29 iif dummy_d3SHQ [detached] lookup 3232260865 (iproute2:60) 2018-08-09 19:36:31,505 WARNING (MainThread) [root] Could not parse rule 32000: from all to 192.168.99.0 /29 iif dummy_UTpMy lookup 3232260865 (iproute2:60) 2018-08-09 19:36:31,506 DEBUG (MainThread) [root] /sbin/ip rule (cwd None) (cmdutils:151) 2018-08-09 19:36:31,512 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 2018-08-09 19:36:31,512 WARNING (MainThread) [root] Could not parse rule 32000: from all to 192.168.99.0 /29 iif dummy_d3SHQ [detached] lookup 3232260865 (iproute2:60) 2018-08-09 19:36:31,512 WARNING (MainThread) [root] Could not parse rule 32000: from all to 192.168.99.0 /29 iif dummy_d3SHQ [detached] lookup 3232260865 (iproute2:60) 2018-08-09 19:36:31,513 WARNING (MainThread) [root] Could not parse rule 32000: from all to 192.168.99.0 /29 iif dummy_UTpMy lookup 3232260865 (iproute2:60) 2018-08-09 19:36:31,513 DEBUG (MainThread) [root] Removing source route for device dummy_UTpMy (sourceroute:215) 2018-08-09 19:36:31,513 DEBUG (MainThread) [root] /sbin/ip link del dev dummy_UTpMy (cwd None) (cmdutils:151) 2018-08-09 19:36:31,532 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:159) 3. qemu-io returns now non-zero code on failures, breaking our tests This command use to return 0 on failures, and the only way to detect failures was to check the output. Now it was fixed to return non-zero code, and this breaks our tests. I think this should be an easy fix. Here is an example: 1m_____________________________ test_no_match[qcow2] _____________________________ tmpdir = local('/var/tmp/vdsm/test_no_match_qcow2_0'), image_format = 'qcow2' def test_no_match(tmpdir, image_format): path = str(tmpdir.join('test.' + image_format)) op = qemuimg.create(path, '1m', image_format) op.run() qemuio.write_pattern(path, image_format, pattern=2) with pytest.raises(qemuio.VerificationError): > qemuio.verify_pattern(path, image_format, pattern=4) storage/qemuio_test.py:59: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ path = '/var/tmp/vdsm/test_no_match_qcow2_0/test.qcow2', format = 'qcow2' offset = 512, len = 1024, pattern = 4 def verify_pattern(path, format, offset=512, len=1024, pattern=5): read_cmd = 'read -P %d -s 0 -l %d %d %d' % (pattern, len, offset, len) cmd = ['qemu-io', '-f', format, '-c', read_cmd, path] rc, out, err = commands.execCmd(cmd, raw=True) if rc != 0 or err != b"": > raise cmdutils.Error(cmd, rc, out, err) E Error: Command ['qemu-io', '-f', 'qcow2', '-c', 'read -P 4 -s 0 -l 1024 512 1024', '/var/tmp/vdsm/test_no_match_qcow2_0/test.qcow2'] failed with rc=1 out='Pattern verification failed at offset 512, 1024 bytes\nread 1024/1024 bytes at offset 512\n1 KiB, 1 ops; 0.0001 sec (7.570 MiB/sec and 7751.9380 ops/sec)\n' err='' storage/qemuio.py:50: Error ----------------------------- Captured stderr call ----------------------------- 2018-08-09 19:37:32,126 DEBUG (MainThread) [storage.operation] /usr/bin/taskset --cpu-list 0-1 /usr/bin/nice -n 19 /usr/bin/ionice -c 3 /usr/bin/qemu-img create -f qcow2 -o compat=0.10 /var/tmp/vdsm/test_no_match_qcow2_0/test.qcow2 1m (cwd None) (operation:150) 2018-08-09 19:37:32,148 DEBUG (MainThread) [storage.operation] SUCCESS: <err> = ''; <rc> = 0 (operation:169) 2018-08-09 19:37:32,148 DEBUG (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 qemu-io -f qcow2 -c 'write -P 2 512 1024' /var/tmp/vdsm/test_no_match_qcow2_0/test.qcow2 (cwd None) (commands:66) 2018-08-09 19:37:32,170 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (commands:87) 2018-08-09 19:37:32,171 DEBUG (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 qemu-io -f qcow2 -c 'read -P 4 -s 0 -l 1024 512 1024' /var/tmp/vdsm/test_no_match_qcow2_0/test.qcow2 (cwd None) (commands:66) 2018-08-09 19:37:32,181 DEBUG (MainThread) [root] FAILED: <err> = ''; <rc> = 1 (commands:87) ------------------------------ Captured log call ------------------------------- operation.py 150 DEBUG /usr/bin/taskset --cpu-list 0-1 /usr/bin/nice -n 19 /usr/bin/ionice -c 3 /usr/bin/qemu-img create -f qcow2 -o compat=0.10 /var/tmp/vdsm/test_no_match_qcow2_0/test.qcow2 1m (cwd None) operation.py 169 DEBUG SUCCESS: <err> = ''; <rc> = 0 commands.py 66 DEBUG /usr/bin/taskset --cpu-list 0-1 qemu-io -f qcow2 -c 'write -P 2 512 1024' /var/tmp/vdsm/test_no_match_qcow2_0/test.qcow2 (cwd None) commands.py 87 DEBUG SUCCESS: <err> = ''; <rc> = 0 commands.py 66 DEBUG /usr/bin/taskset --cpu-list 0-1 qemu-io -f qcow2 -c 'read -P 4 -s 0 -l 1024 512 1024' /var/tmp/vdsm/test_no_match_qcow2_0/test.qcow2 (cwd None) commands.py 87 DEBUG FAILED: <err> = ''; <rc> = 1 4. pywatch tests still fail Looks like our on_fedora() helper is broken, so this test is not marked as xfail. ______________________ TestPyWatch.test_timeout_backtrace ______________________ self = <pywatch_test.TestPyWatch object at 0x7f5cf42899d0> @pytest.mark.xfail(on_fedora(), reason="py-bt is broken on Fedora 27") @pytest.mark.xfail(on_ovirt_ci(), reason="py-bt randomly unavailable on EL7 nodes") def test_timeout_backtrace(self): script = ''' import time def outer(): inner() def inner(): time.sleep(10) outer() ''' rc, out, err = exec_cmd(['./py-watch', '0.1', 'python', '-c', script]) > assert b'in inner ()' in out E AssertionError: assert 'in inner ()' in '=============================================================\n= Watched process timed out ... Terminating watched process =\n=============================================================\n' pywatch_test.py:74: AssertionError ------------------------------ Captured log call ------------------------------- cmdutils.py 151 DEBUG ./py-watch 0.1 python -c ' import time def outer(): inner() def inner(): time.sleep(10) outer() ' (cwd None) cmdutils.py 159 DEBUG FAILED: <err> = '\nwarning: Loadable section ".note.gnu.property" outside of ELF segments\n\nwarning: Loadable section ".note.gnu.property" outside of ELF segments\n'; <rc> = 143 5. ovs tests that pass on Fedora 28 fail on rawhide Not sure how why the tests pass on Fedora 28 and fail on CentOS and Fedora rawhide. ________ ERROR at setup of TestOvsApiBase.test_execute_a_single_command ________ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() with xfail_when_running_on_travis_with_centos(): > service.setup() network/integration/ovs/conftest.py:37: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f79737589d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError ------------------------------ Captured log setup ------------------------------ cmdutils.py 151 DEBUG /usr/share/openvswitch/scripts/ovs-ctl status (cwd None) cmdutils.py 159 DEBUG FAILED: <err> = ''; <rc> = 1 cmdutils.py 151 DEBUG /usr/share/openvswitch/scripts/ovs-ctl --system-id=random start (cwd None) cmdutils.py 159 DEBUG FAILED: <err> = 'modprobe: FATAL: Module openvswitch not found in directory /lib/modules/4.4.0-104-generic\nrmmod: ERROR: Module bridge is in use by: br_netfilter\n'; <rc> = 1 cmdutils.py 151 DEBUG /usr/share/openvswitch/scripts/ovs-ctl status (cwd None) cmdutils.py 159 DEBUG FAILED: <err> = ''; <rc> = 1 Otherwise all tests pass, so we are in pretty good shape :-) Nir

1 1

repoman glitch?
by Dan Kenigsberg 09 Aug '18

09 Aug '18

I've executed http://jenkins.ovirt.org/job/ovirt-system-tests_manual/3053/parameters/ using http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-on-demand-el7-x86_64/… as customer repo. The custom repo has vdsm-4.20.36-11.git9f9bbcc.el7.x86_64.rpm which I expected would be pulled onto ost hosts. However http://jenkins.ovirt.org/job/ovirt-system-tests_manual/3053/artifact/export… shows that this was not the case. Any idea why is that?

5 8

Veritas: Image Transfer Finalize Call Failure
by Pavan Chavva 09 Aug '18

09 Aug '18

Hi Team, Can anyone help answer this question? Best, Pavan. ---------- Forwarded message --------- From: Ketan Pachpande <Ketan.Pachpande(a)veritas.com> Date: Thu, Aug 9, 2018 at 9:44 AM Subject: RE: [EXTERNAL] Updated invitation: RHV- Veritas Netbackup Weekly Sync (Tentative) @ Weekly from 10am to 10:30am on Thursday (EDT) ( ketan.pachpande(a)veritas.com) To: pchavva(a)redhat.com <pchavva(a)redhat.com>, Abhay Marode < Abhay.Marode(a)veritas.com>, Suchitra Herwadkar < Suchitra.Herwadkar(a)veritas.com>, Mahesh Falmari <Mahesh.Falmari(a)veritas.com>, Sudhakar Paulzagade <Sudhakar.Paulzagade(a)veritas.com>, Navin Tah < Navin.Tah(a)veritas.com> Cc: ydary(a)redhat.com <ylavi(a)redhat.com>, adbarbos(a)redhat.com < adbarbos(a)redhat.com> Hi Pavan, I have a question regarding imagetransfer finalize call. After imagetransfer upload, when I call the finalize the transfer, I am getting Finalize Failure error. I am following these steps to upload a disk via rest API. 1. Create disk on a storage domain (POST https:// <ovirt-server>/ovirt-engine/api/disks) 2. Initiate imagetransfer and get the proxy_url and signed_ticket (https:// <ovirt-server> /ovirt-engine/api/imagetransfers) 3. Upload data using curl (to proxy URL) 1. Finalize the transfer: After that disk is getting deleted automatically. Sequence of events in events tab: Is it expected behaviour on finalizing the imagetransfer failure? If so, how to troubleshoot and get the reason of finalizing failure? Thanks, Ketan Pachpande

3 3

ovirt-engine has been tagged (ovirt-engine-4.2.5.3)
by Sandro Bonazzola 09 Aug '18

09 Aug '18

-- 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 4.2 (ovirt-engine) ] [ 07-08-2018 ] [ 004_basic_sanity.update_template_version ]
by Dafna Ron 09 Aug '18

09 Aug '18

Hi, We are failing ovirt 4.2 on project ovirt-engine on test 004_basic_sanity.update_template_version. I believe the reported patch from CQ may have indeed caused the issue. Eli, can you please check this issue? *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/93501/ <https://gerrit.ovirt.org/#/c/93501/> - * *core:make search string fields not null and emptyLink to Job:https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2800 <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2800>Link to all logs:https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2800/artif… <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2800/artifact/b…>(Relevant) error snippet from the log: <error><JsonRpcRequest id: "0aec9ef2-5e1f-4cb6-bf75-f5826d2ae135", method: Volume.getInfo, params: {storagepoolID=fe6f6819-4791-4624-aa56-c82e49b0eaf3, storagedomainID=2a3af2d0-c00e-4ac7-a162-fa08d33c173f, imageID=2d2f61d4-2347-4200-9c1f-0ee376104ef0, volumeID=21ea717f-e3a1-4c36-8101-ba746bd78c40}>2018-08-07 06:12:46,522-04 INFO [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] Running command: AddVmTemplateCommand internal: false. Entities affected : ID: fe6f6819-4791-4624-aa56-c82e49b0eaf3 Type: StoragePoolAction group CREATE_TEMPLATE with role type USER2018-08-07 06:12:46,525-04 INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] START, SetVmStatusVDSCommand( SetVmStatusVDSCommandParameters:{vmId='64293490-e128-48b7-9e23-0491b48d9a1f', status='ImageLocked', exitStatus='Normal'}), log id: eca02a92018-08-07 06:12:46,527-04 INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] FINISH, SetVmStatusVDSCommand, log id: eca02a92018-08-07 06:12:46,527-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] method: runVdsCommand, params: [SetVmStatus, SetVmStatusVDSCommandParameters:{vmId='64293490-e128-48b7-9e23-0491b48d9a1f', status='ImageLocked', exitStatus='Normal'}], timeElapsed: 3ms2018-08-07 06:12:46,537-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.CustomSQLErrorCodeSQLExceptionTranslator] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] Translating SQLException with SQL state '23502', error code '0', message [ERROR: null value in column "description" violates not-null constraint Detail: Failing row contains (ce532690-2131-49a8-b2a0-183936727092, CirrOS_0.4.0_for_x86_64_glance_template, 512, 5b1f874d-dc92-43ed-86ef-a9c2d6bfc9a3, 0, null, fe7292a4-c998-4f6c-897c-fa7525911a16, 2018-08-07 06:12:46.529-04, 1, null, f, 1, 1, 1, Etc/GMT, t, f, 2018-08-07 06:12:46.530974-04, null, null, f, 1, 0, 0, 1, 0, , 3, null, null, null, 0, , , 256, TEMPLATE, 0, 1, 31a8e1fa-1fad-456c-8b8a-aa11551cae9d, f, null, f, f, 1, f, f, f, d0d66980-9a26-11e8-b2f3-5452c0a8c802, null, , f, 0, null, null, null, guest_agent, null, null, null, 2, null, 2, 12345678, f, interleave, t, t, deb3f53e-13c5-4aea-bf90-0339eba39fed, null, null, null, null, 22716173-2816-a109-1d2f-c44d945e92dd, 3b3f239c-d8bb-423f-a39c-e2b905473b83, null, 1, LOCK_SCREEN, 2, null, null, 2048, null, AUTO_RESUME, t). Where: SQL statement "INSERT INTO vm_static( child_count, creation_date, description, free_text_comment, mem_size_mb, max_memory_size_mb, num_of_io_threads, vm_name, num_of_sockets, cpu_per_socket, threads_per_cpu, os, vm_guid, cluster_id, num_of_monitors, single_qxl_pci, allow_console_reconnect, template_status, usb_policy, time_zone, fail_back, vm_type, nice_level, cpu_shares, default_boot_sequence, default_display_type,* *</error>*

3 4

[VDSM] Test pass on Travis! (on Fedora 28)
by Nir Soffer 08 Aug '18

08 Aug '18

Tests pass on Fedora 28: https://travis-ci.org/nirs/vdsm/jobs/413702715 Fedora rawhide fails with various issues, will open another thread about it. Still failing on CentOS in the ovs tests: https://travis-ci.org/nirs/vdsm/jobs/413702714 (see errors bellow). So maybe we need to mark tests as xfail only on CentOS - or maybe the fact it works on Fedora means we don't understand the failure yet? We don't know what is the vm running our tests, but we control the CentOS/Fedora container. Maybe something is missing in the CentOS container? https://github.com/oVirt/vdsm/blob/master/docker/Dockerfile.centos Nir --- ________ ERROR at setup of TestOvsApiBase.test_execute_a_single_command ________ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError ------------------------------ Captured log setup ------------------------------ cmdutils.py 151 DEBUG /usr/share/openvswitch/scripts/ovs-ctl status (cwd None) cmdutils.py 159 DEBUG FAILED: <err> = ''; <rc> = 1 cmdutils.py 151 DEBUG /usr/share/openvswitch/scripts/ovs-ctl --system-id=random start (cwd None) cmdutils.py 159 DEBUG FAILED: <err> = 'rmmod: ERROR: Module bridge is in use by: br_netfilter\n'; <rc> = 1 cmdutils.py 151 DEBUG /usr/share/openvswitch/scripts/ovs-ctl status (cwd None) cmdutils.py 159 DEBUG FAILED: <err> = ''; <rc> = 1 _________ ERROR at setup of TestOvsApiBase.test_execute_a_transaction __________ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError ____ ERROR at setup of TestOvsApiBase.test_instantiate_vsctl_implementation ____ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError ___ ERROR at setup of TestOvsApiWithSingleRealBridge.test_add_slave_to_bond ____ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError ___ ERROR at setup of TestOvsApiWithSingleRealBridge.test_create_remove_bond ___ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError ERROR at setup of TestOvsApiWithSingleRealBridge.test_create_vlan_as_fake_bridge @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError _ ERROR at setup of TestOvsApiWithSingleRealBridge.test_remove_slave_from_bond _ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError ___________ ERROR at setup of TestOvsInfo.test_ovs_info_with_sb_bond ___________ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError ___________ ERROR at setup of TestOvsInfo.test_ovs_info_with_sb_nic ____________ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError _____________ ERROR at setup of SetupTransactionTests.test_dry_run _____________ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() > service.setup() network/integration/ovs/conftest.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7f15a29655d0> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError network/ovsnettestlib.py:39: AssertionError =============== 40 passed, 32 skipped, 10 error in 4.81 seconds ================

1 0

[ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 6-08-2018 ] [ TEST NAME ]
by Dafna Ron 08 Aug '18

08 Aug '18

Hi, We have a failure in CQ on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite. *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/93466/ <https://gerrit.ovirt.org/#/c/93466/> - core: clean stale image_transfer on upgradeLink to Job:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975 <https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975>Link to all logs:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975/ar… <https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975/artifac…>(Relevant) error snippet from the log: <error>* [ INFO ] Stage: Misc configuration [ INFO ] Upgrading CA [ INFO ] Backing up database localhost:ovirt_engine_history to '/var/lib/ovirt-engine-dwh/backups/dwh-20180806074534.L73Aa6.dump'. [ INFO ] Creating/refreshing DWH database schema [ INFO ] Configuring WebSocket Proxy [ INFO ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20180806074537.V9dDgr.dump'. [ INFO ] Creating/refreshing Engine database schema [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0270_add_foreign_key_to_image_transfers.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed [WARNING] Rollback of DWH database postponed to Stage "Clean up" [ INFO ] Rolling back database schema [ INFO ] Clearing Engine database engine [ INFO ] Restoring Engine database engine [ INFO ] Restoring file '/var/lib/ovirt-engine/backups/engine-20180806074537.V9dDgr.dump' to database localhost:engine. [ ERROR ] Errors while restoring engine database, please check the log file for details [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20180806074515-jb06pl.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20180806074550-setup.conf' [WARNING] Rollback of DWH database started This might be a long process, but it should be safe to start the engine service before it finishes, if needed. [ INFO ] Clearing DWH database ovirt_engine_history [ INFO ] Restoring DWH database ovirt_engine_history [ INFO ] Restoring file '/var/lib/ovirt-engine-dwh/backups/dwh-20180806074534.L73Aa6.dump' to database localhost:ovirt_engine_history. [ ERROR ] Errors while restoring ovirt_engine_history database, please check the log file for details [ INFO ] Stage: Pre-termination *</error>*

3 5

iSCSI and targetcli
by Hetz Ben Hamo 07 Aug '18

07 Aug '18

When trying to configure targetcli as target, the ACL requires the initiators machines IQN in order to allow them access. Today, you'll need to login to each node, get the IQN and add it to the ACL. Is it possible to add the IQN of the nodes in the HE WEB UI?

2 2

unboundid-ldapsdk-4.0.7 is now available for testing
by Sandro Bonazzola 07 Aug '18

07 Aug '18

On Fedora we had previously 4.0.6. The new releases 4.0.7 will be soon available in updates-testing repository for Fedora >= 28 and includes several bug fixes and a few enhancements. You can see release notes here: https://github.com/pingi dentity/ldapsdk/releases In oVirt this package is required by ovirt-engine-extension-aaa-ldap. If you're going to test the package, please provide karma: https://bodhi.fedoraproject.org/updates/unboundid-ldapsdk-4.0.7-1.fc28 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…>

1 0

Re: [ovirt-users] Re: Unable to login to the WEB UI Unexpected character ('<' (code 60))....
by Greg Sheremeta 06 Aug '18

06 Aug '18

On Mon, Aug 6, 2018 at 6:25 AM <sylvain.palous(a)gmail.com> wrote: > It doesn't show any errors : > https://ibb.co/cD2A1K Thanks. This is a bug, so adding devel. So that console being empty + an empty ui.log means it's not a gwt problem. Are you logging in with the default admin user? Does it happen with English selected as the locale? Does it happen when you connect via a browser on the same machine? Can you try adding entries to /etc/hosts and connect via a hostname instead of IP? Adding @Ravi Nori <rnori(a)redhat.com> in case this is some known issue with connecting via IP. > > Test with another site : > https://ibb.co/cnVDMK > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/FQZ5GDBFLJLQD… > -- 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>

2 1

guest agent info about disks and filesystems
by Scott Dickerson 06 Aug '18

06 Aug '18

I have a pair of questions I could use some help with. 1. Does the oVirt guest agent collect filesystem level information? I'm hoping something like what `df -h` would report. File systems, free vs used space, etc. Bonus points if we can get that kind of info from linux and windows agents. 2. Assuming that info is available, where can I access it? I assume it isn't surfaced via the REST api (yet), but it would be good to know where it is available. Why? I'm updating VM Portal (web-ui), and it would be great to chart/report guest derived data rather than infrastructure disk provisioned vs allocated space. Thanks! -- Scott Dickerson Senior Software Engineer RHV-M Engineering - UX Team Red Hat, Inc

5 5

no vms autostart?
by Hetz Ben Hamo 06 Aug '18

06 Aug '18

I just found out that there is no option for autostart VM's. This functionality is extremely crucial when a system is going down after a UPS ran out of juice (or that it didn't work when the power failed). Starting VMs automatically help the recovery process, and editable startup list could help a lot more (for example: if 10 VMs are dependent on AD services, the Windows 2012 should be booted 2nd, right after HE, and then the other machines). Autostart VM's could help a lot with UPS if the list can go "backward" to power off VMs in a serialized matter, so when a UPS detects a power loss, it could signal the HE to start shutting down VMs by a list. Any chance to have this feature in 4.3?

3 3

VM Portal UI redesign -- weekly report [29-Jul-2018 - 4-Aug-2018]
by Greg Sheremeta 05 Aug '18

05 Aug '18

VM Portal UI redesign -- weekly report [29-Jul-2018 - 4-Aug-2018] screens: https://github.com/oVirt/ovirt-design/pulls and https://drive.google.com/drive/folders/1JHhQfi32uZd7V8XpoIcdNIUIZd-tmV9I?us… github issues: https://github.com/oVirt/ovirt-web-ui/issues?q=label%3Aredesign StatusThe updated landing page (VM List) is in code review The edit page has made good progress, but is getting a bit bogged down - we've started doing official sprints / agile on the team, hopefully will help accelerate things - when we don't have REST API capabilities, we should consider tabling those items and progressing on other things A VM Portal release (1.4.2) is scheduled for Friday, August 10. It will contain: - new VM List page with new PatternFly notification drawer - new Edit page skeleton - Edit > Overview card working - Edit > Details working - Edit > Snapshots working [We will be officially releasing VM Portal every two weeks now, at the completion of each sprint.] Meeting minutes Aug 2 2018 Attendees: Greg, Scott, Bohdan, Laura, Liz, Lucie Edit > Snapshots card -- design is complete, coding is almost complete and in review Edit > Overview card (top left) -- coded, sagas are not quite done Edit > Overview card (top left) -- we overlooked icon upload Edit > Details card -- IP address discussion. It would be nice to show IPs (v4, v6?). Liz will mockup. Edit > Utilization card -- revisiting disks. Scott needs to do some legwork -- looks like data we have is missing in the REST API results Edit > NIC and Disks review (Liz): they are very similar. Designs are close, perhaps complete Discussion re: hotplugging - Need to offer user option to hotplug (modal) - Alert box for pending changes (in each card) - We can grab Next Run config (vs current) in REST - (vm name is runtime changeable) Discussion re: disabling buttons vs hiding them when users don’t have permissions -- 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

Is ovirt support node HA?
by pengyixiang 05 Aug '18

05 Aug '18

Is ovirt support node HA? How did they works? Is there any document about this? like one node down, we fence this down node, and startup these vms in others active node. Cheers， Pencc

2 1

Issue with engine-setup on master
by Ravi Shankar Nori 02 Aug '18

02 Aug '18

Hi, I pulled the latest mater rpms from nightly builds [1] and there seems to be a issue running engine-setup. engine-setup fails with message [root@laptop ovirt-engine-master-new9]# engine-setup ***L:ERROR Internal error: No module named 'async_tasks_map' I had the same issue with dev env on master Any ideas Thanks Ravi [1] https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm

4 8

vdsm has been tagged (v4.20.36)
by Milan Zamazal 01 Aug '18

01 Aug '18

Vdsm 4.20.36 for oVirt 4.2.6 rc1.

1 0

ovirt-engine has been tagged (ovirt-engine-4.2.6)
by Tal Nisan 01 Aug '18

01 Aug '18

1 0