November 2018 - Devel - oVirt List Archives

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

11 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

query on running OST
by Pooja Pandey 23 Jan '19

23 Jan '19

Hello Team, Could you please help me in answering a query about OST run.I am trying to run on a virtual machine and it is failing with an error that libvirtError: unsupported configuration: Domain requires KVM, but it is not available. Is it necessary to run this Ovirt System Test on a hypervisor only?Please reply on this so that I can proceed further.Thanks.... Regards, Pooja -- DISCLAIMER - *MSysTechnologies LLC* This email message, contents and its attachments may contain confidential, proprietary or legally privileged information and is intended solely for the use of the individual or entity to whom it is actually intended. If you have erroneously received this message, please permanently delete it immediately and notify the sender. If you are not the intended recipient of the email message,you are notified strictly not to disseminate,distribute or copy this e-mail.E-mail transmission cannot be guaranteed to be secure or error-free as Information could be intercepted, corrupted, lost, destroyed, incomplete or contain viruses and MSysTechnologies LLC accepts no liability for the contents and integrity of this mail or for any damage caused by the limitations of the e-mail transmission.

5 9

[VDSM] all test passed, build failed with "tar: journal/b087148aba6d49b9bbef488e52a48752/system.journal: file changed as we read it"
by Nir Soffer 21 Dec '18

21 Dec '18

We have this failure that pops randomly: 1. All tests pass *00:13:13.284* ___________________________________ summary ____________________________________*00:13:13.285* tests: commands succeeded*00:13:13.286* storage-py27: commands succeeded*00:13:13.286* storage-py36: commands succeeded*00:13:13.286* lib-py27: commands succeeded*00:13:13.287* lib-py36: commands succeeded*00:13:13.288* network-py27: commands succeeded*00:13:13.290* network-py36: commands succeeded*00:13:13.291* virt-py27: commands succeeded*00:13:13.292* virt-py36: commands succeeded*00:13:13.293* congratulations :) 2. But we fail to collect logs at the end *00:14:35.992* ##########################################################*00:14:35.995* ## Wed Nov 28 17:39:50 UTC 2018 Finished env: fc28:fedora-28-x86_64*00:14:35.996* ## took 764 seconds*00:14:35.997* ## rc = 1*00:14:35.997* ##########################################################*00:14:36.009* ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv*00:14:36.010* ##! Last 20 log entries: /tmp/mock_logs.Lcop4ZOq/script/stdout_stderr.log*00:14:36.011* ##!*00:14:36.012* journal/b087148aba6d49b9bbef488e52a48752/system.journal*00:14:36.013* tar: journal/b087148aba6d49b9bbef488e52a48752/system.journal: file changed as we read it*00:14:36.014* journal/b087148aba6d49b9bbef488e52a48752/user-1000.journal*00:14:36.015* lastlog*00:14:36.015* libvirt/*00:14:36.015* libvirt/lxc/*00:14:36.015* libvirt/libxl/*00:14:36.016* libvirt/qemu/*00:14:36.016* libvirt/qemu/LiveOS-f920001d-be4e-47ea-ac26-72480fd5be87.log*00:14:36.017* libvirt/uml/*00:14:36.017* ovirt-guest-agent/*00:14:36.017* ovirt-guest-agent/ovirt-guest-agent.log*00:14:36.017* README*00:14:36.018* samba/*00:14:36.018* samba/old/*00:14:36.018* sssd/*00:14:36.018* tallylog*00:14:36.018* wtmp*00:14:36.018* Took 678 seconds*00:14:36.018* ===================================*00:14:36.019* ##!*00:14:36.019* ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^*00:14:36.019* ##!######################################################## This looks like an issue with vdsm check-patch.sh: function collect_logs { res=$? [ "$res" -ne 0 ] && echo "*** err: $res" cd /var/log tar -cvzf "$EXPORT_DIR/mock_varlogs.tar.gz" * cd /var/host_log tar -cvzf "$EXPORT_DIR/host_varlogs.tar.gz" * } trap collect_logs EXIT Seems that tar fail to collect log if the log is modified while copied, which makes sense. We can ignore errors in tar, since log collection should not fail the build, but I think a better solution is to avoid collecting any logs since vdsm writes its own logs during tests - all the info must be in vdsm log. Here is the list of collected logs: *00:13:47.280* + tar -cvzf /home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/exported-artifacts/mock_varlogs.tar.gz btmp dnf.librepo.log dnf.log dnf.rpm.log faillog glusterfs hawkey.log journal lastlog libvirt openvswitch README tallylog vdsm_tests.log wtmp yum.log*00:13:47.285* btmp*00:13:47.285* dnf.librepo.log*00:13:47.299* dnf.log*00:13:47.309* dnf.rpm.log*00:13:47.310* faillog*00:13:47.311* glusterfs/*00:13:47.312* hawkey.log*00:13:47.313* journal/*00:13:47.313* lastlog*00:13:47.315* libvirt/*00:13:47.315* libvirt/qemu/*00:13:47.316* openvswitch/*00:13:47.317* openvswitch/ovs-vswitchd.log*00:13:47.318* openvswitch/ovsdb-server.log*00:13:47.319* README*00:13:47.320* tallylog*00:13:47.321* vdsm_tests.log*00:13:47.342* wtmp*00:13:47.343* yum.log*00:13:47.349* + cd /var/host_log*00:13:47.350* + tar -cvzf /home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/exported-artifacts/host_varlogs.tar.gz anaconda audit boot.log btmp chrony cloud-init.log cloud-init-output.log cron dnf.librepo.log dnf.log dnf.rpm.log firewalld glusterfs hawkey.log journal lastlog libvirt ovirt-guest-agent README samba sssd tallylog wtmp*00:13:47.356* anaconda/*00:13:47.356* anaconda/ifcfg.log*00:13:47.357* anaconda/ks-script-l5qnynnj.log*00:13:47.358* anaconda/storage.log*00:13:47.359* anaconda/program.log*00:13:47.395* anaconda/ks-script-b5_08tmo.log*00:13:47.396* anaconda/ks-script-6uks8bp3.log*00:13:47.397* anaconda/hawkey.log*00:13:47.398* anaconda/syslog*00:13:47.406* anaconda/journal.log*00:13:47.449* anaconda/dnf.librepo.log*00:13:47.458* anaconda/packaging.log*00:13:47.465* anaconda/dbus.log*00:13:47.466* anaconda/anaconda.log*00:13:47.467* anaconda/ks-script-slrcz39_.log*00:13:47.503* audit/*00:13:47.504* audit/audit.log.3*00:13:47.657* audit/audit.log.2*00:13:47.814* audit/audit.log.1*00:13:47.981* audit/audit.log*00:13:48.008* audit/audit.log.4*00:13:48.155* boot.log*00:13:48.156* btmp*00:13:48.157* chrony/*00:13:48.159* cloud-init.log*00:13:48.159* cloud-init-output.log*00:13:48.161* cron*00:13:48.162* dnf.librepo.log*00:13:49.930* dnf.log*00:13:51.335* dnf.rpm.log*00:13:51.421* firewalld*00:13:51.423* glusterfs/*00:13:51.424* hawkey.log*00:13:51.704* journal/*00:13:51.708* journal/b087148aba6d49b9bbef488e52a48752/*00:13:51.709* journal/b087148aba6d49b9bbef488e52a48752/system.journal*00:13:55.817* tar: journal/b087148aba6d49b9bbef488e52a48752/system.journal: file changed as we read it*00:13:55.819* journal/b087148aba6d49b9bbef488e52a48752/user-1000.journal*00:13:55.915* lastlog*00:13:55.923* libvirt/*00:13:55.924* libvirt/lxc/*00:13:55.926* libvirt/libxl/*00:13:55.927* libvirt/qemu/*00:13:55.928* libvirt/qemu/LiveOS-f920001d-be4e-47ea-ac26-72480fd5be87.log*00:13:55.929* libvirt/uml/*00:13:55.930* ovirt-guest-agent/*00:13:55.930* ovirt-guest-agent/ovirt-guest-agent.log*00:13:55.932* README*00:13:55.933* samba/*00:13:55.933* samba/old/*00:13:55.935* sssd/*00:13:55.935* tallylog*00:13:55.935* wtmp Most if not all are lot relevant to vdsm tests, and should not be collected. This was added in: commit 9c9c17297433e5a5a49aa19cde10b206e7db61e9 Author: Edward Haas <edwardh(a)redhat.com> Date: Tue Apr 17 10:53:11 2018 +0300 automation: Collect logs even when check-patch fails Change-Id: Idfe07ce6fc55473b1db1d7f16754f559cc5c345a Signed-off-by: Edward Haas <edwardh(a)redhat.com> Reviewed in: https://gerrit.ovirt.org/c/90370 Edward, can you explain why do we need to collect logs during check-patch, and why do we need to collect all the logs in the system? Nir

3 13

[VDSM] check-merged failing for years - remove it?
by Nir Soffer 06 Dec '18

06 Dec '18

vdsm check-merged job takes 1.5 hours, and fails 80% of the time. https://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/buildTime… Nobody checks these failures or care about them. We are abusing CI resources for no benefit. Can we remove this job? Nir

6 10

Failing OST patches
by Kaustav Majumder 04 Dec '18

04 Dec '18

Recently I have pushed 2 patches for OST[1][2], both are failing in CI. Though unrelated failures I find the errors in "add_hosts" test beacuse the host is non operation within the asserted time.I have added the link for the jenkins log [3]. [1] https://gerrit.ovirt.org/#/c/95327/ [2] https://gerrit.ovirt.org/#/c/95347/ [3] https://pastebin.com/MVpws4Et Any advice? -- KAUSTAV MAJUMDER ASSOCIATE SOFTWARE ENGINEER Red Hat India PVT LTD. <https://www.redhat.com/> kmajumder(a)redhat.com M: 08981884037 IM: IRC: kmajumder <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatway <https://twitter.com/redhatway> @redhatinc <https://instagram.com/redhatinc> @redhatsnaps <https://snapchat.com/add/redhatsnaps>

4 6

Re: Any way to make VM Hidden/Locked for access
by Pavan Chavva 04 Dec '18

04 Dec '18

+Ovirt Devel and Adelino. FYI. Best, Pavan. On Wed, Nov 28, 2018 at 8:21 AM Mahesh Falmari <Mahesh.Falmari(a)veritas.com> wrote: > Hi Nir, > > Just wanted to check if there is any way to create a VM through API and > make this VM hidden or locked so that it is not shown/accessible to the > users until we explicitly enable it again. > > The use case here is of VM recovery, where we would like to create a VM > first and wanted to check if there is any issue in VM creation and then > fail in the first phase itself before the actual data transfer takes place. > But the issue we may see here is that once VM gets created, it becomes > accessible to users who may play with it and it would impact the subsequent > recovery operations. > > > > Thanks & Regards, > Mahesh Falmari > > > -- PAVAN KUMAR CHAVVA ENGINEERING PARTNER MANAGER Red Hat pchavva(a)redhat.com M: 4793219099 IM: pchavva

3 2

[Ovirt] [CQ weekly status] [30-11-2018]
by Dafna Ron 02 Dec '18

02 Dec '18

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: RED (#1) I checked last date ovirt-engine and vdsm passed and moved packages to tested as they are the bigger projects and it was on the 27-11-218. We have been having sporadic failures for most of the projects on test check_snapshot_with_memory. We have deducted that this is caused by a code regression in storage based on the following things: 1.Evgheni and Gal helped debug this issue to rule out lago and infra issue as the cause of failure and both determined the issue is a code regression - most likely in storage. 2. The failure only happens on 4.2 branch. 3. the failure itself is cannot run a vm due to low disk space in storage domain and we cannot see any failures which would leave any leftovers in the storage domain. Dan and Ryan are actively involved in trying to find the regression but the consensus is that this is a storage related regression and* we are having a problem getting the storage team to join us in debugging the issue. * I prepared a patch to skip the test in case we cannot get cooperation from storage team and resolve this regression in the next few days: https://gerrit.ovirt.org/#/c/95889/ *CQ-Master:* YELLOW (#1) We have failures which CQ is still bisecting and until its done we cannot point to any specific failing projects. Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

7 13

otopi defaults again to python3
by Yedidyah Bar David 02 Dec '18

02 Dec '18

Hi all, As some of you might recall, some time ago we made otopi default to python3, and quickly reverted that, realizing this causes too much breakage. Now things should hopefully be more stable, and I now merged a patch to default to python3 again. Current status: engine-setup works with python3 on fedora. host-deploy works with python3 on fedora, with both engine being on el7 and on fedora. Didn't try on el7, might work as well. hosted-engine --deploy is most likely broken on fedora, but I think it was already broken. We are working on that, but it will require some more time - notably, having stuff from vdsm on python3 (if not fully porting vdsm to python3, which I understand will take even more time). If you want to use python2, you can do that with: OTOPI_PYTHON=/bin/python hosted-engine --deploy On el7, if you manually added python3 (which is not available in the base repos), things will break - use above workaround if needed. Best regards, -- Didi

2 2

[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

[VDSM] Fedora 28 support - updates
by Nir Soffer 30 Nov '18

30 Nov '18

If you want to add host running Fedora 28, you need to do few manual steps: 1. Add hosts fail to configure the firewall Do not check the "Configure filewall" checkbox Adding host will fail because engine cannot communicate with vdsm. Fix - disable the firewall on the host. $ iptables -F There is probably a better way, but I did not find it yet :-) Sandro, do we have an update about this? 2. Engine fail in Host.getCapabilties Libvirt changed the location and format of this file. This will cause Host.getCapabilties to fai, and the host will become "Unassigned" This is a new issue revealed by updating our virt-preview repo this week. Fix - install old cpu_map.xml $ wget https://raw.githubusercontent.com/libvirt/libvirt/18cab54c3a0bc72390f293006… -O /usr/share/libvirt/cpu_map.xml Engine should retry and succeed after that. 3. Sanlock fail to write to its pid file, connecting to storage fail Fix - set selinux to permissive mode $ setenforce 0 To make this persistent edit /etc/selinux/config SELINUX=permissive We have a bug for this. After that you should have a working system. Nir

5 8

List of Queries related to RHV
by Suchitra Herwadkar 29 Nov '18

29 Nov '18

Hi Nir, Pavan https://ovirt.org/develop/release-management/features/storage/incremental-b… On reading more from the article, we have some questions which we will like to discuss in the call 1. Irrespective of the underlying storage, we will always restore the data as raw. But it’s not very clear to us how the disk format conversion will be taken care of internally by RHV. 1. Conversion from raw data to qcow format will only work for disk marked to be incremental or it is not specific to that only. Would rhv stage the data before conversion to qcow2. 1. For this feature( incremental backup) to work, disks have to be marked as such. User needs to mark those disks as incrementals while creating VM, otherwise this will not work. 1. If we use incremental backups, then will there not be a backing file. Do we have to upload the entire image and then rhv would convert to qcow. What if we want to just upload just the incremental part/changes relative to some base image. Thanks Suchitra

2 1

Need help setting default value to a dropdown variable in webadmin
by Kaustav Majumder 29 Nov '18

29 Nov '18

Hi all, Have been struggling with gwt code while trying to set a default value to a list drop down if a condition is satisfied. The class I am working on is "VmDiskPopupWidget.java" . I need to set default Allocation Policy 'volumeType' as 'Preallocated'. The select dropdown is of type 'ListModelListBoxEditor<VolumeType>' Any advice. -- KAUSTAV MAJUMDER ASSOCIATE SOFTWARE ENGINEER Red Hat India PVT LTD. <https://www.redhat.com/> kmajumder(a)redhat.com M: 08981884037 IM: IRC: kmajumder <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatway <https://twitter.com/redhatway> @redhatinc <https://instagram.com/redhatinc> @redhatsnaps <https://snapchat.com/add/redhatsnaps>

1 0

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

GlusterFS rebase for oVirt 4.3
by Sandro Bonazzola 28 Nov '18

28 Nov '18

According to Sahina we dropped dependency on gluster-gnfs and it's safe to move on from the unsupported 3.12 version to a newer one 4.1 / 5.0. This is for getting an agreement on what we should require in oVirt 4.3: CentOS Storage SIG provides bot 4.1 and 5 for x86_64[1] and ppc64le[2] If I understood correctly, 5 is shipping glusterd2 which requires a significant effort to get support for while 4.1 is still on glusterd which should work with current oVirt code. Sahina, can you give directions on what we should move to? Thanks. [1] http://mirror.centos.org/centos/7/storage/x86_64/ [2] http://mirror.centos.org/altarch/7/storage/ppc64le/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

4 11

error when running VDSM build
by Nir Levy 28 Nov '18

28 Nov '18

*I am installing over * *CentOS Linux release 7.5.1804* make pylint which runs: tox -e pylint static/usr/share/vdsm/sitecustomize.py lib/vdsm lib/vdsmclient lib/yajsonrpc failed for: Problem importing module base.py: cannot import name get_node_last_lineno *./.tox/pylint/lib/python2.7/site-packages/pylint/checkers/base.py:48*: from pylint.checkers.utils import get_node_last_lineno which is located at: *./.tox/pylint-py3k/lib/python2.7/site-packages/pylint/checkers/utils.py:912:* *def get_node_last_lineno(node):* what can cause this error? Regards, *Nir.* *-----------------* *full output:* *-----------------* tox -e pylint \ static/usr/share/vdsm/sitecustomize.py \ lib/vdsm \ lib/vdsmclient \ lib/yajsonrpc \ pylint recreate: /home/root/vdsm/.tox/pylint pylint installdeps: pylint==1.8 pylint installed: astroid==1.6.5,backports.functools-lru-cache==1.5,backports.ssl-match-hostname==3.5.0.1,blivet==0.61.15.69,cffi==1.6.0,chardet==2.2.1,configobj==4.7.2,configparser==3.5.0,configshell-fb==1.1.23,coverage==4.4.1,cryptography==1.7.2,decorator==3.4.0,dnspython==1.12.0,enum34==1.1.6,ethtool==0.8,filelock==3.0.10,funcsigs==1.0.2,futures==3.2.0,gssapi==1.2.0,idna==2.4,iniparse==0.4,ioprocess==1.2.0,ipaclient==4.5.4,ipaddress==1.0.16,ipalib==4.5.4,ipaplatform==4.5.4,ipapython==4.5.4,IPy==0.75,isort==4.3.4,jwcrypto==0.4.2,kitchen==1.1.1,kmod==0.1,langtable==0.0.31,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.19,netifaces==0.10.4,ovirt-imageio-common==1.5.0,pbr==3.1.1,perf==0.1,pluggy==0.8.0,ply==3.4,policycoreutils-default-encoding==0.1,pthreading==0.1.3,py==1.7.0,pyasn1==0.1.9,pyasn1-modules==0.0.8,pycparser==2.14,pycurl==7.19.0,pygobject==3.22.0,pygpgme==0.3,pyinotify==0.9.4,pykickstart==1.99.66.18,pyliblzma==0.5.3,pylint==1.8.0,pyOpenSSL==0.13.1,pyparsing==1.5.6,pyparted==3.9,python-augeas==0.5.0,python-dateutil==2.4.2,python-ldap==2.4.15,python-linux-procfs==0.4.9,python-nss==0.16.0,python-yubico==1.2.3,pyudev==0.15,pyusb==1.0.0b1,pyxattr==0.5.1,PyYAML==3.10,qrcode==5.0.1,requests==2.6.0,rtslib-fb==2.1.63,sanlock-python==3.6.0,schedutils==0.4,seobject==0.1,sepolicy==1.1,singledispatch==3.4.0.3,six==1.10.0,slip==0.4.0,slip.dbus==0.4.0,SSSDConfig==1.16.0,subprocess32==3.2.6,targetcli-fb===2.1.fb46,toml==0.10.0,tox==2.9.1,urlgrabber==3.10,urllib3==1.10.2,urwid==1.1.1,virtualenv==16.1.0,WebOb==1.2.3,wrapt==1.10.11,yum-langpacks==0.4.2,yum-metadata-parser==1.1.4 pylint runtests: PYTHONHASHSEED='2893585131' pylint runtests: commands[0] | pylint -j0 --reports=no --score=no static/usr/share/vdsm/sitecustomize.py lib/vdsm lib/vdsmclient lib/yajsonrpc Problem importing module base.py: cannot import name get_node_last_lineno Problem importing module base.pyc: cannot import name get_node_last_lineno Problem importing module base.py: cannot import name get_node_last_lineno Problem importing module base.py: cannot import name get_node_last_lineno Problem importing module base.py: cannot import name get_node_last_lineno

3 3

[VDSM] Travis Fedora 29 first build results
by Nir Soffer 28 Nov '18

28 Nov '18

We have patches[1] for Fedora 29 build on Travis[2]. Here are initial results: - storage tests passed - virt tests passed - python 3.7 compile test failed (async is a keyword now) - python 3.6 tests skipped (need to add py37 env) - lib tests failed - network test failed - legacy nose tests failed [1] https://gerrit.ovirt.org/q/topic:dockerfile+is:open [2] https://travis-ci.org/nirs/vdsm/jobs/459969129 Nir

2 2

Hosts in Unassigned state after upgrading libvirt to 4.9
by Nir Soffer 28 Nov '18

28 Nov '18

I updated 2 Fedora 28 hosts today, getting new ovirt-master-release.rpm, which exposes new virt-preview repo providing libvirt 4.9 and qemu 3.1. After the update, connecting with engine master (built few week ago) fail with: 2018-11-26 22:07:51,702+02 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-94) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "[Errno 2] No such file or directory: '/usr/share/libvirt/cpu_map.xml'"}] Looks like contents of /usr/share/libvirt/ is different now: $ ls -1 /usr/share/libvirt/cpu_map/*.xml | head /usr/share/libvirt/cpu_map/index.xml /usr/share/libvirt/cpu_map/ppc64_POWER6.xml /usr/share/libvirt/cpu_map/ppc64_POWER7.xml /usr/share/libvirt/cpu_map/ppc64_POWER8.xml /usr/share/libvirt/cpu_map/ppc64_POWER9.xml /usr/share/libvirt/cpu_map/ppc64_POWERPC_e5500.xml /usr/share/libvirt/cpu_map/ppc64_POWERPC_e6500.xml /usr/share/libvirt/cpu_map/ppc64_vendors.xml /usr/share/libvirt/cpu_map/x86_486.xml /usr/share/libvirt/cpu_map/x86_athlon.xml Do we have a fix for this? Nir

3 7

[VDSM] New: warnings in build
by Nir Soffer 28 Nov '18

28 Nov '18

Since we moved to pytest 4.0, we have warnings summary at the end of the build. Here is example summary: *00:10:06.166* =============================== warnings summary ===============================*00:10:06.167* /home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/lib/vdsm/storage/mailbox.py:73*00:10:06.168* /home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/lib/vdsm/storage/mailbox.py:73: DeprecationWarning: fromstring() is deprecated. Use frombytes() instead.*00:10:06.171* _zeroCheck = checksum(EMPTYMAILBOX, CHECKSUM_BYTES) ... You can see complete warnings here: https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2413/cons… We have only few warnings, but they are repeated a lot. Nir

1 0

mismatch in disk size while uploading a disk in chunks using Image Transfer
by Ranjit DSouza 27 Nov '18

27 Nov '18

Hi I am trying to upload a snapshot disk in chunks. Everything seems to work fine, but observed that the actual_size after upload, is much lesser than the actual_size of the original disk. Here are the steps: 1. Take a snapshot of a vm disk and download it (using Image Transfer mechanism). Save it on the file system somewhere. This disk name is 3gbdisk. It is Raw + sparse. Resides on nfs storage. The size of this downloaded file is 3 GB. "actual_size" : "1389109248", //1 GB "alias" : "3gbdisk", "content_type" : "data", "format" : "raw", "image_id" : "8fbac55e-0c86-4c0b-911b-f5b0a6722834", "propagate_errors" : "false", "provisioned_size" : "3221225472", "shareable" : "false", "sparse" : "true", "status" : "ok", "storage_type" : "image", "total_size" : "0", "wipe_after_delete" : "false", 2. Now create a new floating disk, (raw + sparse), with provisioned_size = 3221225472, or 3 GB. This disk name is vmRestoreDisk 3. Upload to this disk using Image Transfer API, using libCurl in chunks of 128 MB. This is done in a while loop, sequentially reading portions of the file downloaded in step 1 and uploading these chunks via libcurl. I Use the Transfer URL, not proxy URL. Here is the trace of the first chunk. Note the Content-Range and Content-Length headers. Start offset = 0, end offset = 134217727 (or 128 MB) upload request for chunk, start offset: 0, end offset: 134217727 Upload Started Header:Content-Range: bytes 0-134217727/3221225472 Header:Content-Length: 3221225472 * Trying 10.210.46.215... * TCP_NODELAY set * Connected to pnm86hpch30bl15.pne.ven.veritas.com (10.210.46.215) port 54322 (#0) * ALPN, offering http/1.1 * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN, server did not agree to a protocol * Server certificate: * subject: O=pne.ven.veritas.com; CN=pnm86hpch30bl15.pne.ven.veritas.com * start date: Oct 7 08:55:24 2018 GMT * expire date: Oct 7 08:55:24 2023 GMT * issuer: C=US; O=pne.ven.veritas.com; CN=pravauto20.pne.ven.veritas.com.59289 * SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway. > PUT /images/8ebc9fa8-d322-423e-8a14-5e46ca10ed4e HTTP/1.1 Host: pnm86hpch30bl15.pne.ven.veritas.com:54322 Accept: */* Content-Length: 134217728 Expect: 100-continue * Done waiting for 100-continue * We are completely uploaded and fine * HTTP 1.0, assume close after body < HTTP/1.0 200 OK < Date: Fri, 23 Nov 2018 11:52:53 GMT < Server: WSGIServer/0.1 Python/2.7.5 < Content-Type: application/json; charset=UTF-8 < Content-Length: 0 < * Closing connection 0 http response code from curl 200 Upload Finished. Return Value: 0 4. Finalize the Image Transfer after all chunks are uploaded. Observed that the disk status goes from 'uploading via API' to finalizing to OK. 5. Do a GET call on the disk (vmRestoreDisk). "actual_size" : "134217728", //128MB "alias" : "vmRestoreDisk", "content_type" : "data", "format" : "raw", "image_id" : "3eda3df2-514a-4e78-b999-1729216b25db", "propagate_errors" : "false", "provisioned_size" : "3221225472", "shareable" : "false", "sparse" : "true", "status" : "ok", "storage_type" : "image", "total_size" : "0", "wipe_after_delete" : "false", As you can see, the actual size is just 128 MB, not 1 GB. I have attached the logs of the upload operation. I think I may be missing something, let me know in case you need further information. Thanks Ranjit

3 6

ovirt-engine has been tagged (ovirt-engine-4.2.8)
by Tal Nisan 27 Nov '18

27 Nov '18

1 0

Re: splitting tests for stdci v2
by Nir Soffer 27 Nov '18

27 Nov '18

On Mon, Nov 26, 2018 at 3:00 PM Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > Hi, > > I'm currently working on paralleling our stdci v2. > > I've already extracted 'linters' stage, more patches (and more > substages) are on the way. > > This part i.e. : > > if git diff-tree --no-commit-id --name-only -r HEAD | egrep --quiet > 'vdsm.spec.in|Makefile.am|automation' ; then > ./automation/build-artifacts.sh" > ... > > seems to be an excellent candidate for extraction to a separate substage. > > The question is - how should we proceed with tests? I can create > substage for each of: > > tox -e "tests,{storage,lib,network,virt}" > > But the original 'check-patch' combined the coverage reports into one - > we would lose that. > My long term goal is to get rid of all the ugly bash code in the makefile, and run everything via tox, but as first step I think we can split the work by running: make tests In the tests substage, instead of "make check" today. Does it change anything about coverage? Theoretically we can split also to storage/network/virt/infra jobs but I think this will consume too many resources and harm other projects sharing the slaves. > There is a possibility that we could work on something that gathers > coverage data from multiple sources (tests, OST) as a completely > separate jenkins job or smth, but that will be a bigger effort. > What do you think about it? > > Marcin > > > > >

3 3

OST: Warning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
by Yedidyah Bar David 27 Nov '18

27 Nov '18

Hi all, I noticed this warning in OST's lago log, e.g. [1]: 2018-11-27 07:32:44,684::log_utils.py::start_log_task::655::nose::INFO:: # detach_vm_network_from_host_0: [0m [0m 2018-11-27 07:32:50,360::network_utils_v4.py::<genexpr>::119::py.warnings::WARNING:: * Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal 2018-11-27 07:32:50,360::log_utils.py::end_log_task::670::nose::INFO:: # detach_vm_network_from_host_0: [32mSuccess [0m (in 0:00:05) This seems to be a result of OST:basic-suite-master/test_utils/network_utils_v4.py:get_network_attachment , which does: network = next(net for net in dc.networks_service().list() if net.name == network_name) Apparently, dc.networks_service() returns a str, not unicode. Is this normal? Expected? Should the caller (OST) convert to unicode if needed, or the SDK? If so, [2] should fix (pushed just now, check-patch should finish in an hour or so, only then we can know for sure). Adding Ondra for considering the SDK side. For reference: to debug this on my own OST machine, I did this (after running the basic suite): python import ovirtsdk4 as sdk4 engine = sdk4.Connection(url='https://%s/ovirt-engine/api' % '192.168.201.4', username='admin@internal', password='123', insecure=True, debug=True).system_service() dc = engine.data_centers_service().data_center_service(engine.data_centers_service().list(search='name={}'.format('test-dc'))[0].id) [(net.name, type(net.name)) for net in dc.networks_service().list()] Which returned: [('ovirtmgmt', <type 'str'>), ('VM Network with a very long name and \xd7\xa2\xd7\x91\xd7\xa8\xd7\x99\xd7\xaa', <type 'str'>), ('Labeled_Network', <type 'str'>), ('Migration_Net', <type 'str'>)] Best regards, [1] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11697/artifa… [2] https://gerrit.ovirt.org/95768 -- Didi

1 0

oVirt impersonation and sessions
by Anastasiya Ruzhanskaya 26 Nov '18

26 Nov '18

Hello everyone! I wanted to find out how the impersonation technique used in oVirt works? I know from libvirt developers, that oVirt opens one connection only for multiple clients. How does this work? Also I found out in source code that in ActionParameterBase class the sessionId field is marked transient but, for example, for GWT rpc message, which goes to the server and says what action will be made (shut down, pause vm) this is the only field in all sent information which says what the session is. Where is the session sent instead? There was also a field with session id in https headers, but this was related to cookie so I am not completely sure if this can help to identify the current user.

2 2

Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Nir Soffer 26 Nov '18

26 Nov '18

I have seen this issue in the recent days several times. Here are some examples: - https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console - https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… There are too issues: - No test ran, so we need to retrigger manually - Gerrit report build FAILURE instead of build ERROR I reported the second issue many times in the last 5 years, no progress yet. Nir

1 0

UI test failing on a vdsm change?
by Dan Kenigsberg 26 Nov '18

26 Nov '18

I just noticed that a vdsm change to gluster tests https://gerrit.ovirt.org/#/c/95596/ failed in the change queue, on WebDriverException in _init_browser connecting to hub https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11365/testRe… The failure is clearly unrelated to the patch; maybe one of you can explain why the test fails?

3 5

Vdsm: Failing test_no_match
by Milan Zamazal 26 Nov '18

26 Nov '18

Hi, test_no_match fails on CI most of the time (but not always) in https://gerrit.ovirt.org/95518: _____________________________ test_no_match[qcow2] _____________________________ 11:30:16 11:30:16 tmpdir = local('/var/tmp/vdsm/test_no_match_qcow2_0'), image_format = 'qcow2' 11:30:16 11:30:16 def test_no_match(tmpdir, image_format): 11:30:16 path = str(tmpdir.join('test.' + image_format)) 11:30:16 op = qemuimg.create(path, '1m', image_format) 11:30:16 op.run() 11:30:16 qemuio.write_pattern(path, image_format, pattern=2) 11:30:16 with pytest.raises(qemuio.VerificationError): 11:30:16 > qemuio.verify_pattern(path, image_format, pattern=4) 11:30:16 11:30:16 storage/qemuio_test.py:59: 11:30:16 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 11:30:16 11:30:16 path = '/var/tmp/vdsm/test_no_match_qcow2_0/test.qcow2', format = 'qcow2' 11:30:16 offset = 512, len = 1024, pattern = 4 11:30:16 11:30:16 def verify_pattern(path, format, offset=512, len=1024, pattern=5): 11:30:16 read_cmd = 'read -P %d -s 0 -l %d %d %d' % (pattern, len, offset, len) 11:30:16 cmd = ['qemu-io', '-f', format, '-c', read_cmd, path] 11:30:16 rc, out, err = commands.execCmd(cmd, raw=True) 11:30:16 if rc != 0 or err != b"": 11:30:16 > raise cmdutils.Error(cmd, rc, out, err) 11:30:16 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.0002 sec (3.756 MiB/sec and 3846.1538 ops/sec)\n' err='' 11:30:16 11:30:16 storage/qemuio.py:50: Error (Similarly for raw.) You can see the complete test run log here (or in other CI runs of the patch): https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2040/cons… It fails on both Fedora and CentOS. It may or may not be related to the fact that QEMU 2.11 is used in the failed runs. Any idea what could be wrong? Thanks, Milan

3 10

vdsm has been tagged (v4.20.44)
by Milan Zamazal 26 Nov '18

26 Nov '18

1 0

[VDSM] TestMount.testSymlinkMount failing
by Germano Veit Michel 26 Nov '18

26 Nov '18

Hi, I have seen CI failing with some "random" errors which makes submitting a series of patches a bit annoying, as some patch always fails with some error, then next run another patch fails. One of these problems is TestMount.testSymlinkMount. Looks like its getting EBUSY when doing a rmdir. So probably something still using it? =================================== FAILURES =================================== __________________________ TestMount.testSymlinkMount __________________________ args = (<storage.mount_test.TestMount testMethod=testSymlinkMount>,) kwargs = {} @wraps(f) def wrapper(*args, **kwargs): if cond: raise SkipTest(reason) > return f(*args, **kwargs) testValidation.py:274: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ testValidation.py:333: in wrapper return f(*args, **kwargs) storage/mount_test.py:167: in testSymlinkMount m.umount() /usr/lib64/python2.7/contextlib.py:35: in __exit__ self.gen.throw(type, value, traceback) testlib.py:218: in namedTemporaryDir shutil.rmtree(tmpDir) /usr/lib64/python2.7/shutil.py:261: in rmtree rmtree(fullname, ignore_errors, onerror) /usr/lib64/python2.7/shutil.py:270: in rmtree onerror(os.rmdir, path, sys.exc_info()) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ path = '/var/tmp/tmpOYMiHx/mountpoint', ignore_errors = False onerror = <function onerror at 0x7fd68afc9938> def rmtree(path, ignore_errors=False, onerror=None): """Recursively delete a directory tree. If ignore_errors is set, errors are ignored; otherwise, if onerror is set, it is called to handle the error with arguments (func, path, exc_info) where func is os.listdir, os.remove, or os.rmdir; path is the argument to that function that caused it to fail; and exc_info is a tuple returned by sys.exc_info(). If ignore_errors is false and onerror is None, an exception is raised. """ if ignore_errors: def onerror(*args): pass elif onerror is None: def onerror(*args): raise try: if os.path.islink(path): # symlinks to directories are forbidden, see bug #1669 raise OSError("Cannot call rmtree on a symbolic link") except OSError: onerror(os.path.islink, path, sys.exc_info()) # can't continue even if onerror hook returns return names = [] try: names = os.listdir(path) except os.error, err: onerror(os.listdir, path, sys.exc_info()) for name in names: fullname = os.path.join(path, name) try: mode = os.lstat(fullname).st_mode except os.error: mode = 0 if stat.S_ISDIR(mode): rmtree(fullname, ignore_errors, onerror) else: try: os.remove(fullname) except os.error, err: onerror(os.remove, fullname, sys.exc_info()) try: > os.rmdir(path) E OSError: [Errno 16] Device or resource busy: '/var/tmp/tmpOYMiHx/mountpoint' /usr/lib64/python2.7/shutil.py:268: OSError ----------------------------- Captured stderr call ----------------------------- 2018-11-07 00:41:55,518 DEBUG (MainThread) [storage.Misc.excCmd] /usr/bin/taskset --cpu-list 0-1 /sbin/mkfs.ext2 -F /var/tmp/tmpOYMiHx/backing.img (cwd None) (commands:68) 2018-11-07 00:41:55,561 DEBUG (MainThread) [storage.Misc.excCmd] SUCCESS: <err> = 'mke2fs 1.44.2 (14-May-2018)\n'; <rc> = 0 (commands:89) 2018-11-07 00:41:55,562 INFO (MainThread) [storage.Mount] mounting /var/tmp/tmpOYMiHx/link_to_image at /var/tmp/tmpOYMiHx/mountpoint (mount:204) 2018-11-07 00:41:55,563 DEBUG (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 /usr/bin/mount -o loop /var/tmp/tmpOYMiHx/link_to_image /var/tmp/tmpOYMiHx/mountpoint (cwd None) (commands:68) 2018-11-07 00:41:55,598 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (commands:89) 2018-11-07 00:41:55,599 DEBUG (MainThread) [storage.Mount] /var/tmp/tmpOYMiHx/mountpoint mounted: 0.03 seconds (utils:454) 2018-11-07 00:41:55,599 DEBUG (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 /sbin/udevadm settle --timeout=5 (cwd None) (commands:68) 2018-11-07 00:41:55,624 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (commands:89) 2018-11-07 00:41:55,625 DEBUG (MainThread) [storage.Mount] Waiting for udev mount events: 0.03 seconds (utils:454) 2018-11-07 00:41:55,628 INFO (MainThread) [storage.Mount] unmounting /var/tmp/tmpOYMiHx/mountpoint (mount:212) 2018-11-07 00:41:55,629 DEBUG (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 /usr/bin/umount /var/tmp/tmpOYMiHx/mountpoint (cwd None) (commands:68) 2018-11-07 00:41:55,658 DEBUG (MainThread) [root] FAILED: <err> = 'umount: /var/tmp/tmpOYMiHx/mountpoint: target is busy.\n'; <rc> = 32 (commands:89) Full logs here: https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/1811/arti…

2 5

OST fails: python2-pbr requires git-core
by Yedidyah Bar David 25 Nov '18

25 Nov '18

Hi all, https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… fails with: 11:04:30 + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins cronie 11:04:30 Error: Package: python2-pbr-4.2.0-2.el7.noarch (alocalsync) 11:04:30 Requires: git-core 11:04:30 + ret=1 Any idea? Thanks and best regards, -- Didi

2 4

OST: Cannot attach Storage. Storage Domain format V4 is illegal
by Yedidyah Bar David 25 Nov '18

25 Nov '18

Hi all, OST manual job [1] failed for me, with what seems to me like a bug [2], unrelated to the patches I used in it: 002_bootstrap.add_master_storage_domain (from nosetests) Error Message Fault reason is "Operation Failed". Fault detail is "[Cannot attach Storage. Storage Domain format V4 is illegal.]". HTTP response code is 409. Any idea? Retriggering, for now. Best regards, [1] https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… [2] https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… -- Didi

1 1

unittest2pytes - Convert unittest test-cases to pytest
by Nir Soffer 24 Nov '18

24 Nov '18

I tried this tool on tests/storage/merge_test.py, and it save the uninteresting work of replacing assertXXX methods with asserts and pytest.raises. See https://gerrit.ovirt.org/c/95703 - mostly written by the tool. This can save lot of time converting legacy tests. Get it from https://pypi.org/project/unittest2pytest/ Nir

1 0

[Ovirt] [CQ weekly status] [23-11-2018]
by Dafna Ron 23 Nov '18

23 Nov '18

Hi, This mail is to provide the *current *status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. CQ ovirt-4.2 - YELLOW (#1) e CQ ovirt-Master - RED (#1) - *Project failing* - ovirt-engine - *First job reported*: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267 - *root cause*: https://gerrit.ovirt.org/#/c/95169/ ansible: Remove duplication of vnc_tls option - *Revert for change*: https://gerrit.ovirt.org/95666 - Tomasz Baranski is working on testing and fixing the change. There is a long queue of changes waiting to be tested and the revert patch is in queue. Once revert is tested the jobs for ovirt-engine, unless any other regressions were introduced, project should start to pass. Happy week! Dafna ------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

vdsm-client: Adding a new verb to vdsm
by Kaustav Majumder 23 Nov '18

23 Nov '18

Hi all, I was working on adding a new verb to vdsm-gluster [1]. But right now the only way i see to test this is by using vdsm-client.I have patched a host running vdsm with my code, but the vdsm-client is not showing the required verb. Is there anything else needed to be done? Eg-vdsm-client --gluster-enabled GlusterVolume globalOptionsList [1] https://gerrit.ovirt.org/#/c/95636/ Thanks, Kaustav

4 3

[ OST Failure Report ] [ oVirt Master (ovirt-engone) ] [ 21-11-2018 ] [ check_update_host ]
by Dafna Ron 23 Nov '18

23 Nov '18

Hi, We have a failure in ovirt-master in basic suite for test check_update_host. Link and headline of suspected patches: ansible: Remove duplication of vnc_tls option - https://gerrit.ovirt.org/#/c/95169/ Link to Job: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267 Link to all logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267/artifa… (Relevant) error snippet from the log: <error> [dron@dron post-002_bootstrap.py]$ egrep 89d99b74-fa6c-4d1d-a261-fb7ca7fcada2 lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log 2018-11-21 13:41:34,209-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 9ms 2018-11-21 13:41:34,224-05 INFO [org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckCommand] (default task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command: HostUpgradeCheckCommand internal: false. Entities affected : ID: ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDSAction group EDIT_HOST_CONFIGURATION with role type ADMIN 2018-11-21 13:41:34,259-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 13ms 2018-11-21 13:41:34,273-05 INFO [org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckInternalCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command: HostUpgradeCheckInternalCommand internal: true. Entities affected : ID: ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDS 2018-11-21 13:41:34,277-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 4ms 2018-11-21 13:41:34,281-05 DEBUG [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Inventory hosts: [lago-basic-suite-master-host-0] 2018-11-21 13:41:34,282-05 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Executing Ansible command: ANSIBLE_STDOUT_CALLBACK=hostupgradeplugin [/usr/bin/ansible-playbook, --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config, --check, --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa, --inventory=/tmp/ansible-inventory2326258642232337463, /usr/share/ovirt-engine/playbooks/ovirt-host-upgrade.yml] [Logfile: null] 2018-11-21 13:41:37,610-05 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Ansible playbook command has exited with value: 2 2018-11-21 13:41:37,611-05 ERROR [org.ovirt.engine.core.bll.host.HostUpgradeManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to run check-update of host 'lago-basic-suite-master-host-0'. 2018-11-21 13:41:37,611-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to check if updates are available for host 'lago-basic-suite-master-host-0' with error message 'Failed to run check-update of host 'lago-basic-suite-master-host-0'.' 2018-11-21 13:41:37,616-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] EVENT_ID: HOST_AVAILABLE_UPDATES_FAILED(839), Failed to check for available updates on host lago-basic-suite-master-host-0 with message 'Failed to run check-update of host 'lago-basic-suite-master-host-0'.'. [dron@dron post-002_bootstrap.py]$ </error>

5 9

Fwd: [ovirt-users] FOSDEM‘19 Virtualization & IaaS Devroom CfP
by Piotr Kliczewski 22 Nov '18

22 Nov '18

A friendly reminder that Cfp is due by 1st of December. Please submit your proposal using: https://penta.fosdem.org/submission/FOSDEM19 ---------- Forwarded message --------- From: Piotr Kliczewski <pkliczew(a)redhat.com> Date: Tue, Oct 16, 2018 at 9:32 AM Subject: [ovirt-users] FOSDEM‘19 Virtualization & IaaS Devroom CfP To: users <users(a)ovirt.org> Cc: Doron Fediuck <doron(a)redhat.com> 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> https://penta.fosdem.org/submission/FOSDEM19 [2] iaas-virt-devroom at lists.fosdem.org <https://lists.fosdem.org/listinfo/fosdem> [3] bkp at redhat.com <https://lists.fosdem.org/listinfo/fosdem>

1 0

tracking usage of deprecated 'commands.execCmd' in VDSM
by Marcin Sobczyk 22 Nov '18

22 Nov '18

Hi, usage of 'commands.execCmd' stands in our way to be Python 3-compatible. I've made a report of files that refer to it across the project: https://gerrit.ovirt.org/95635 I think it would be a good idea to have that list to track the removal progress. Regards, Marcin

2 1

[ACTION REQUIRED] Compose for oVirt 4.3.0 beta (alpha?)
by Sandro Bonazzola 22 Nov '18

22 Nov '18

Hi, I started preparing repository for beta (or alpha if beta release criteria are not satisfied) Please add the builds you want included in the release configuration files. I already started filling the configuration files, if your package is already there, please check if the versions and the shipped builds are correct and fix if not. Reference gerrit project is: https://gerrit.ovirt.org/#/admin/projects/releng-tools for release notes automatic generation: milestones/ovirt-4.3.0.conf for adding builds to the repository: releases/ovirt-4.3.0_beta1.conf documentation: releases/README-prepare-patches 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>

1 0

Fwd: Error Message in basic-suite-master: segmentation fault during host-deply
by Galit Rosenthal 22 Nov '18

22 Nov '18

Hi, I have a problem with basic-suite-master with host deploy Who can help solve this issue? Thanks, Galit check patch [3] is failing on : Basic suite master fails when using packages from new repository used, it might be related to the new 7.6 packages[1]: Error Message: 2018-11-21 08:20:52,005-05 ERROR [org.ovirt.engine.core.uutils.ssh.SSHDialog] (EE-ManagedThreadFactory-engine-Thread-2) [b85560f] SSH error running command root@lago-basic-suite-master-host-1:'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 --warning=no-timestamp -C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True': RuntimeException: Unexpected error during execution: bash: line 1: 1374 Segmentation fault "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True Host Deploy fails on segmentation fault [2]: [1] http://mirror.centos.org/centos/7/cr/x86_64/ [2] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/2331/… [3] gerrit: https://gerrit.ovirt.org/#/c/95570/ -- GALIT ROSENTHAL SOFTWARE ENGINEER Red Hat <https://www.redhat.com/> galit(a)gmail.com T: 972-9-7692230 <https://red.ht/sig>

2 1

screenshots for all UI patches / UXD reviewer update
by Greg Sheremeta 21 Nov '18

21 Nov '18

Hi all, Just as a refresher and for anyone new -- please be sure to add screenshots of your admin portal patches to your gerrit commit in the form of an imgur.com link in the commit message. Additionally, Laura Wright is now handling most of our UI look and feel review duties. She is quickly becoming an oVirt UI expert :) so please continue to add her on your UI patches so she can +1 the designs. It's especially important to have her review English strings, too. So if you were previously adding Liz Blanchard (Liz is still around but focusing on kubevirt), you can now add Laura instead. Generally, maintainers should avoid merging patches that touch the UI until Laura has +1'd. Please let me know if you have any questions! 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>

1 0

Failures on master CQ effecting all projects - (missing packages}
by Dafna Ron 21 Nov '18

21 Nov '18

Hi, We have a failure in upgrade suite on add_host due to missing packages required by qemu-kv, I am working on debugging and fixing the issue and will update once its resolved. Please note that since its effecting add_host all projects are effected. Jira logged: https://ovirt-jira.atlassian.net/browse/OVIRT-2581 Thanks Dafna

5 11

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

21 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

ovirt-engine has been tagged (ovirt-engine-4.3.0_alpha)
by Tal Nisan 20 Nov '18

20 Nov '18

1 0

vdsm has been tagged (v4.30.3)
by Milan Zamazal 20 Nov '18

20 Nov '18

1 0

[QA][Automation] Maintainer needed for basic-suite-master compatibility test suite
by Sandro Bonazzola 19 Nov '18

19 Nov '18

Hi, Milan Zamal who previously was monitoring the automated test and helping fixing issues related to it has no more capacity for continue with this task[1]. We are now looking for someone to help monitoring the test results and help handling its failures when running it with different cluster levels. [1] https://gerrit.ovirt.org/#/c/95515/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

CentOS Virt SIG - (at least) one volunteer needed
by Sandro Bonazzola 19 Nov '18

19 Nov '18

Hi, with Christmas holidays coming the CentOS Virt SIG will have both me and Tomasz Baranski not available in case of urgent issues. I'd like to ask for a volunteer from a region where there's no Christmas holiday (Israel comes to my mind) for covering during our absence and future similar absences. Documentation for joining the SIG is here: https://wiki.centos.org/SIGGuide You can contact me directly if you want to candidate yourself. Being a Fedora packager is a nice to have, it will ease working with the SIG build system and with the packaging tasks. 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>

2 2

Getting info about qemu guest agent into the engine
by Tomasz Barański 19 Nov '18

19 Nov '18

Hello, wise people! As a part of BZ1615830[1] I want to add information about qemu guest agent to engine's DB. I have some trouble figuring out some details. 1. VDSM seems to be using QGA, but it does not report any information about it. Am I right? I only found a mention about it in `xml` field in JSON returned by `VM.getInfo` (and `Host.getVMFullList`): a `virtio` channel as documented in libvirt. 2. How does the engine puts data into `vm_dynamic` table? I can't find any usage for `InsertVmDynamic` procedure. 3. Also, it's not clear to me how (whether?) the engine consumes output of VM.getInfo/Host.getVMFullList. Any pointers to relevant code appreciated. Tomo [1] https://bugzilla.redhat.com/show_bug.cgi?id=1615830

4 5

Re: [ovirt-users] Re: Engine ISO Uploader - SSL Peer Not Trusted
by Sandro Bonazzola 19 Nov '18

19 Nov '18

Moving to devel mailing list. Il giorno dom 18 nov 2018 alle ore 11:17 Yedidyah Bar David <didi(a)redhat.com> ha scritto: > On Sat, Nov 17, 2018 at 6:32 PM, Shawn Weeks <sweeks(a)weeksconsulting.us> > wrote: > > The only issue with the UI is I’m on VPN so uploading from my local > machine > > would be extremely slow. I discovered the –insecure flag for the cli and > > that seems to have worked. > > Please note that we intend to deprecate this tool. Please try the api/sdk > as suggested by Nir and tell us if you have any comments/issues etc. > Thanks. > > Actually I thought we already deprecated it in 4.2, but I now searched and > can't find anything like [1][2] (which was for the image uploader) or a > note > in the release notes [3]. Adding Sandro. Is it too late now to deprecate > in 4.2 (so that we can remove in 4.3)? > Tal, are we removing ISO domains in 4.3? If yes we need to deprecate the iso uploader in 4.2 so we can remove it in 4.3, if not we need to keep it in 4.3 since the web ui doesn't upload to iso domain (AFAIK). > > See also [4][5], which are for RHV. > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1306637 > [2] https://www.ovirt.org/release/4.0.0/#ovirt-image-uploader > [3] https://ovirt.org/release/4.2.0/ > [4] https://bugzilla.redhat.com/show_bug.cgi?id=1579119 > [5] > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… > > Thanks and best regards, > > > > > > > > > Thanks > > > > Shawnk > > > > > > > > From: Nir Soffer <nsoffer(a)redhat.com> > > Sent: Saturday, November 17, 2018 8:43 AM > > To: Shawn Weeks <sweeks(a)weeksconsulting.us> > > Cc: users <users(a)ovirt.org>; Daniel Erez <derez(a)redhat.com> > > Subject: Re: [ovirt-users] Engine ISO Uploader - SSL Peer Not Trusted > > > > > > > > On Sat, Nov 17, 2018, 02:45 Shawn Weeks <sweeks(a)weeksconsulting.us > wrote: > > > > Trying to upload an iso using engine-iso-uploader on a hosted-engine > > instance and I’m getting an SSL Error. I followed the directions at > > https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL/ to > setup > > SSL and am able to login to the Admin console without an issue. Also > checked > > that things like curl recognize the CA correctly. Not sure where > > engine-iso-uploader is getting it’s trust store. > > > > > > > > [root@cloud ~]# engine-iso-uploader list > > > > Please provide the REST API password for the admin@internal oVirt Engine > > user (CTRL+D to abort): > > > > ERROR: Unable to connect to REST API at > > https://cloud.dev.example.com:443/ovirt-engine/api due to SDK error > > > > Message: Error while sending HTTP request: (60, "Peer's certificate > issuer > > has been marked as not trusted by the user.") > > > > > > > > What am I missing? > > > > > > > > If you ate using 4.2, you can upload iso files to data domains. You can > > upload directly from the UI: > > > > > > > > 1. Open storage > disks > > > > 2. Click Upload > Start > > > > 3. Select file and fill in the form > > > > > > > > For faster upload or automation, you can use the SDK. See this example > code: > > > > > > > > > https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_d… > > > > > > > > With some configuration changes you can use this as command line tool for > > uploading iso or other images. > > > > > > > > Nir > > > > > > > > > > _______________________________________________ > > 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/MHEE6MQR2PFKP… > > > > > > -- > Didi > -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

[ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 15-11-2018 ] [ check_snapshot_with_memory ]
by Dafna Ron 18 Nov '18

18 Nov '18

Hi, we have a failure on basic suite for test check_snapshot_with. _memory. I am actually not seeing any reason the patch would cause that specific issue but its consistently failing on this change. I am seeing a vm memory saved to the iscsi domain but aside from that nothing is failing before tto cause a cleanup issue or create low space on the storage). can some one please take a look to see if anything in the patch is causing this? Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/95436/1 - webadmin: network operation in progress - sync host interfaces Link to Job: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/ Link to all logs: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/artifact/b… (Relevant) error snippet from the log: <error> 2018-11-15 08:19:33,409-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method: runVdsCommand, params: [IsVmDuringInitiating , IsVmDuringInitiatingVDSCommandParameters:{vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}], timeElapsed: 1ms 2018-11-15 08:19:33,430-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM vm0 due to a failed validation: [Cannot run VM. Low disk space on Storage Domain iscsi.] (User: admin@internal-authz). 2018-11-15 08:19:33,430-05 WARN [org.ovirt.engine.core.bll.RunVmCommand] (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Validation of action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__ ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_DISK_SPACE_LOW_ON_STORAGE_DOMAIN,$storageName iscsi 2018-11-15 08:19:33,431-05 INFO [org.ovirt.engine.core.bll.RunVmCommand] (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Lock freed to object 'EngineLock:{exclusiveLocks='[9144eb88-8f0a-4e77-9d70-3b761e 48ecb4=VM]', sharedLocks=''}' 2018-11-15 08:19:33,438-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method: runAction, params: [RunVm, RunVmParams:{comm andId='69628467-56d3-4d93-aed1-a2807b7dbc45', user='null', commandType='Unknown', vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}], timeElapsed: 115ms 2018-11-15 08:19:33,441-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-5) [] Operation Failed: [Cannot run VM. Low disk space on Storage Domain iscsi.] 2018-11-15 08:19:34,044-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-25) [] START, GetAllVmStatsVDSCommand(HostName = lago-basic-su ite-4-2-host-0, VdsIdVDSCommandParametersBase:{hostId='063dfef9-bc9d-44c3-8ba3-8142e3eb129c'}), log id: 65651e2b 2018-11-15 08:19:34,045-05 DEBUG [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message] (EE-ManagedThreadFactory-engineScheduled-Thread-25) [] SEND destination:jms.topic.vdsm_requests reply-to:jms.topic.vdsm_responses content-length:103 </error>

4 5

Proposing Fred Rolland as a Storage backend maintainer
by Tal Nisan 18 Nov '18

18 Nov '18

Hi everyone, I'd like to propose Fred as a backend maintainer in Engine for the storage area. Fred has been contributing to ovirt-engine for the last 3.5 years and have done tremendous job in adding new features, bug fixes and code review. Thanks, Tal.

6 5

[vdsm] illegible check-patch failure
by Dan Kenigsberg 18 Nov '18

18 Nov '18

This job https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/1965/cons… fails on 06:46:24 journal/b087148aba6d49b9bbef488e52a48752/system.journal 06:46:27 tar: journal/b087148aba6d49b9bbef488e52a48752/system.journal: file changed as we read it (I think). Is that true? How can this be avoided?

2 1

[BACKUP] Estimating qcow2 disk image size before upload
by Nir Soffer 17 Nov '18

17 Nov '18

When uploading to qcow2 disks on block storage you must set the disk initial_size correctly so the system allocates big enough disk. If the initial size is too small, the upload will fail when trying to write after the end of the device. This info can be useful for people working on a backup solution for oVirt. The easiest case is upload of existing qcow2 image using the SDK. In this case we create a new disk with: initial_size=image_size, provisioned_size=virtual_size, image_size is the size of the file: os.stat('image').st_size Note that "qemu-img info" return "actual-size" - this is the allocated size on storage which is not helpful for uploading images. Example: https://github.com/oVirt/ovirt-engine-sdk/blob/78c3d5bd14eeb93ef72ec31d775f… A more tricky case is when a backup system keeps raw guest data, but know how to generate qcow2 image stream, without creating a temporary image. In this case the required size can be calculated by counting the number of clusters that need to be allocated in the final image. This depends on the location of the data in the image. For example this creates 1G image with only one cluster: $ python -c 'with open("one-cluster.raw", "wb") as f: f.truncate(1024**3) f.write("x")' $ ls -lhs one-cluster.raw 4.0K -rw-rw-r--. 1 nsoffer nsoffer 1.0G Nov 15 18:24 one-cluster.raw $ qemu-img measure -f raw -O qcow2 one-cluster.raw required size: 458752 fully allocated size: 1074135040 $ qemu-img convert -f raw -O qcow2 one-cluster.raw one-cluster.qcow2 $ ls -lhs one-cluster.qcow2 324K -rw-r--r--. 1 nsoffer nsoffer 384K Nov 15 18:25 one-cluster.qcow2 But this creates a fully allocated 1G image: $ python -c 'with open("fully-allocated.raw", "wb") as f: f.truncate(1024**3) for i in range(0, 1024**3, 64 * 1024): f.seek(i) f.write("x")' $ ls -lhs fully-allocated.raw 64M -rw-rw-r--. 1 nsoffer nsoffer 1.0G Nov 15 18:30 fully-allocated.raw $ qemu-img measure -f raw -O qcow2 fully-allocated.raw required size: 1074135040 fully allocated size: 1074135040 $ qemu-img convert -f raw -O qcow2 fully-allocated.raw fully-allocated.qcow2 $ ls -lhs fully-allocated.qcow2 1.1G -rw-r--r--. 1 nsoffer nsoffer 1.1G Nov 15 18:31 fully-allocated.qcow2 We had code in vdsm that does exactly this, and it was removed since qemu-img support a new "measure" command in RHEL 7.5 providing this info. But this works only for existing images. You can find the code in this vdsm commit: https://github.com/oVirt/vdsm/tree/4eee97d6aa532b6f3ecdfde0333d17c27c412f86 The module implementing estimation: https://github.com/oVirt/vdsm/blob/4eee97d6aa532b6f3ecdfde0333d17c27c412f86… The tests for this module: https://github.com/oVirt/vdsm/blob/4eee97d6aa532b6f3ecdfde0333d17c27c412f86… If you know the data ranges that will be written to the qcow2 image, you can count the clusters like this: https://github.com/oVirt/vdsm/blob/4eee97d6aa532b6f3ecdfde0333d17c27c412f86… Then you can use the cluster count to estimate qcow2 file size: https://github.com/oVirt/vdsm/blob/4eee97d6aa532b6f3ecdfde0333d17c27c412f86… Nir

2 3

[Ovirt] [CQ weekly status] [16-11-2018]
by Dafna Ron 16 Nov '18

16 Nov '18

Hi All, I want to just give a quick and simple status on CQ so that everyone is informed on the general state of our tests when they come in on beginning of the week. *Ovirt-Master*- *GREEN* *Ovirt-4.2* - *GREEN* Happy Week! Dafna

1 0

Setting Type and action Variables in Ovirt Validation messages
by Kaustav Majumder 16 Nov '18

16 Nov '18

Hi all, I am working on a bug where the error messages comes as non interpolated [ https://bugzilla.redhat.com/show_bug.cgi?id=1369319].I am trying to figure out where the 'type' and 'action' variables are set in ovirt for validation error messages One such example from AppErrors.properties is :- ACTION_TYPE_FAILED_GENERATOR_NOT_SUPPORTED_BY_CLUSTER=Cannot ${action} ${type}. The random number generator is not supported by the Cluster. Thanks, Kaustav

2 1

Re: [EXTERNAL] Re: List of Queries related to RHV
by Nir Soffer 15 Nov '18

15 Nov '18

On Wed, Oct 17, 2018 at 5:03 PM 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. > Right, this is only for internal use. ... > *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? > Arik, can you answer this? Regarding backup, I think you need to store the vm configuration at the time of the backup regardless of having a version or not. The amount of data is very small. > *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? > Using the UI you can use qcow2 format only for thin disks on block storage. Using the SDK you can also create qcow2 image on thin file based storage. You can see examples here: https://github.com/oVirt/ovirt-engine-sdk/blob/78c3d5bd14eeb93ef72ec31d775f… In 4.3 we plan to support qcow2 image format for both thin and preallocated disks to allow change block tracking for incremental backup. See html: https://github.com/oVirt/ovirt-site/blob/bc51f4a7867d9c7e3797da6da1d19e111c… > > > *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. > I don't know about any stats from users, but the general idea is: - one engine - 1 or more DCs - 1 or more storage domains in a DC - 1 or more clusters per DCs - 1 or more hosts per cluster The theoretical limit is 2000 hosts per DC (limited by sanlock), but the practical limit is much lower. I don't think we have setups with more than 200 hosts. Martin, do you have more info on this? > *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. > > This is much more complicated to calculate. > But from our observations this takes roughly 1.5 times. > > It sounds like a reasonable speed up. Can RHVM server requests in parallel, > > Yes > if so are there any settings that need to be tweaked? > > We don't have any settings related to concurrency. > 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. > > 1.5 seconds for reading 1024 bytes? > [Mahesh] Seeking response to this query. > > The throughout you will get depends on many things: - are you communicating with the proxy (using proxy_url) or the daemon (transfer_url)? Accessing the daemon directly will be faster. - are you running on the same host as the daemon performing the transfer? - if you run on the same host, are you using unix socket? (15% improvement expected) - are you using the same connection per thread for entire transfer (huge improvement when doing small requests) - which version are you testing? we support keep alive connections only since 1.4.x. - are you using big enough requests? you will get best performance if you use one big request per thread - network bandwidth - storage speed For best throughput when downloading single disk, you should use multiple threads, each downloading one part of an image, but I'm not sure it worth the time to optimize this since backup are expected the run in the same time anyway, and you will quickly reach the storage limit while downloading disks for multiple vms on multiple hosts in the same time. I suggest testing the expected use case, not single download. > *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? > snapshots are always consistent if you have qemu guest agent installed, and the guest is using the guest agent scripts properly. Without the guest agent, or if it is not configured properly, file system will have to recover after restore, in the same way it recovers after power failure. To be able to resume a vm to the same state when the snapshot was done you need to include memory in the snapshot, but this make the snapshot much slower, depending on the amount of guest memory, and require huge amount of space, so I don't think it makes sense for backup. Regarding REST API, Arik can add more info about this. Nir

4 5

[CQ ovirt master] [ovirt-engine] - not passing for 10 days
by Ehud Yonasi 15 Nov '18

15 Nov '18

Hey, I've seen that CQ Master is not passing ovirt-engine for 10 days and fails on test suite called restore_vm0_networking here's a snap error regarding it: https://pastebin.com/7msEYqKT Link to a sample job with the error: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11113/artifac… Can some1 have a look at it and help to resolve the issue?

8 29

Unassigned bugs for targeted releases
by Sandro Bonazzola 14 Nov '18

14 Nov '18

Hi, we have 32 bugs targeted to a release but without an assignee: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… Can you please review the list and ensure someone will work on them or drop the target if they're not going to be worked on? 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>

3 3

Proposing Shmuel Melamud as a Virt backend maintainer
by Michal Skrivanek 14 Nov '18

14 Nov '18

Hi all, I’d like to propose Shmuel as a backend maintainer for the virt area. He’s a good candidate with his 200+ patches and insight into complex parts of VM pools, templates, q35 support, v2v, sparsify... Feel free to bother him more with review requests;) Thanks, michal

7 6

Please Stop merging to ovirt-engine master branch
by Dafna Ron 14 Nov '18

14 Nov '18

Hi , Please stop merging to ovirt-engine master branch as we have been failing on different regressions for the last 11 days. I do not want any other regressions to be introduced until we can properly catch them which means we need to fix the current issues before merging more changes. Thanks, Dafna

3 4

vdsm has been tagged (v4.30.2)
by Milan Zamazal 14 Nov '18

14 Nov '18

1 0

VDSM-Gluster python 3 compatibility
by Kaustav Majumder 14 Nov '18

14 Nov '18

Hi all, I have been working on making vdsm-gluster python 3 compatible. I had some queries regarding the tool used for getting storage devices info. Till now vdsm uses python blivet for getting the device tree information. I am not sure if blivet is compatible with python 3 so I had two propositions which I want some advice on. 1) Using lsblk and parsing the output 2) Using ansible modules locally in the vdsm hosts. Although I feel the 2nd way will add more dependencies to the project but it can help us in the long run to add more functionality easily. Thanks, Kaustav

2 2

Re: [CentOS-devel] SIGs: Possibility to drop EOL content at 7.6.1810 release time
by Sandro Bonazzola 13 Nov '18

13 Nov '18

Il giorno ven 2 nov 2018 alle ore 12:33 Niels de Vos <ndevos(a)redhat.com> ha scritto: > On Thu, Nov 01, 2018 at 11:01:51AM +0200, Anssi Johansson wrote: > ... > > For reference and inspiration, here are some directories from > > mirror.centos.org, including both up-to-date content and potentially EOL > > content. SIGs should review the list to make sure these directories can > > be copied over to 7.6.1810 when that time comes. Making the decisions > > now would save a bit of time at 7.6.1810 release time. > > > .. > > > storage/x86_64/gluster-3.10 > > storage/x86_64/gluster-3.12 > > The above two can be dropped (also for CentOS 6). This includes the > centos-release-gluster310 and centos-release-gluster-312 packages in > Extras. > > Can we keep 3.12? It's still consumed by oVirt 4.2. Adding oVirt devel team, just in case we'll need urgently to rebase on newer Gluster on CentOS 7.6 GA or block upgrade to CentOS 7.6 from oVirt side till we figure out how to handle. > > storage/x86_64/gluster-4.0 > > storage/x86_64/gluster-4.1 > > storage/x86_64/gluster-5 > > These three are still maintained. > > Thanks, > Niels > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

3 6

Upstream package missing release suffix
by Ales Musil 13 Nov '18

13 Nov '18

Hello, ovirt-lldp-labeler is missing release suffix in nightly build [1]. This has been fixed some time ago in [2]. Any idea what could be wrong? Thank you. Regards, Ales. [1] https://plain.resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/ [2] https://gerrit.ovirt.org/c/94616/ -- ALES MUSIL Associate Software Engineer - rhv network Red Hat EMEA <https://www.redhat.com/> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

2 1

[VDSM] Proposing Denis as vdsm gluster maintainer
by Nir Soffer 13 Nov '18

13 Nov '18

Hi all, Denis is practically maintaining vdsm gluster code in the recent years, and it is time to make this official. Please ack, Nir

7 6

ovirt-engine has been tagged (ovirt-engine-4.2.7.5 )
by Tal Nisan 12 Nov '18

12 Nov '18

1 0

[ACTION REQUIRED] oVirt 4.3.0 Beta preparations
by Sandro Bonazzola 12 Nov '18

12 Nov '18

Hi, we'd like to be ready for releasing a first oVirt 4.3.0 beta on November 26th. In order to do that, we need all packages to be ready for it by Sunday November 25th. Maintainers: please ensure your packages can be installed are feature complete with regards to ovirt-4.3.0 target and passed CI testing. An integration testing on the master nightly will be done manually on Friday November 23rd to ensure basic functionalities are working as expected. Please note we don't have any guarantee that CentOS 7.6 will be out by that time. Please check oVirt 4.3 Beta release criteria[1] and help getting ready for it. If you have something that should block the beta release please raise the issue as soon as possible. Thanks, [1] https://www.ovirt.org/develop/release-management/releases/4.3/release-manag… -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

3 4

amount of reports by abrt
by Piotr Kliczewski 11 Nov '18

11 Nov '18

I attended a talk about abrt and noticed there are good number of reports [1] generated by issues in ovirt. Thanks, Piotr [1] https://retrace.fedoraproject.org/faf/reports/

3 4

ovirt-engine external IDP (Keycloak) integration
by Ravi Shankar Nori 08 Nov '18

08 Nov '18

Hi All, Please find design document [1] for integrating ovirt-engine with Keycloak using mod_auth_openidc. Engine can be configured to use external IDP to handle user authentication while still supporting Rest API bearer authentication. There are some changes to how clients will obtain tokens to use for bearer authentication. All clients need to request tokens from the external IDP and use it to access engine. When external authentication is enabled admin@internal and all internal profiles for authentication are disabled. Please see the design document for more details. Thanks Ravi [1] https://docs.google.com/document/d/1Wio7bQNeNinx7Luj5t-KpsSYQ2Z1Y0I8UhUyJAZ… Integration Issues that need attention 1. Ovirt-engine Python, Java and Ruby SDKs need to be modified to obtain token from either engine SSO or external OpenID Connect IDP. 2. OVN if we are not using SDK needs to be modified to obtain token from either engine SSO or external OpenID Connect IDP. 3. OVN changes needed to config user admin@internal. admin@internal access will be disabled if external integration is enabled. So OVN needs to be configurable to use another user for REST API access. 4. Ansible is using SDK, if SDK is fixed to use a file the file needs to passed from ansible to SDK. 5. Cloudforms and Satellite are using Ruby SDK, we need to file a bug to fix the issue. The file with the details of external IDP URL and client-id and client-secret needs to be passed to SDK. 6. REST API SDK V3 is not going to work with password and negotiate authentication 7. VM Single Sign-on will not work as we don’t have a password. 8. VM Console needs to work, if VM console is using token and bearer authentication everything should work

3 3

Failing compilation of engine to RPM using build-artefacts.sh
by Andrej Krejcir 08 Nov '18

08 Nov '18

Hi, I use a VM with latest CentOS to compile engine to RPM. Steps: - git clone repo from my dev machine to the VM - run ovirt-engine/automation/build-artifacts.sh This used to work, but since about 2 weeks ago the build fails with an error message: + %py_byte_compile /usr/bin/python2 /root/rpmbuild/BUILDROOT/ovirt-engine-4.3.0-0.0.master.20181105130924.git58423b7.el7.x86_64/usr/share/ovirt-engine/ /var/tmp/rpm-tmp.f7B35C: line 82: fg: no job control error: Bad exit status from /var/tmp/rpm-tmp.f7B35C (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.f7B35C (%install) Attaching the whole build log and the file '/var/tmp/rpm-tmp.f7B35C'. I'm not sure how to fix this. Can anyone help? Thanks, Andrej

2 1

Fwd: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 719 - Still Failing!
by Eitan Raviv 07 Nov '18

07 Nov '18

Hi, We have a failure on OST/network-suite-master for several days now. My suspicions of the cause are detailed below. Can you have a look? Thanks ---------- Forwarded message --------- From: Eitan Raviv <eraviv(a)redhat.com> Date: Mon, Nov 5, 2018 at 8:39 AM Subject: Re: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 719 - Still Failing! To: Ori Liel <oliel(a)redhat.com> Hi, Can you have a look? Thanks On Thu, Nov 1, 2018 at 10:08 AM Eitan Raviv <eraviv(a)redhat.com> wrote: > Hi Ondra, > > We have above failure on OST network-suite-4.2 [1] due to: > Fault reason is "Request syntactically incorrect.". Fault detail is "For > correct usage, see: > https://192.168.201.4/ovirt-engine/apidoc#services/vm/methods/preview_snaps… > " > > and I see in engine.log [2]: > > javax.xml.bind.UnmarshalException: unexpected element (uri:"", local:"disks") > > at the same time I see in model_4.2 [3] that a change was done to add the disks, but if i am not mistaken the ovirt-engine-sdk pom.xml [4] was not bumped to reflect this change. > > Can you please check? > > Thanks > > [1] > https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/719/arti… > [2] > https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/717/arti… > [3] > https://gerrit.ovirt.org/#/q/project:ovirt-engine-api-model+branch:model_4.2 > [4] https://gerrit.ovirt.org/#/q/project:ovirt-engine-sdk+branch:sdk_4.2 > > > > ---------- Forwarded message --------- > From: Edward Haas <edwardh(a)redhat.com> > Date: Thu, Nov 1, 2018 at 8:35 AM > Subject: Fwd: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build > # 719 - Still Failing! > To: <rhevm-network-staff(a)redhat.com> > > > FYI > > ---------- Forwarded message --------- > From: <jenkins(a)jenkins.phx.ovirt.org> > Date: Thu, Nov 1, 2018 at 6:02 AM > Subject: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # > 719 - Still Failing! > To: <lgoldber(a)redhat.com>, <edwardh(a)redhat.com>, <infra(a)ovirt.org> > > > Project: > http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ > Build: > http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/719/ > Build Number: 719 > Build Status: Still Failing > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #717 > [Marcin Sobczyk] Change logging level for 'schema.inconsistency' > > > Changes for Build #718 > [Ales Musil] master: Update master suite compatibility version > > > Changes for Build #719 > [Ales Musil] master: Update master suite compatibility version > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: > network-suite-4.2.tests.test_mac_pools.test_undo_preview_snapshot_when_mac_used_reassigns_a_new_mac > > Error Message: > Error: Fault reason is "Request syntactically incorrect.". Fault detail is > "For correct usage, see: > https://192.168.201.4/ovirt-engine/apidoc#services/vm/methods/preview_snaps…". > HTTP response code is 400. > > Stack Trace: > system = <lib.system.SDKSystemRoot object at 0x7fc7f91f48d0> > default_cluster = <lib.clusterlib.Cluster object at 0x7fc7f91f4bd0> > ovirtmgmt_vnic_profile = <lib.netlib.VnicProfile object at 0x7fc7f81b3710> > cirros_template = 'Cirros_0_4_0' > > def test_undo_preview_snapshot_when_mac_used_reassigns_a_new_mac( > system, default_cluster, ovirtmgmt_vnic_profile, > cirros_template): > with virtlib.vm_pool(system, size=2) as (vm_0, vm_1): > vm_0.create(vm_name=VM0, > cluster=default_cluster, > template=cirros_template) > vm_0.wait_for_down_status() > > vm_0.run() > vm_0.wait_for_up_status() > > nicless_snapshot = _create_snapshot(vm_0) > > vm_0.create_vnic(NIC_NAME_1, ovirtmgmt_vnic_profile, > MAC_ADDR_1) > vm_0.stop() > vm_0.wait_for_down_status() > > > nicless_snapshot.preview() > > network-suite-4.2/tests/test_mac_pools.py:124: > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ _ _ > network-suite-4.2/lib/virtlib.py:243: in preview > snapshot=self.get_sdk_type() > /usr/lib64/python2.7/site-packages/ovirtsdk4/services.py:31091: in > preview_snapshot > return self._internal_action(action, 'previewsnapshot', None, headers, > query, wait) > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:299: in > _internal_action > return future.wait() if wait else future > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:55: in wait > return self._code(response) > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:296: in callback > self._check_fault(response) > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:132: in > _check_fault > self._raise_error(response, body) > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ _ _ > > response = <ovirtsdk4.http.Response object at 0x7fc7f81b3350> > detail = <ovirtsdk4.types.Fault object at 0x7fc7f81b39d0> > > @staticmethod > def _raise_error(response, detail=None): > """ > Creates and raises an error containing the details of the > given HTTP > response and fault. > > This method is intended for internal use by other components > of the > SDK. Refrain from using it directly, as backwards > compatibility isn't > guaranteed. > """ > fault = detail if isinstance(detail, types.Fault) else None > > msg = '' > if fault: > if fault.reason: > if msg: > msg += ' ' > msg = msg + 'Fault reason is "%s".' % fault.reason > if fault.detail: > if msg: > msg += ' ' > msg = msg + 'Fault detail is "%s".' % fault.detail > if response: > if response.code: > if msg: > msg += ' ' > msg = msg + 'HTTP response code is %s.' % response.code > if response.message: > if msg: > msg += ' ' > msg = msg + 'HTTP response message is "%s".' % > response.message > > if isinstance(detail, six.string_types): > if msg: > msg += ' ' > msg = msg + detail + '.' > > class_ = Error > if response is not None: > if response.code in [401, 403]: > class_ = AuthError > elif response.code == 404: > class_ = NotFoundError > > error = class_(msg) > error.code = response.code if response else None > error.fault = fault > > raise error > E Error: Fault reason is "Request syntactically incorrect.". Fault > detail is "For correct usage, see: > https://192.168.201.4/ovirt-engine/apidoc#services/vm/methods/preview_snaps…". > HTTP response code is 400. > > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:118: Error >

4 7

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-11-2018 ] [ 002_bootstrap.add_dc ]
by Dafna Ron 06 Nov '18

06 Nov '18

Hi, We failed to add a DC due to computability level in the upgrade suite. The upgrade suite is upgrading 4.2 to master. Eli, can you please check if any fix is needed for upgrade? Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/95190/ - engine: Remove Cluster Levels 3.6 and 4.0 Link to Job: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10975 Link to all logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10975/artifa… (Relevant) error snippet from the log: <error> 2018-11-04 06:26:54,619-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [1d8362d9] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '192.168.201.1' using session 'v2y73+8hVB7ccwgjlAQOAK539eW6UsAysQQHbbiSy+mGDSTjOyZ38bpl9XLrGXSLJAqKyeXSdqfrbAqB4qWZUA==' logged in. 2018-11-04 06:26:54,873-05 WARN [org.ovirt.engine.core.bll.storage.pool.AddEmptyStoragePoolCommand] (default task-1) [4b627395-5dd6-4211-a63e-d78f3728ec6f] Validation of action 'AddEmptyStoragePool' failed for user admin@internal-authz. Reasons: VAR__TYPE__STORAGE__POOL,VAR__ACTION__CREATE,ACTION_TYPE_FAILED_GIVEN_VERSION_NOT_SUPPORTED 2018-11-04 06:26:54,877-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Cannot create Data Center. Selected Compatibility Version is not supported. </error>

2 2

Fwd: [CentOS-devel] Point-release Freeze is Active
by Sandro Bonazzola 02 Nov '18

02 Nov '18

FYI. This shouldn't affect directly oVirt 4.2.7 but further updates to oVIrt deps will need to wait till CentOS 7.6 will be out. ---------- Forwarded message --------- From: Brian Stinson <brian(a)bstinson.com> Date: gio 1 nov 2018 alle ore 16:29 Subject: [CentOS-devel] Point-release Freeze is Active To: <centos-devel(a)centos.org> Hi Folks, As is usual, we freeze the SIG Sign + Push process as part of preparing for a point release. This helps us once CR is ready (it isn't yet, though) so that we can seed it quickly in CBS to build against. The Point-release Freeze does not affect content moving from the testing tags in CBS to buildlogs.c.o, that will continue to show up as it is built. Do note: since we do want to give testers and developers an opportunity to build and test against an upcoming point-release before it goes GA, content coming from buildlogs.centos.org may require enabling the CR repo once it's ready. Any new requests for sign+push (adding new tags to mirror.c.o) during Point-release Freeze will be held until the point release goes GA. If there are any questions, please let us know and discuss here on the list. Cheers! -- Brian Stinson _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org https://lists.centos.org/mailman/listinfo/centos-devel -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

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