May 2018 - Devel - oVirt List Archives

[VDSM] travis tests fail consistently since Apr 14
by Nir Soffer 12 Jun '18

12 Jun '18

There are several issues: 1. coverage fail after this patch: https://github.com/oVirt/vdsm/commit/6b905c2c134bcf344961d28eefbd05f2838d2e… https://travis-ci.org/oVirt/vdsm/builds/366574414 ... pwd /vdsm/tests ls .cov* ls: cannot access .cov*: No such file or directory make[1]: *** [check] Error 2 make[1]: Leaving directory `/vdsm/tests' 2. pywatch_test - gdb not installed We need to add gdb and install install python-debuginfo package on the test images. self = <pywatch_test.TestPyWatch object at 0x2bbc0d0> def test_timeout(self): rc, out, err = exec_cmd(['./py-watch', '0.1', 'sleep', '10']) assert b'Watched process timed out' in out > assert rc == 128 + signal.SIGTERM E assert 1 == (128 + 15) E + where 15 = signal.SIGTERM pywatch_test.py:45: AssertionError ------------------------------ Captured log call ------------------------------- cmdutils.py 151 DEBUG ./py-watch 0.1 sleep 10 (cwd None) cmdutils.py 159 DEBUG FAILED: <err> = 'Traceback (most recent call last):\n File "./py-watch", line 59, in <module>\n dump_trace(watched_proc)\n File "./py-watch", line 32, in dump_trace\n \'thread apply all py-bt\'])\n File "/usr/lib64/python2.7/site-packages/subprocess32.py", line 575, in call\n p = Popen(*popenargs, **kwargs)\n File "/usr/lib64/python2.7/site-packages/subprocess32.py", line 822, in __init__\n restore_signals, start_new_session)\n File "/usr/lib64/python2.7/site-packages/subprocess32.py", line 1567, in _execute_child\n raise child_exception_type(errno_num, err_msg)\nOSError: [Errno 2] No such file or directory: \'gdb\'\n'; <rc> = 1 Nir

8 15

[Fedora][Engine] Hystrix going to be orphaned in Fedora
by Sandro Bonazzola 08 Jun '18

08 Jun '18

FESCo approved an updated policy for packages which fail to build from source during mass rebuilds (FTBFS). The updated policy is still at https://fedoraproject.org/ wiki/Fails_to_build_from_source. Highlights: - packages which FTBFS are subject to orphaning if there is no maintainer acknowledgement within 8 weeks - packages which FTBFS in two consecutive mass rebuilds will be retired soon after the second mass rebuild Focusing on Hystrix, it has been reported failing on 2018-03-14, more than 10 weeks ago and it's failing to build since Fedora 26, totalling 3 consecutive mass rebuild failures. This put Hystrix in a candidate position for being orphaned. The Hystrix package is used by oVirt Engine. The POM requires version 1.4.14 (released this on 6 Aug 2015) . Fedora 24 and CentOS Virt SIG has 1.4.21 (released this on 17 Nov 2015). Latest upstream version is 1.5.13. Since in oVirt 4.3 we're aiming to support Fedora 28 we need to decide on what to do with Hystrix: - drop it as dependency? - update to latest? - try to fix build failure and keep current version? Roman, current maintainer (in cc) is unresponsive, not replying to my needinfo since 2017-08-17 Any volunteer for taking over? -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

2 6

Propose Milan Zamazal as virt maintainer
by Francesco Romani 04 Jun '18

04 Jun '18

Hi all, Milan Zamazal has been working on the oVirt project for more than 2.5 years. Let me highlight some of his many contributions to the project: - Since January this year - 2018, he's been a maintainer for the stable branches. - He developed important features like memory hotunplug, which required tight cooperation and communication with the other layers of the stack (libvirt, qemu). - He is a mentor in the Outreachy program, which lead to creation of the oVirt Log Analyzer: https://github.com/mz-pdm/ovirt-log-analyzer - He contributed more than 290 patches to the Vdsm project in master branch alone, excluding backports and contributions to Engine - He contributed and is contributing testcases and fixes to the oVirt System Test suite, a tool which was already pivotal in ensuring the quality of the oVirt project. As reviewer, Milan is responsive and his comments are always comprehensive and well focused, with strong attitude towards getting things done and done right. Milan also demonstrated his ability to adapt to the needs of the project: - he demonstrated careful and thoughtful patch management while maintaining the stable branches - he also demonstrated he's not shy to tackle large and needed changes during the 4.1 and 4.2 cycles, when we deeply reorganized the XML processing in the virt code. For those reasons, and many more, I think he will be a good addition to the maintainers team, and I propose him as virt co-maintainer. Please share your thoughts Bests, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

6 5

[ OST Failure Report ] [ hc-basic-suite-4.2 ] [30-05-2018 ] [ 002_bootstrap.add_hosts ]
by Gal Ben Haim 01 Jun '18

01 Jun '18

Hi, 4.2 Hyper-converged suite is failing on "add_hosts" test (host 1 deployment failed). Link to Job: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… Link to all logs: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… (Relevant) error snippet from the host deploy log: <error> 2018-05-30 05:30:09,706-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE misc METHOD otopi.plugins.ovirt_host_deploy.hosted-engine.configureha.Plugin._set_ha_conf (None) 2018-05-30 05:30:09,713-0400 ERROR otopi.plugins.ovirt_host_deploy.hosted-engine.configureha configureha._set_ha_conf:114 HA client was not imported 2018-05-30 05:30:09,713-0400 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/tmp/ovirt-lQCcc6VFAV/pythonlib/otopi/context.py", line 133, in _executeMethod method['method']() File "/tmp/ovirt-lQCcc6VFAV/otopi-plugins/ovirt-host-deploy/hosted-engine/configureha.py", line 116, in _set_ha_conf _('Cannot resolve ovirt_hosted_engine_ha module') RuntimeError: Cannot resolve ovirt_hosted_engine_ha module <error> -- *GAL bEN HAIM* RHV DEVOPS

3 3

I want to Translate Ovirt To Chinese
by 唐朝 01 Jun '18

01 Jun '18

Hi: I am a software engineer in China. Chinese is my native language. I prefer to Ovirt than Openstack.Your jobs is very prefessional. Best wishes!

2 1

ovirt-engine-cli | SDK 3 | oVirt 4.3
by Sandro Bonazzola 31 May '18

31 May '18

Hi, Bug 1399709 <https://bugzilla.redhat.com/show_bug.cgi?id=1399709> - [RFE] Deprecate and remove the ovirt-shell tool Stated: "The ovirt-shell is deprecated since version 4.0 of the oVirt, and it will be removed in version 4.2 of oVirt, together with version 3 of the API." and is currently targeted to 4.4. Integration team is in the process to move Jenkins jobs to fedora 28 and I'd like to understand if I need to include ovirt-engine-sdk 3 and ovirt-engine-cli into fedora 28 or not. Right now, ovirt-engine-cli is required by ovirt-engine so if we want to drop it, we need to remove the dependency in ovirt-engine. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

post-merge CI triggering from GitHub
by Barak Korren 31 May '18

31 May '18

Its broken right now, we're investigating the issue. Tracker ticket: https://ovirt-jira.atlassian.net/browse/OVIRT-2071 Thanks Tomas Golembiovsky for reporting! -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 1

Re: [ovirt-devel] dynamic ownership changes
by Michal Skrivanek 31 May '18

31 May '18

--Apple-Mail=_82B55436-9E61-4F82-AF39-6B64C656C187 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Elad, why did you install vdsm-hook-allocate_net? adding Dan as I think the hook is not supposed to fail this badly in any = case Thanks, michal > On 5 May 2018, at 19:22, Elad Ben Aharon <ebenahar(a)redhat.com> wrote: >=20 > Start VM fails on: >=20 > 2018-05-05 17:53:27,399+0300 INFO (vm/e6ce66ce) [virt.vm] = (vmId=3D'e6ce66ce-852f-48c5-9997-5d2959432a27') drive 'vda' path: = 'dev=3D/rhev/data-center/mnt/blockSD/db5a6696-d907-4938-9a78-bdd13a843c62/= images/6cdabfe5-=20 > d1ca-40af-ae63-9834f235d1c8/7ef97445-30e6-4435-8425-f35a01928211' -> = u'*dev=3D/rhev/data-center/mnt/blockSD/db5a6696-d907-4938-9a78-bdd13a843c6= 2/images/6cdabfe5-d1ca-40af-ae63-9834f235d1c8/7ef97445-30e6-4435-8425-=20= > f35a01928211' (storagexml:334)=20 > 2018-05-05 17:53:27,888+0300 INFO (jsonrpc/1) [vdsm.api] START = getSpmStatus(spUUID=3D'940fe6f3-b0c6-4d0c-a921-198e7819c1cc', = options=3DNone) from=3D::ffff:10.35.161.127,53512, = task_id=3Dc70ace39-dbfe-4f5c-ae49-a1e3a82c=20 > 2758 (api:46)=20 > 2018-05-05 17:53:27,909+0300 INFO (vm/e6ce66ce) [root] = /usr/libexec/vdsm/hooks/before_device_create/10_allocate_net: rc=3D2 = err=3Dvm net allocation hook: [unexpected error]: Traceback (most recent = call last):=20 > File "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", = line 105, in <module>=20 > main()=20 > File "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", = line 93, in main=20 > allocate_random_network(device_xml)=20 > File "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", = line 62, in allocate_random_network=20 > net =3D _get_random_network()=20 > File "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", = line 50, in _get_random_network=20 > available_nets =3D _parse_nets()=20 > File "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", = line 46, in _parse_nets=20 > return [net for net in os.environ[AVAIL_NETS_KEY].split()]=20 > File "/usr/lib64/python2.7/UserDict.py", line 23, in __getitem__=20 > raise KeyError(key)=20 > KeyError: 'equivnets'=20 >=20 >=20 > (hooks:110)=20 > 2018-05-05 17:53:27,915+0300 ERROR (vm/e6ce66ce) [virt.vm] = (vmId=3D'e6ce66ce-852f-48c5-9997-5d2959432a27') The vm start process = failed (vm:943)=20 > Traceback (most recent call last):=20 > File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 872, in = _startUnderlyingVm=20 > self._run()=20 > File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2861, = in _run=20 > domxml =3D hooks.before_vm_start(self._buildDomainXML(),=20 > File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2254, = in _buildDomainXML=20 > dom, self.id <http://self.id/>, self._custom['custom'])=20 > File = "/usr/lib/python2.7/site-packages/vdsm/virt/domxml_preprocess.py", line = 240, in replace_device_xml_with_hooks_xml=20 > dev_custom)=20 > File "/usr/lib/python2.7/site-packages/vdsm/common/hooks.py", line = 134, in before_device_create=20 > params=3DcustomProperties)=20 > File "/usr/lib/python2.7/site-packages/vdsm/common/hooks.py", line = 120, in _runHooksDir=20 > raise exception.HookError(err)=20 > HookError: Hook Error: ('vm net allocation hook: [unexpected error]: = Traceback (most recent call last):\n File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line = 105, in <module>\n main()\n > File "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", = line 93, in main\n allocate_random_network(device_xml)\n File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 62, = i > n allocate_random_network\n net =3D _get_random_network()\n File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 50, = in _get_random_network\n available_nets =3D _parse_nets()\n File = "/us > r/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 46, = in _parse_nets\n return [net for net in = os.environ[AVAIL_NETS_KEY].split()]\n File = "/usr/lib64/python2.7/UserDict.py", line 23, in __getit > em__\n raise KeyError(key)\nKeyError: \'equivnets\'\n\n\n',) >=20 >=20 >=20 > Hence, the success rate was 28% against 100% running with d/s (d/s). = If needed, I'll compare against the latest master, but I think you get = the picture with d/s. >=20 > vdsm-4.20.27-3.gitfee7810.el7.centos.x86_64=20 > libvirt-3.9.0-14.el7_5.3.x86_64=20 > qemu-kvm-rhev-2.10.0-21.el7_5.2.x86_64=20 > kernel 3.10.0-862.el7.x86_64 > rhel7.5 >=20 >=20 > Logs attached >=20 > On Sat, May 5, 2018 at 1:26 PM, Elad Ben Aharon <ebenahar(a)redhat.com = <mailto:ebenahar@redhat.com>> wrote: > nvm, found gluster 3.12 repo, managed to install vdsm >=20 > On Sat, May 5, 2018 at 1:12 PM, Elad Ben Aharon <ebenahar(a)redhat.com = <mailto:ebenahar@redhat.com>> wrote: > No, vdsm requires it: >=20 > Error: Package: vdsm-4.20.27-3.gitfee7810.el7.centos.x86_64 = (/vdsm-4.20.27-3.gitfee7810.el7.centos.x86_64)=20 > Requires: glusterfs-fuse >=3D 3.12=20 > Installed: glusterfs-fuse-3.8.4-54.8.el7.x86_64 (@rhv-4.2.3) >=20 > Therefore, vdsm package installation is skipped upon force install. >=20 > On Sat, May 5, 2018 at 11:42 AM, Michal Skrivanek = <michal.skrivanek(a)redhat.com <mailto:michal.skrivanek@redhat.com>> = wrote: >=20 >=20 >> On 5 May 2018, at 00:38, Elad Ben Aharon <ebenahar(a)redhat.com = <mailto:ebenahar@redhat.com>> wrote: >>=20 >> Hi guys,=20 >>=20 >> The vdsm build from the patch requires glusterfs-fuse > 3.12. This is = while the latest 4.2.3-5 d/s build requires 3.8.4 (3.4.0.59rhs-1.el7) >=20 > because it is still oVirt, not a downstream build. We can=E2=80=99t = really do downstream builds with unmerged changes:/ >=20 >> Trying to get this gluster-fuse build, so far no luck. >> Is this requirement intentional?=20 >=20 > it should work regardless, I guess you can force install it without = the dependency >=20 >>=20 >> On Fri, May 4, 2018 at 2:38 PM, Michal Skrivanek = <michal.skrivanek(a)redhat.com <mailto:michal.skrivanek@redhat.com>> = wrote: >> Hi Elad, >> to make it easier to compare, Martin backported the change to 4.2 so = it is actually comparable with a run without that patch. Would you = please try that out?=20 >> It would be best to have 4.2 upstream and this[1] run to really = minimize the noise. >>=20 >> Thanks, >> michal >>=20 >> [1] = http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-on-demand-el7-x86_64= /28/ = <http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-on-demand-el7-x86_6= 4/28/> >>=20 >>> On 27 Apr 2018, at 09:23, Martin Polednik <mpolednik(a)redhat.com = <mailto:mpolednik@redhat.com>> wrote: >>>=20 >>> On 24/04/18 00:37 +0300, Elad Ben Aharon wrote: >>>> I will update with the results of the next tier1 execution on = latest 4.2.3 >>>=20 >>> That isn't master but old branch though. Could you run it against >>> *current* VDSM master? >>>=20 >>>> On Mon, Apr 23, 2018 at 3:56 PM, Martin Polednik = <mpolednik(a)redhat.com <mailto:mpolednik@redhat.com>> >>>> wrote: >>>>=20 >>>>> On 23/04/18 01:23 +0300, Elad Ben Aharon wrote: >>>>>=20 >>>>>> Hi, I've triggered another execution [1] due to some issues I saw = in the >>>>>> first which are not related to the patch. >>>>>>=20 >>>>>> The success rate is 78% which is low comparing to tier1 = executions with >>>>>> code from downstream builds (95-100% success rates) [2]. >>>>>>=20 >>>>>=20 >>>>> Could you run the current master (without the dynamic_ownership = patch) >>>>> so that we have viable comparision? >>>>>=20 >>>>> =46rom what I could see so far, there is an issue with move and = copy >>>>>> operations to and from Gluster domains. For example [3]. >>>>>>=20 >>>>>> The logs are attached. >>>>>>=20 >>>>>>=20 >>>>>> [1] >>>>>> *https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv = <https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv> >>>>>> -4.2-ge-runner-tier1-after-upgrade/7/testReport/ >>>>>> <https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv = <https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv> >>>>>> -4.2-ge-runner-tier1-after-upgrade/7/testReport/>* >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> [2] >>>>>> https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ = <https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/> >>>>>>=20 >>>>>> rhv-4.2-ge-runner-tier1-after-upgrade/7/ >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> [3] >>>>>> 2018-04-22 13:06:28,316+0300 INFO (jsonrpc/7) [vdsm.api] FINISH >>>>>> deleteImage error=3DImage does not exist in domain: >>>>>> 'image=3Dcabb8846-7a4b-4244-9835-5f603e682f33, >>>>>> domain=3De5fd29c8-52ba-467e-be09-ca40ff054dd4' >>>>>> from=3D: >>>>>> :ffff:10.35.161.182,40936, = flow_id=3Ddisks_syncAction_ba6b2630-5976-4935, >>>>>> task_id=3D3d5f2a8a-881c-409e-93e9-aaa643c10e42 (api:51) >>>>>> 2018-04-22 13:06:28,317+0300 ERROR (jsonrpc/7) = [storage.TaskManager.Task] >>>>>> (Task=3D'3d5f2a8a-881c-409e-93e9-aaa643c10e42') Unexpected error = (task:875) >>>>>> Traceback (most recent call last): >>>>>> File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", = line 882, >>>>>> in >>>>>> _run >>>>>> return fn(*args, **kargs) >>>>>> File "<string>", line 2, in deleteImage >>>>>> File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line = 49, in >>>>>> method >>>>>> ret =3D func(*args, **kwargs) >>>>>> File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line = 1503, >>>>>> in >>>>>> deleteImage >>>>>> raise se.ImageDoesNotExistInSD(imgUUID, sdUUID) >>>>>> ImageDoesNotExistInSD: Image does not exist in domain: >>>>>> 'image=3Dcabb8846-7a4b-4244-9835-5f603e682f33, >>>>>> domain=3De5fd29c8-52ba-467e-be09-ca40ff054dd4' >>>>>>=20 >>>>>> 2018-04-22 13:06:28,317+0300 INFO (jsonrpc/7) = [storage.TaskManager.Task] >>>>>> (Task=3D'3d5f2a8a-881c-409e-93e9-aaa643c10e42') aborting: Task is = aborted: >>>>>> "Image does not exist in domain: 'image=3Dcabb8846-7a4b-4244-9835- >>>>>> 5f603e682f33, domain=3De5fd29c8-52ba-467e-be09-ca40ff054dd4'" - = code 268 >>>>>> (task:1181) >>>>>> 2018-04-22 13:06:28,318+0300 ERROR (jsonrpc/7) = [storage.Dispatcher] FINISH >>>>>> deleteImage error=3DImage does not exist in domain: >>>>>> 'image=3Dcabb8846-7a4b-4244-9835-5f603e682f33, >>>>>> domain=3De5fd29c8-52ba-467e-be09 >>>>>> -ca40ff054d >>>>>> d4' (dispatcher:82) >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On Thu, Apr 19, 2018 at 5:34 PM, Elad Ben Aharon = <ebenahar(a)redhat.com <mailto:ebenahar@redhat.com>> >>>>>> wrote: >>>>>>=20 >>>>>> Triggered a sanity tier1 execution [1] using [2], which covers = all the >>>>>>> requested areas, on iSCSI, NFS and Gluster. >>>>>>> I'll update with the results. >>>>>>>=20 >>>>>>> [1] >>>>>>> https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/4.2 = <https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/4.2> >>>>>>> _dev/job/rhv-4.2-ge-flow-storage/1161/ >>>>>>>=20 >>>>>>> [2] >>>>>>> https://gerrit.ovirt.org/#/c/89830/ = <https://gerrit.ovirt.org/#/c/89830/> >>>>>>> vdsm-4.30.0-291.git77aef9a.el7.x86_64 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> On Thu, Apr 19, 2018 at 3:07 PM, Martin Polednik = <mpolednik(a)redhat.com <mailto:mpolednik@redhat.com>> >>>>>>> wrote: >>>>>>>=20 >>>>>>> On 19/04/18 14:54 +0300, Elad Ben Aharon wrote: >>>>>>>>=20 >>>>>>>> Hi Martin, >>>>>>>>>=20 >>>>>>>>> I see [1] requires a rebase, can you please take care? >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>> Should be rebased. >>>>>>>>=20 >>>>>>>> At the moment, our automation is stable only on iSCSI, NFS, = Gluster and >>>>>>>>=20 >>>>>>>>> FC. >>>>>>>>> Ceph is not supported and Cinder will be stabilized soon, = AFAIR, it's >>>>>>>>> not >>>>>>>>> stable enough at the moment. >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>> That is still pretty good. >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> [1] https://gerrit.ovirt.org/#/c/89830/ = <https://gerrit.ovirt.org/#/c/89830/> >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Thanks >>>>>>>>>=20 >>>>>>>>> On Wed, Apr 18, 2018 at 2:17 PM, Martin Polednik = <mpolednik(a)redhat.com <mailto:mpolednik@redhat.com> >>>>>>>>> > >>>>>>>>> wrote: >>>>>>>>>=20 >>>>>>>>> On 18/04/18 11:37 +0300, Elad Ben Aharon wrote: >>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> Hi, sorry if I misunderstood, I waited for more input = regarding what >>>>>>>>>>=20 >>>>>>>>>>> areas >>>>>>>>>>> have to be tested here. >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> I'd say that you have quite a bit of freedom in this regard. >>>>>>>>>> GlusterFS >>>>>>>>>> should be covered by Dennis, so iSCSI/NFS/ceph/cinder with = some suite >>>>>>>>>> that covers basic operations (start & stop VM, migrate it), = snapshots >>>>>>>>>> and merging them, and whatever else would be important for = storage >>>>>>>>>> sanity. >>>>>>>>>>=20 >>>>>>>>>> mpolednik >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> On Wed, Apr 18, 2018 at 11:16 AM, Martin Polednik < >>>>>>>>>> mpolednik(a)redhat.com <mailto:mpolednik@redhat.com> >>>>>>>>>> > >>>>>>>>>>=20 >>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>> On 11/04/18 16:52 +0300, Elad Ben Aharon wrote: >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>>> We can test this on iSCSI, NFS and GlusterFS. As for ceph = and >>>>>>>>>>>> cinder, >>>>>>>>>>>>=20 >>>>>>>>>>>> will >>>>>>>>>>>>> have to check, since usually, we don't execute our = automation on >>>>>>>>>>>>> them. >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Any update on this? I believe the gluster tests were = successful, >>>>>>>>>>>>> OST >>>>>>>>>>>>>=20 >>>>>>>>>>>> passes fine and unit tests pass fine, that makes the = storage >>>>>>>>>>>> backends >>>>>>>>>>>> test the last required piece. >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> On Wed, Apr 11, 2018 at 4:38 PM, Raz Tamir = <ratamir(a)redhat.com <mailto:ratamir@redhat.com>> >>>>>>>>>>>> wrote: >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> +Elad >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> On Wed, Apr 11, 2018 at 4:28 PM, Dan Kenigsberg = <danken(a)redhat.com <mailto:danken@redhat.com> >>>>>>>>>>>>>> > >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> On Wed, Apr 11, 2018 at 12:34 PM, Nir Soffer = <nsoffer(a)redhat.com <mailto:nsoffer@redhat.com>> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> On Wed, Apr 11, 2018 at 12:31 PM Eyal Edri = <eedri(a)redhat.com <mailto:eedri@redhat.com>> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Please make sure to run as much OST suites on this patch = as >>>>>>>>>>>>>>>> possible >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> before merging ( using 'ci please build' ) >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> But note that OST is not a way to verify the patch. >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> Such changes require testing with all storage types we = support. >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> Nir >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> On Tue, Apr 10, 2018 at 4:09 PM, Martin Polednik < >>>>>>>>>>>>>>>> mpolednik(a)redhat.com <mailto:mpolednik@redhat.com> >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> Hey, >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> I've created a patch[0] that is finally able to = activate >>>>>>>>>>>>>>>>>> libvirt's >>>>>>>>>>>>>>>>>> dynamic_ownership for VDSM while not negatively = affecting >>>>>>>>>>>>>>>>>> functionality of our storage code. >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> That of course comes with quite a bit of code = removal, mostly >>>>>>>>>>>>>>>>>> in >>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>> area of host devices, hwrng and anything that touches = devices; >>>>>>>>>>>>>>>>>> bunch >>>>>>>>>>>>>>>>>> of test changes and one XML generation caveat = (storage is >>>>>>>>>>>>>>>>>> handled >>>>>>>>>>>>>>>>>> by >>>>>>>>>>>>>>>>>> VDSM, therefore disk relabelling needs to be disabled = on the >>>>>>>>>>>>>>>>>> VDSM >>>>>>>>>>>>>>>>>> level). >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> Because of the scope of the patch, I welcome >>>>>>>>>>>>>>>>>> storage/virt/network >>>>>>>>>>>>>>>>>> people to review the code and consider the = implication this >>>>>>>>>>>>>>>>>> change >>>>>>>>>>>>>>>>>> has >>>>>>>>>>>>>>>>>> on current/future features. >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> [0] https://gerrit.ovirt.org/#/c/89830/ = <https://gerrit.ovirt.org/#/c/89830/> >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> In particular: dynamic_ownership was set to 0 = prehistorically >>>>>>>>>>>>>>>>>> (as >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> part >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> of https://bugzilla.redhat.com/show_bug.cgi?id=3D554961 = <https://bugzilla.redhat.com/show_bug.cgi?id=3D554961> ) because >>>>>>>>>>>>>>> libvirt, >>>>>>>>>>>>>>> running as root, was not able to play properly with = root-squash >>>>>>>>>>>>>>> nfs >>>>>>>>>>>>>>> mounts. >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Have you attempted this use case? >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> I join to Nir's request to run this with storage QE. >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Raz Tamir >>>>>>>>>>>>>> Manager, RHV QE >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>=20 >>>>>=20 >>>>>=20 >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org <mailto:Devel@ovirt.org> >>> http://lists.ovirt.org/mailman/listinfo/devel = <http://lists.ovirt.org/mailman/listinfo/devel> >>>=20 >>>=20 >>=20 >>=20 >=20 >=20 >=20 >=20 > <logs.tar.gz> --Apple-Mail=_82B55436-9E61-4F82-AF39-6B64C656C187 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi = Elad,<div class=3D"">why did you install = vdsm-hook-allocate_net?</div><div class=3D""><br class=3D""></div><div = class=3D"">adding Dan as I think the hook is not supposed to fail this = badly in any case</div><div class=3D""><br class=3D""></div><div = class=3D"">Thanks,</div><div class=3D"">michal<br class=3D""><div><br = class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On 5 May = 2018, at 19:22, Elad Ben Aharon <<a href=3D"mailto:ebenahar@redhat.com"= class=3D"">ebenahar(a)redhat.com</a>> wrote:</div><br = class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" = class=3D"">Start VM fails on:<div class=3D""><br class=3D""></div><div = class=3D""><span style=3D"font-family:monospace" class=3D""><span = style=3D"background-color: rgb(255, 255, 255);" class=3D"">2018-05-05 = 17:53:27,399+0300 INFO  (vm/e6ce66ce) [virt.vm] = (vmId=3D'e6ce66ce-852f-48c5-9997-5d2959432a27') drive 'vda' path: = 'dev=3D/rhev/data-center/mnt/blockSD/db5a6696-d907-4938-9a78-bdd13a843c62/= images/6cdabfe5- </span><br = class=3D"">d1ca-40af-ae63-9834f235d1c8/7ef97445-30e6-4435-8425-f35a0192821= 1' -> = u'*dev=3D/rhev/data-center/mnt/blockSD/db5a6696-d907-4938-9a78-bdd13a843c6= 2/images/6cdabfe5-d1ca-40af-ae63-9834f235d1c8/7ef97445-30e6-4435-8425- = <br class=3D"">f35a01928211' (storagexml:334) <br class=3D"">2018-05-05 = 17:53:27,888+0300 INFO  (jsonrpc/1) [vdsm.api] START = getSpmStatus(spUUID=3D'940fe6f3-b0c6-4d0c-a921-198e7819c1cc', = options=3DNone) from=3D::ffff:10.35.161.127,53512, = task_id=3Dc70ace39-dbfe-4f5c-ae49-a1e3a82c <br class=3D"">2758 (api:46) = <br class=3D"">2018-05-05 17:53:27,909+0300 INFO  (vm/e6ce66ce) = [root] /usr/libexec/vdsm/hooks/before_device_create/10_allocate_net: = rc=3D2 err=3Dvm net allocation hook: [unexpected error]: Traceback (most = recent call last): <br class=3D""> File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line = 105, in <module> <br class=3D"">   main() <br = class=3D""> File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 93, = in main <br = class=3D"">   allocate_random_network(device_xml) <br = class=3D""> File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 62, = in allocate_random_network <br class=3D"">   net =3D = _get_random_network() <br class=3D""> File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 50, = in _get_random_network <br class=3D"">   available_nets =3D= _parse_nets() <br class=3D""> File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 46, = in _parse_nets <br class=3D"">   return [net for net in = os.environ[AVAIL_NETS_KEY].split()] <br class=3D""> File = "/usr/lib64/python2.7/UserDict.py", line 23, in __getitem__ <br = class=3D"">   raise KeyError(key) <br class=3D"">KeyError: = 'equivnets' <br class=3D""> <br class=3D""> <br class=3D"">(hooks:110) <br class=3D"">2018-05-05 17:53:27,915+0300 = <span style=3D"color:rgb(255,255,255);background-color:rgb(0,0,0)" = class=3D"">ERROR</span><span style=3D"background-color: rgb(255, 255, = 255);" class=3D""> (vm/e6ce66ce) [virt.vm] = (vmId=3D'e6ce66ce-852f-48c5-9997-5d2959432a27') The vm start process = failed (vm:943) </span><br class=3D"">Traceback (most recent call last): = <br class=3D""> File = "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 872, in = _startUnderlyingVm <br class=3D"">   self._run() <br = class=3D""> File = "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2861, in _run = <br class=3D"">   domxml =3D = hooks.before_vm_start(self._buildDomainXML(), <br class=3D""> File = "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2254, in = _buildDomainXML <br class=3D"">   dom, <a = href=3D"http://self.id/" class=3D"">self.id</a>, self._custom['custom']) = <br class=3D""> File = "/usr/lib/python2.7/site-packages/vdsm/virt/domxml_preprocess.py", line = 240, in replace_device_xml_with_hooks_xml <br = class=3D"">   dev_custom) <br class=3D""> File = "/usr/lib/python2.7/site-packages/vdsm/common/hooks.py", line 134, in = before_device_create <br = class=3D"">   params=3DcustomProperties) <br = class=3D""> File = "/usr/lib/python2.7/site-packages/vdsm/common/hooks.py", line 120, in = _runHooksDir <br class=3D"">   raise = exception.HookError(err) <br class=3D"">HookError: Hook Error: ('vm net = allocation hook: [unexpected error]: Traceback (most recent call = last):\n  File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line = 105, in <module>\n    main()\n<br = class=3D""> File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 93, = in main\n    allocate_random_network(device_xml)\n =  File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 62, = i<br class=3D"">n allocate_random_network\n    net =3D = _get_random_network()\n  File = "/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net", line 50, = in _get_random_network\n    available_nets =3D = _parse_nets()\n  File "/us<br = class=3D"">r/libexec/vdsm/hooks/before_device_create/10_allocate_net", = line 46, in _parse_nets\n    return [net for net in = os.environ[AVAIL_NETS_KEY].split()]\n  File = "/usr/lib64/python2.7/UserDict.py", line 23, in __getit<br = class=3D"">em__\n    raise KeyError(key)\nKeyError: = \'equivnets\'\n\n\n',)<br class=3D""></span><br class=3D""></div><div = class=3D""><br class=3D""></div><div class=3D""><br class=3D""></div><div = class=3D"">Hence, the success rate was 28% against 100% running with d/s = (d/s). If needed, I'll compare against the latest master, but I think = you get the picture with d/s.</div><div class=3D""><br = class=3D""></div><div class=3D""><span style=3D"font-family:monospace" = class=3D""><span style=3D"background-color: rgb(255, 255, 255);" = class=3D"">vdsm-4.20.27-3.gitfee7810.el7.centos.x86_64 </span><br = class=3D"">libvirt-3.9.0-14.el7_5.3.x86_64 <br = class=3D"">qemu-kvm-rhev-2.10.0-21.el7_5.2.x86_64 <br class=3D"">kernel = 3.10.0-862.el7.x86_64</span></div><div class=3D""><span = style=3D"font-family:monospace" class=3D"">rhel7.5<br = class=3D""></span><br class=3D""></div><div class=3D""><br = class=3D""></div><div class=3D"">Logs attached</div></div><div = class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Sat, = May 5, 2018 at 1:26 PM, Elad Ben Aharon <span dir=3D"ltr" = class=3D""><<a href=3D"mailto:ebenahar@redhat.com" target=3D"_blank" = class=3D"">ebenahar(a)redhat.com</a>></span> wrote:<br = class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 = .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr" = class=3D"">nvm, found gluster 3.12 repo, managed to install = vdsm</div><div class=3D"HOEnZb"><div class=3D"h5"><div = class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Sat, = May 5, 2018 at 1:12 PM, Elad Ben Aharon <span dir=3D"ltr" = class=3D""><<a href=3D"mailto:ebenahar@redhat.com" target=3D"_blank" = class=3D"">ebenahar(a)redhat.com</a>></span> wrote:<br = class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 = .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr" = class=3D"">No, vdsm requires it:<div class=3D""><br = class=3D""></div><div class=3D""><span style=3D"font-family:monospace" = class=3D""><span style=3D"background-color: rgb(255, 255, 255);" = class=3D"">Error: Package: vdsm-4.20.27-3.gitfee7810.el7.<wbr = class=3D"">centos.x86_64 (/vdsm-4.20.27-3.gitfee7810.el<wbr = class=3D"">7.centos.x86_64) </span><br = class=3D"">          Req= uires: glusterfs-fuse >=3D 3.12 <br = class=3D"">          Ins= talled: glusterfs-fuse-3.8.4-54.8.el7.<wbr class=3D"">x86_64 = (@rhv-4.2.3)<br class=3D""></span><br class=3D""></div><div = class=3D"">Therefore, vdsm package installation is skipped upon force = install.</div></div><div class=3D"m_8270803836802176999HOEnZb"><div = class=3D"m_8270803836802176999h5"><div class=3D"gmail_extra"><br = class=3D""><div class=3D"gmail_quote">On Sat, May 5, 2018 at 11:42 AM, = Michal Skrivanek <span dir=3D"ltr" class=3D""><<a = href=3D"mailto:michal.skrivanek@redhat.com" target=3D"_blank" = class=3D"">michal.skrivanek(a)redhat.com</a>></span> wrote:<br = class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 = .8ex;border-left:1px #ccc solid;padding-left:1ex"><div = style=3D"word-wrap:break-word;line-break:after-white-space" class=3D""><br= class=3D""><div class=3D""><span class=3D""><br class=3D""><blockquote = type=3D"cite" class=3D""><div class=3D"">On 5 May 2018, at 00:38, Elad = Ben Aharon <<a href=3D"mailto:ebenahar@redhat.com" target=3D"_blank" = class=3D"">ebenahar(a)redhat.com</a>> wrote:</div><br = class=3D"m_8270803836802176999m_4224343900157515506m_-5974818518343566788A= pple-interchange-newline"><div class=3D""><div dir=3D"ltr" class=3D"">Hi = guys, <div class=3D""><br class=3D""></div><div class=3D"">The = vdsm build from the patch requires glusterfs-fuse > 3.12. This = is while the latest 4.2.3-5 d/s build requires 3.8.4 (<span = style=3D"font-family:monospace" class=3D""><span = style=3D"background-color:rgb(255,255,255)" = class=3D"">3.4.0.59rhs-1.el7)</span><br = class=3D""></span></div></div></div></blockquote><div class=3D""><br = class=3D""></div></span>because it is still oVirt, not a downstream = build. We can=E2=80=99t really do downstream builds with unmerged = changes:/</div><div class=3D""><span class=3D""><br class=3D""><blockquote= type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div= class=3D""><font face=3D"monospace" class=3D"">Trying to get this = gluster-fuse build, so far no luck.</font></div><div class=3D""><font = face=3D"monospace" class=3D"">Is this requirement = intentional? </font></div></div></div></blockquote><div = class=3D""><br class=3D""></div></span>it should work regardless, I = guess you can force install it without the dependency</div><div = class=3D""><div = class=3D"m_8270803836802176999m_4224343900157515506h5"><div class=3D""><br= class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div = class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Fri, = May 4, 2018 at 2:38 PM, Michal Skrivanek <span dir=3D"ltr" = class=3D""><<a href=3D"mailto:michal.skrivanek@redhat.com" = target=3D"_blank" class=3D"">michal.skrivanek(a)redhat.com</a>></span> = wrote:<br class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 = 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div = style=3D"word-wrap:break-word;line-break:after-white-space" class=3D"">Hi = Elad,<div class=3D"">to make it easier to compare, Martin backported the = change to 4.2 so it is actually comparable with a run without that = patch. Would you please try that out? </div><div class=3D"">It = would be best to have 4.2 upstream and this[1] run to really minimize = the noise.</div><div class=3D""><br class=3D""></div><div = class=3D"">Thanks,</div><div class=3D"">michal</div><div class=3D""><br = class=3D""></div><div class=3D"">[1] <a = href=3D"http://jenkins.ovirt.org/job/vdsm_4.2_build-artifacts-on-demand-el= 7-x86_64/28/" target=3D"_blank" class=3D"">http://jenkins.ovirt.org/j<wbr = class=3D"">ob/vdsm_4.2_build-artifacts-on<wbr = class=3D"">-demand-el7-x86_64/28/</a></div><div class=3D""><br = class=3D""><div class=3D""><blockquote type=3D"cite" class=3D""><div = class=3D""><div = class=3D"m_8270803836802176999m_4224343900157515506m_-5974818518343566788h= 5"><div class=3D"">On 27 Apr 2018, at 09:23, Martin Polednik <<a = href=3D"mailto:mpolednik@redhat.com" target=3D"_blank" = class=3D"">mpolednik(a)redhat.com</a>> wrote:</div><br = class=3D"m_8270803836802176999m_4224343900157515506m_-5974818518343566788m= _-2464431127513935993Apple-interchange-newline"></div></div><div = class=3D""><div class=3D""><div class=3D""><div = class=3D"m_8270803836802176999m_4224343900157515506m_-5974818518343566788h= 5">On 24/04/18 00:37 +0300, Elad Ben Aharon wrote:<br = class=3D""><blockquote type=3D"cite" class=3D"">I will update with the = results of the next tier1 execution on latest 4.2.3<br = class=3D""></blockquote><br class=3D"">That isn't master but old branch = though. Could you run it against<br class=3D"">*current* VDSM master?<br = class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">On Mon, = Apr 23, 2018 at 3:56 PM, Martin Polednik <<a = href=3D"mailto:mpolednik@redhat.com" target=3D"_blank" = class=3D"">mpolednik(a)redhat.com</a>><br class=3D"">wrote:<br = class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">On = 23/04/18 01:23 +0300, Elad Ben Aharon wrote:<br class=3D""><br = class=3D""><blockquote type=3D"cite" class=3D"">Hi, I've triggered = another execution [1] due to some issues I saw in the<br class=3D"">first = which are not related to the patch.<br class=3D""><br class=3D"">The = success rate is 78% which is low comparing to tier1 executions with<br = class=3D"">code from downstream builds (95-100% success rates) [2].<br = class=3D""><br class=3D""></blockquote><br class=3D"">Could you run the = current master (without the dynamic_ownership patch)<br class=3D"">so = that we have viable comparision?<br class=3D""><br class=3D"">=46rom = what I could see so far, there is an issue with move and copy<br = class=3D""><blockquote type=3D"cite" class=3D"">operations to and from = Gluster domains. For example [3].<br class=3D""><br class=3D"">The logs = are attached.<br class=3D""><br class=3D""><br class=3D"">[1]<br = class=3D"">*<a = href=3D"https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv" = target=3D"_blank" class=3D"">https://rhv-jenkins.rhev-ci-v<wbr = class=3D"">ms.eng.rdu2.redhat.com/job/rhv</a><br = class=3D"">-4.2-ge-runner-tier1-after-upg<wbr = class=3D"">rade/7/testReport/<br class=3D""><<a = href=3D"https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv" = target=3D"_blank" class=3D"">https://rhv-jenkins.rhev-ci-v<wbr = class=3D"">ms.eng.rdu2.redhat.com/job/rhv</a><br = class=3D"">-4.2-ge-runner-tier1-after-upg<wbr = class=3D"">rade/7/testReport/>*<br class=3D""><br class=3D""><br = class=3D""><br class=3D"">[2]<br class=3D""><a = href=3D"https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/" = target=3D"_blank" class=3D"">https://rhv-jenkins.rhev-ci-vm<wbr = class=3D"">s.eng.rdu2.redhat.com/job/</a><br class=3D""><br = class=3D"">rhv-4.2-ge-runner-tier1-after-<wbr class=3D"">upgrade/7/<br = class=3D""><br class=3D""><br class=3D""><br class=3D"">[3]<br = class=3D"">2018-04-22 13:06:28,316+0300 INFO  (jsonrpc/7) = [vdsm.api] FINISH<br class=3D"">deleteImage error=3DImage does not exist = in domain:<br class=3D"">'image=3Dcabb8846-7a4b-4244-9835<wbr = class=3D"">-5f603e682f33,<br class=3D"">domain=3De5fd29c8-52ba-467e-be09<w= br class=3D"">-ca40ff054dd4'<br class=3D"">from=3D:<br = class=3D"">:ffff:10.35.161.182,40936, flow_id=3Ddisks_syncAction_ba6b2<wbr= class=3D"">630-5976-4935,<br = class=3D"">task_id=3D3d5f2a8a-881c-409e-93e<wbr class=3D"">9-aaa643c10e42 = (api:51)<br class=3D"">2018-04-22 13:06:28,317+0300 ERROR (jsonrpc/7) = [storage.TaskManager.Task]<br = class=3D"">(Task=3D'3d5f2a8a-881c-409e-93e9<wbr class=3D"">-aaa643c10e42')= Unexpected error (task:875)<br class=3D"">Traceback (most recent call = last):<br class=3D"">File "/usr/lib/python2.7/site-packa<wbr = class=3D"">ges/vdsm/storage/task.py", line 882,<br class=3D"">in<br = class=3D"">_run<br class=3D"">  return fn(*args, **kargs)<br = class=3D"">File "<string>", line 2, in deleteImage<br = class=3D"">File "/usr/lib/python2.7/site-packa<wbr = class=3D"">ges/vdsm/common/api.py", line 49, in<br class=3D"">method<br = class=3D"">  ret =3D func(*args, **kwargs)<br class=3D"">File = "/usr/lib/python2.7/site-packa<wbr class=3D"">ges/vdsm/storage/hsm.py", = line 1503,<br class=3D"">in<br class=3D"">deleteImage<br class=3D""> =  raise se.ImageDoesNotExistInSD(imgUU<wbr class=3D"">ID, sdUUID)<br = class=3D"">ImageDoesNotExistInSD: Image does not exist in domain:<br = class=3D"">'image=3Dcabb8846-7a4b-4244-9835<wbr = class=3D"">-5f603e682f33,<br class=3D"">domain=3De5fd29c8-52ba-467e-be09<w= br class=3D"">-ca40ff054dd4'<br class=3D""><br class=3D"">2018-04-22 = 13:06:28,317+0300 INFO  (jsonrpc/7) [storage.TaskManager.Task]<br = class=3D"">(Task=3D'3d5f2a8a-881c-409e-93e9<wbr class=3D"">-aaa643c10e42')= aborting: Task is aborted:<br class=3D"">"Image does not exist in = domain: 'image=3Dcabb8846-7a4b-4244-9835<wbr class=3D"">-<br = class=3D"">5f603e682f33, domain=3De5fd29c8-52ba-467e-be09<wbr = class=3D"">-ca40ff054dd4'" - code 268<br class=3D"">(task:1181)<br = class=3D"">2018-04-22 13:06:28,318+0300 ERROR (jsonrpc/7) = [storage.Dispatcher] FINISH<br class=3D"">deleteImage error=3DImage does = not exist in domain:<br class=3D"">'image=3Dcabb8846-7a4b-4244-9835<wbr = class=3D"">-5f603e682f33,<br class=3D"">domain=3De5fd29c8-52ba-467e-be09<b= r class=3D"">-ca40ff054d<br class=3D"">d4' (dispatcher:82)<br = class=3D""><br class=3D""><br class=3D""><br class=3D"">On Thu, Apr 19, = 2018 at 5:34 PM, Elad Ben Aharon <<a = href=3D"mailto:ebenahar@redhat.com" target=3D"_blank" = class=3D"">ebenahar(a)redhat.com</a>><br class=3D"">wrote:<br = class=3D""><br class=3D"">Triggered a sanity tier1 execution [1] using = [2], which covers all the<br class=3D""><blockquote type=3D"cite" = class=3D"">requested areas, on iSCSI, NFS and Gluster.<br class=3D"">I'll = update with the results.<br class=3D""><br class=3D"">[1]<br class=3D""><a= href=3D"https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/4.2" = target=3D"_blank" class=3D"">https://rhv-jenkins.rhev-ci-vm<wbr = class=3D"">s.eng.rdu2.redhat.com/view/4.2</a><br = class=3D"">_dev/job/rhv-4.2-ge-flow-stora<wbr class=3D"">ge/1161/<br = class=3D""><br class=3D"">[2]<br class=3D""><a = href=3D"https://gerrit.ovirt.org/#/c/89830/" target=3D"_blank" = class=3D"">https://gerrit.ovirt.org/#/c/8<wbr class=3D"">9830/</a><br = class=3D"">vdsm-4.30.0-291.git77aef9a.el7<wbr class=3D"">.x86_64<br = class=3D""><br class=3D""><br class=3D""><br class=3D"">On Thu, Apr 19, = 2018 at 3:07 PM, Martin Polednik <<a = href=3D"mailto:mpolednik@redhat.com" target=3D"_blank" = class=3D"">mpolednik(a)redhat.com</a>><br class=3D"">wrote:<br = class=3D""><br class=3D"">On 19/04/18 14:54 +0300, Elad Ben Aharon = wrote:<br class=3D""><blockquote type=3D"cite" class=3D""><br = class=3D"">Hi Martin,<br class=3D""><blockquote type=3D"cite" = class=3D""><br class=3D"">I see [1] requires a rebase, can you please = take care?<br class=3D""><br class=3D""><br class=3D""></blockquote>Should= be rebased.<br class=3D""><br class=3D"">At the moment, our automation = is stable only on iSCSI, NFS, Gluster and<br class=3D""><br = class=3D""><blockquote type=3D"cite" class=3D"">FC.<br class=3D"">Ceph = is not supported and Cinder will be stabilized soon, AFAIR, it's<br = class=3D"">not<br class=3D"">stable enough at the moment.<br = class=3D""><br class=3D""><br class=3D""></blockquote>That is still = pretty good.<br class=3D""><br class=3D""><br class=3D"">[1] <a = href=3D"https://gerrit.ovirt.org/#/c/89830/" target=3D"_blank" = class=3D"">https://gerrit.ovirt.org/#/c/8<wbr class=3D"">9830/</a><br = class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br = class=3D""><br class=3D"">Thanks<br class=3D""><br class=3D"">On Wed, = Apr 18, 2018 at 2:17 PM, Martin Polednik <<a = href=3D"mailto:mpolednik@redhat.com" target=3D"_blank" = class=3D"">mpolednik(a)redhat.com</a><br class=3D"">><br = class=3D"">wrote:<br class=3D""><br class=3D"">On 18/04/18 11:37 +0300, = Elad Ben Aharon wrote:<br class=3D""><br class=3D""><blockquote = type=3D"cite" class=3D""><br class=3D"">Hi, sorry if I misunderstood, I = waited for more input regarding what<br class=3D""><br = class=3D""><blockquote type=3D"cite" class=3D"">areas<br class=3D"">have = to be tested here.<br class=3D""><br class=3D""><br class=3D"">I'd say = that you have quite a bit of freedom in this regard.<br = class=3D""></blockquote>GlusterFS<br class=3D"">should be covered by = Dennis, so iSCSI/NFS/ceph/cinder with some suite<br class=3D"">that = covers basic operations (start & stop VM, migrate it), snapshots<br = class=3D"">and merging them, and whatever else would be important for = storage<br class=3D"">sanity.<br class=3D""><br class=3D"">mpolednik<br = class=3D""><br class=3D""><br class=3D"">On Wed, Apr 18, 2018 at 11:16 = AM, Martin Polednik <<br class=3D""><a = href=3D"mailto:mpolednik@redhat.com" target=3D"_blank" = class=3D"">mpolednik(a)redhat.com</a><br class=3D"">><br class=3D""><br = class=3D"">wrote:<br class=3D""><blockquote type=3D"cite" class=3D""><br = class=3D"">On 11/04/18 16:52 +0300, Elad Ben Aharon wrote:<br = class=3D""><br class=3D""><br class=3D""><blockquote type=3D"cite" = class=3D"">We can test this on iSCSI, NFS and GlusterFS. As for ceph = and<br class=3D"">cinder,<br class=3D""><br class=3D"">will<br = class=3D""><blockquote type=3D"cite" class=3D"">have to check, since = usually, we don't execute our automation on<br class=3D"">them.<br = class=3D""><br class=3D""><br class=3D"">Any update on this? I believe = the gluster tests were successful,<br class=3D"">OST<br class=3D""><br = class=3D""></blockquote>passes fine and unit tests pass fine, that makes = the storage<br class=3D"">backends<br class=3D"">test the last required = piece.<br class=3D""><br class=3D""><br class=3D"">On Wed, Apr 11, 2018 = at 4:38 PM, Raz Tamir <<a href=3D"mailto:ratamir@redhat.com" = target=3D"_blank" class=3D"">ratamir(a)redhat.com</a>><br = class=3D"">wrote:<br class=3D""><br class=3D""><br class=3D"">+Elad<br = class=3D""><blockquote type=3D"cite" class=3D""><br class=3D""><br = class=3D"">On Wed, Apr 11, 2018 at 4:28 PM, Dan Kenigsberg <<a = href=3D"mailto:danken@redhat.com" target=3D"_blank" = class=3D"">danken(a)redhat.com</a><br class=3D""><blockquote type=3D"cite" = class=3D"">><br class=3D"">wrote:<br class=3D""><br class=3D"">On = Wed, Apr 11, 2018 at 12:34 PM, Nir Soffer <<a = href=3D"mailto:nsoffer@redhat.com" target=3D"_blank" = class=3D"">nsoffer(a)redhat.com</a>><br class=3D"">wrote:<br = class=3D""><br class=3D""><br class=3D"">On Wed, Apr 11, 2018 at 12:31 = PM Eyal Edri <<a href=3D"mailto:eedri@redhat.com" target=3D"_blank" = class=3D"">eedri(a)redhat.com</a>><br class=3D""><blockquote = type=3D"cite" class=3D"">wrote:<br class=3D""><br class=3D""><br = class=3D"">Please make sure to run as much OST suites on this patch = as<br class=3D""><blockquote type=3D"cite" class=3D"">possible<br = class=3D""><br class=3D"">before merging ( using 'ci please build' )<br = class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br = class=3D""><br class=3D"">But note that OST is not a way to verify the = patch.<br class=3D""><br class=3D""><br class=3D""></blockquote>Such = changes require testing with all storage types we support.<br = class=3D""><br class=3D"">Nir<br class=3D""><br class=3D"">On Tue, Apr = 10, 2018 at 4:09 PM, Martin Polednik <<br class=3D""><a = href=3D"mailto:mpolednik@redhat.com" target=3D"_blank" = class=3D"">mpolednik(a)redhat.com</a><br class=3D"">><br class=3D""><br = class=3D"">wrote:<br class=3D""><br class=3D""><br class=3D""><blockquote = type=3D"cite" class=3D"">Hey,<br class=3D""><br class=3D""><br = class=3D"">I've created a patch[0] that is finally able to activate<br = class=3D""><blockquote type=3D"cite" class=3D"">libvirt's<br = class=3D"">dynamic_ownership for VDSM while not negatively affecting<br = class=3D"">functionality of our storage code.<br class=3D""><br = class=3D"">That of course comes with quite a bit of code removal, = mostly<br class=3D"">in<br class=3D"">the<br class=3D"">area of host = devices, hwrng and anything that touches devices;<br class=3D"">bunch<br = class=3D"">of test changes and one XML generation caveat (storage is<br = class=3D"">handled<br class=3D"">by<br class=3D"">VDSM, therefore disk = relabelling needs to be disabled on the<br class=3D"">VDSM<br = class=3D"">level).<br class=3D""><br class=3D"">Because of the scope of = the patch, I welcome<br class=3D"">storage/virt/network<br = class=3D"">people to review the code and consider the implication = this<br class=3D"">change<br class=3D"">has<br class=3D"">on = current/future features.<br class=3D""><br class=3D"">[0] <a = href=3D"https://gerrit.ovirt.org/#/c/89830/" target=3D"_blank" = class=3D"">https://gerrit.ovirt.org/#/c/8<wbr class=3D"">9830/</a><br = class=3D""><br class=3D""><br class=3D"">In particular: =  dynamic_ownership was set to 0 prehistorically<br class=3D"">(as<br = class=3D""><br class=3D""><br class=3D""></blockquote>part<br = class=3D""><br class=3D""></blockquote><br class=3D"">of <a = href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D554961" = target=3D"_blank" class=3D"">https://bugzilla.redhat.com/sh<wbr = class=3D"">ow_bug.cgi?id=3D554961</a> ) because<br = class=3D""></blockquote>libvirt,<br class=3D"">running as root, was not = able to play properly with root-squash<br class=3D"">nfs<br = class=3D"">mounts.<br class=3D""><br class=3D"">Have you attempted this = use case?<br class=3D""><br class=3D"">I join to Nir's request to run = this with storage QE.<br class=3D""><br class=3D""><br class=3D""><br = class=3D""><br class=3D"">--<br class=3D""></blockquote><br class=3D""><br= class=3D"">Raz Tamir<br class=3D"">Manager, RHV QE<br class=3D""><br = class=3D""><br class=3D""><br class=3D""><br class=3D""><br = class=3D""></blockquote></blockquote></blockquote></blockquote></blockquot= e></blockquote></blockquote><br class=3D""></blockquote></blockquote><br = class=3D""><br class=3D""></blockquote></blockquote></div></div><span = class=3D"">______________________________<wbr = class=3D"">_________________<br class=3D"">Devel mailing list<br = class=3D""><a href=3D"mailto:Devel@ovirt.org" target=3D"_blank" = class=3D"">Devel(a)ovirt.org</a><br class=3D""><a = href=3D"http://lists.ovirt.org/mailman/listinfo/devel" target=3D"_blank" = class=3D"">http://lists.ovirt.org/mailman<wbr = class=3D"">/listinfo/devel</a><br class=3D""><br class=3D""><br = class=3D""></span></div></div></blockquote></div><br = class=3D""></div></div></blockquote></div><br class=3D""></div> </div></blockquote></div><br = class=3D""></div></div></div></blockquote></div><br class=3D""></div> </div></div></blockquote></div><br class=3D""></div> </div></div></blockquote></div><br class=3D""></div> <span = id=3D"cid:77382D15-7BFB-4164-A6D0-F8FA5BE5E692@mrkev"><logs.tar.gz><= /span></div></blockquote></div><br class=3D""></div></body></html>= --Apple-Mail=_82B55436-9E61-4F82-AF39-6B64C656C187--

5 11

[Announcement] Introducing Standard CI build summary
by Daniel Belenky 31 May '18

31 May '18

Hi, On behalf of oVirt's CI team, I'm happy to announce the STDCI build summary - *We've used patternfly *[1] <http://www.patternfly.org/> to ensure a clean, simple and elegant view of information for your builds. The summary is available for STDCI V2 [2] projects and it is located under *build-artifacts/ci_build_summary.html* *[image: location.png]* STDCI build summary is a single web page, generated dynamically for every build on STDCI. It visualizes all CI threads that ran for that build and features a set of quick links. The main view shows a list of all threads with an indicator if that thread failed or passed. The quick links to the right of each thread lead to *log* and *artifacts* of that thread only. Note that *log* shows the output of your script only to ease debugging. [image: threads_list.png] At the top right side, you will find a set of quick links for convenience: [image: menus.png] *Test results* (available if JUnit XML files were exported during the build) leads to a summary of all JUnit test results that were collected during the build. *Test results analyzer *shows the history of test execution results in a tabular format. *Findbugs results *(available if Findbugs report was generated and exported during the build) shows trend report for Findbugs. *Full build log* shows the full log of all threads. This log is harder to understand as it includes output from CI runtime environment as well as from your scripts. *Rebuild (for GitHub PR)/Retrigger (for Gerrit patch): *Run the build again. The new build will report and vote to Gerrit/GitHub with the new result. *View PR/patch: *Links back to the PR on GitHub or patchset page in Gerrit. [image: view_in_jenkins.png] *View in Jenkins* will lead you back to the build view in Jenkins [image: view_in_blueocean.png] *View in Blue Ocean *will lead you to the build view in Jenkins Blue Ocean view STDCI Documentation https://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standar… For any questions, don't hesitate to contact the CI team at #rhev-integ, #rhev-dev or view mail at infra(a)ovirt.org. Thanks, Daniel.

2 1

CI not responding to GitHub web hooks
by Tomáš Golembiovský 31 May '18

31 May '18

Hi, it seems CI is not responding to GitHub web hooks... is it congested or broken? Tomas -- Tomáš Golembiovský <tgolembi(a)redhat.com>

2 1

[ OST Failure Report ] [ oVirt master ] [ 2018-05-25 ] [AddHost]
by Barak Korren 30 May '18

30 May '18

Test failed: [ AddHost (in upgrade-from-release-suite) ] Link to suspected patches: https://gerrit.ovirt.org/#/c/91445/5 - Disable TLS versions < 1.2 for hosts with cluster level>=4.1 Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7776/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7776/artifact… Error snippet from log: From nosetst log: <error> AssertionError: False != True after 1200 seconds </error> Not finding a host deploy log in /var/log/ovirt-engine for some reason. This seems to have cause consistent failure in all other engine patches that followed it. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

7 24

Travis failure on ovirt-engine
by Sandro Bonazzola 30 May '18

30 May '18

Hi, now that travis is correctly using postresql 9.5, it fails on: ERROR: function uuid_generate_v1() does not exist looking at the spec file, I think we miss postgresql-contrib (or it's equivalent) within the test environment. Roman, can you help with this? -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 1

unboundid-ldapsdk-4.0.6 is now available for testing
by Sandro Bonazzola 30 May '18

30 May '18

On Fedora we had previously 4.0.5. The new releases 4.0.6 will be soon available in updates-testing repository for Fedora >= 27 and includes several bug fixes and a few enhancements. You can see release notes here: https://github.com/ pingidentity/ldapsdk/releases In oVirt this package is required by ovirt-engine-extension-aaa-ldap. If you're going to test the package, please provide karma: Fedora 28: https://bodhi.fedoraproject.org/updates/FEDORA-2018-733f231fd4 Fedora 27: https://bodhi.fedoraproject.org/updates/FEDORA-2018-18d425fcdd Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 1

Does ovirt engine itself support high scalability
by simiam 30 May '18

30 May '18

Hi, Does ovirt engine itself support high scalability? Thanks.

2 2

UI validation testing in ovirt-system-tests
by Greg Sheremeta 28 May '18

28 May '18

Hi, I added some basic UI validation testing to ovirt-system-tests [1]. Now when ovirt-engine patches are merged, OST will verify that the webadmin UI loads and renders. It currently verifies on both Chrome and Firefox and takes screenshots (example: [2]). We decided to start with the basics -- only login and a few simple navigation verification, with no assertions. Patches are most welcome since I need to move on to other tasks. Known needs: - add an assertion that ui.log remains empty while browsing - web-ui tests - assertions that things look decent Best wishes, Greg [1] https://gerrit.ovirt.org/#/c/67166/ Use a headless browser to perform basic UI sanity tests -- verify the UI loads, we can login, the UI renders correctly, navigation works, etc. [2] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7829/artifac… (URL expires, screenshot below) Example from the test: -- 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

[ OST Failure Report ] [ oVirt master ] [ 2018-05-28 ] [004_basic_sanity.disk_operations]
by Barak Korren 28 May '18

28 May '18

Test failed: [ 004_basic_sanity.disk_operations <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7811/testRepo…> ] Link to suspected patches: https://gerrit.ovirt.org/#/c/91068/4 Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7811/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7811/artifact… Error snippet from log: <error> Note: There is another ongoing regression in engine master ATM, but this issue is causing a different suit to fail so it was luckily not masked by it. False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 78, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 528, in cold_storage_migration lambda: api.follow_link( File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 271, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 258, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 237, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: False != True after 600 seconds --------------------- >> end captured logging << --------------------- </error> -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 2

Does ovirt engine itself support high scalability
by simiam 28 May '18

28 May '18

Hi, Does ovirt engine itself support high scalability? Thanks.

1 0

CVE-2018-3639 - Important - oVirt - Speculative Store Bypass
by Sandro Bonazzola 25 May '18

25 May '18

As you may have already heard, an industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of Load & Store instructions. This issue is well described by CVE-2018-3639 announce available at https://access.redhat.com/security/cve/cve-2018-3639. oVirt team has released right now an update of ovirt-engine to version 4.2.3.7 which add support for SSBD CPUs in order to mitigate the security issue. If you are running oVirt on Red Hat Enterprise Linux, please apply updates described in https://access.redhat.com/security/cve/cve-2018-3639. If you are running oVirt on CentOS Linux please apply updated described by: CESA-2018:1629 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html> CESA-2018:1632 Important CentOS 7 libvirt Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022840.html> CESA-2018:1649 Important CentOS 7 java-1.8.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022839.html> CESA-2018:1648 Important CentOS 7 java-1.7.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022838.html> An update for qemu-kvm-ev has been also tagged for release and announced with CESA-2018:1655 Important: qemu-kvm-ev security update <https://lists.centos.org/pipermail/centos-virt/2018-May/005804.html> but due to some issues in CentOS release process for Virt SIG content, it is not yet available on mirrors. We are working with CentOS community to get the packages signed and published as soon as possible. In the meanwhile you can still get the update package by enabling the test repository https://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ on your systems or manually installing the package from the repository. If you're running oVirt on a different Linux distribution, please check with your vendor for available updates. Please note that to fully mitigate this vulnerability, system administrators must apply both hardware “microcode” updates and software patches that enable new functionality. At this time, microprocessor microcode will be delivered by the individual manufacturers. The oVirt team recommends end users and systems administrator to apply any available updates as soon as practical. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 1

[ANN] oVirt 4.2.4 First Release Candidate is now available
by Sandro Bonazzola 24 May '18

24 May '18

The oVirt Project is pleased to announce the availability of the oVirt 4.2.4 First Release Candidate, as of May 24th, 2018 This update is a release candidate of the fourth in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later Due to an issue with CentOS mirrors oVirt Node has not been built. We'll build and release oVirt Node as soon as the updated qemu-kvm-ev will be available on CentOS mirrors. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node is not yet available, will be provided soon[2] Additional Resources: * Read more about the oVirt 4.2.4 release highlights: http://www.ovirt.org/release/4.2.4/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.2.4/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

2 3

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [22-05-2018 ] [ 004_basic_sanity.update_template_version]
by Dafna Ron 24 May '18

24 May '18

Hi, This failure seems to be related to the regression we found earlier today which was causing failure in initialize engine: https://gerrit.ovirt.org/#/c/89293/ - core:make search string fields not null and empty The fix for the above change was reported as failed on the update template test with an error which I think is related to the same regression. https://gerrit.ovirt.org/#/c/91476/ - db: resolve duplicate db scripts Can you please have a look? *Link to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7675/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7675/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7675/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7675/artifact…>(Relevant) error snippet from the log: <error>2018-05-22 12:40:21,015-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] method: runQuery, params: [GetSoundDevices, IdQueryParameters:{refresh='false', filtered='false'}], timeElapsed: 3ms2018-05-22 12:40:21,021-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] method: get, params: [5cf93146-a5f1-4330-affe-672eaf39cc0d], timeElapsed: 1ms2018-05-22 12:40:21,045-04 INFO [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] Lock Acquired to object 'EngineLock:{exclusiveLocks='[2f43ef56-db61-4d93-99ee-00e84c741a29=DISK, bb954b00-d22c-4421-aba2-35335f9c441f=TEMPLATE, 9d749a87-45c9-4251-8e69-e55da5d3deed=DISK]', sharedLocks='[5cf93146-a5f1-4330-affe-672eaf39cc0d=VM, 4c68925d-569d-4987-8f54-29859763391a=TEMPLATE]'}'2018-05-22 12:40:21,097-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] method: get, params: [5cf93146-a5f1-4330-affe-672eaf39cc0d], timeElapsed: 2ms2018-05-22 12:40:21,111-04 INFO [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] Running command: AddVmTemplateCommand internal: false. Entities affected : ID: 79448f95-c26c-45b6-b396-ecd8fe98c2d9 Type: StoragePoolAction group CREATE_TEMPLATE with role type USER2018-05-22 12:40:21,115-04 INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] START, SetVmStatusVDSCommand( SetVmStatusVDSCommandParameters:{vmId='5cf93146-a5f1-4330-affe-672eaf39cc0d', status='ImageLocked', exitStatus='Normal'}), log id: 4897bb3a2018-05-22 12:40:21,117-04 INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] FINISH, SetVmStatusVDSCommand, return: , log id: 4897bb3a2018-05-22 12:40:21,117-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] method: runVdsCommand, params: [SetVmStatus, SetVmStatusVDSCommandParameters:{vmId='5cf93146-a5f1-4330-affe-672eaf39cc0d', status='ImageLocked', exitStatus='Normal'}], timeElapsed: 4ms2018-05-22 12:40:21,125-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.CustomSQLErrorCodeSQLExceptionTranslator] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] Translating SQLException with SQL state '23502', error code '0', message [ERROR: null value in column "description" violates not-null constraint Detail: Failing row contains (bb954b00-d22c-4421-aba2-35335f9c441f, CirrOS_0.4.0_for_x86_64_glance_template, 512, 4c68925d-569d-4987-8f54-29859763391a, 0, null, 5e28a528-59ad-4054-9397-a9174ec356a7, 2018-05-22 12:40:21.119-04, 1, null, f, 1, 1, 1, Etc/GMT, t, f, 2018-05-22 12:40:21.120272-04, null, null, f, 1, 0, 0, 1, 0, , 3, null, null, null, 0, , , 256, TEMPLATE, 0, 1, 7d498f3a-b16d-4574-9e47-9c87cd1c866b, f, null, f, f, 1, f, f, f, bd48ab26-5ddb-11e8-b3bb-5452c0a8c904, null, , f, 0, null, null, null, guest_agent, null, null, null, 2, null, 2, 12345678, f, interleave, t, t, 20fa3adb-29f2-4938-b07a-751d63a65447, null, null, null, 0, null, 3463183e-b5ce-076d-2a26-0e3e9d93dafb, d2f75033-25ec-e3b3-3c27-351115d4aa2b, null, 0, LOCK_SCREEN, 2, null, null, 2048, null, AUTO_RESUME). Where: SQL statement "INSERT INTO vm_static( child_count, creation_date, description, free_text_comment, mem_size_mb, max_memory_size_mb, num_of_io_threads, vm_name, num_of_sockets, cpu_per_socket, threads_per_cpu, os, vm_guid, cluster_id, num_of_monitors, single_qxl_pci, allow_console_reconnect, template_status, usb_policy, time_zone, fail_back, vm_type, nice_level, cpu_shares, default_boot_sequence, default_display_type, priority, auto_startup, is_stateless, iso_path, origin, initrd_url, kernel_url, kernel_params, entity_type, quota_id, migration_support, is_disabled,dedicated_vm_for_vds, is_smartcard_enabled, is_delete_protected, sso_method, tunnel_migration, vnc_keyboard_layout, min_allocated_mem, is_run_and_pause, created_by_user_id, migration_downtime, template_version_number, vmt_guid, template_version_name, serial_number_policy, custom_serial_number, is_boot_menu_enabled, is_spice_file_transfer_enabled, is_spice_copy_paste_enabled, cpu_profile_id, numatune_mode, is_auto_converge, is_migrate_compressed, predefined_properties, userdefined_properties, custom_emulated_machine, bios_type, custom_cpu_name, small_icon_id, large_icon_id, console_disconnect_action, resume_behavior, custom_compatibility_version, migration_policy_id, lease_sd_id) VALUES( v_child_count, v_creation_date, v_description, v_free_text_comment, v_mem_size_mb, v_max_memory_size_mb, v_num_of_io_threads, v_name, v_num_of_sockets, v_cpu_per_socket, v_threads_per_cpu, v_os, v_vmt_guid, v_cluster_id, v_num_of_monitors, v_single_qxl_pci, v_allow_console_reconnect, v_status, v_usb_policy, v_time_zone, v_fail_back, v_vm_type, v_nice_level, v_cpu_shares, v_default_boot_sequence, v_default_display_type, v_priority, v_auto_startup, v_is_stateless, v_iso_path, v_origin, v_initrd_url, v_kernel_url, v_kernel_params, v_template_type, v_quota_id, v_migration_support, v_is_disabled, v_dedicated_vm_for_vds, v_is_smartcard_enabled, v_is_delete_protected, v_sso_method, v_tunnel_migration, v_vnc_keyboard_layout, v_min_allocated_mem, v_is_run_and_pause, v_created_by_user_id, v_migration_downtime, v_template_version_number, v_base_template_id, v_template_version_name, v_serial_number_policy, v_custom_serial_number, v_is_boot_menu_enabled, v_is_spice_file_transfer_enabled, v_is_spice_copy_paste_enabled, v_cpu_profile_id, v_numatune_mode, v_is_auto_converge, v_is_migrate_compressed, v_predefined_properties, v_userdefined_properties, v_custom_emulated_machine, v_bios_type, v_custom_cpu_name, v_small_icon_id, v_large_icon_id, v_console_disconnect_action, v_resume_behavior, v_custom_compatibility_version, v_migration_policy_id, v_lease_sd_id)"PL/pgSQL function insertvmtemplate(integer,timestamp with time zone,character varying,text,integer,integer,integer,character varying,integer,integer,integer,integer,uuid,uuid,integer,boolean,boolean,integer,integer,character varying,boolean,integer,integer,integer,integer,integer,integer,boolean,boolean,boolean,boolean,character varying,boolean,character varying,integer,character varying,character varying,character varying,uuid,integer,text,boolean,character varying,integer,boolean,uuid,character varying,integer,uuid,character varying,smallint,character varying,boolean,boolean,boolean,uuid,character varying,boolean,boolean,character varying,character varying,character varying,integer,character varying,uuid,uuid,character varying,character varying,character varying,uuid,uuid) line 16 at SQL statement]; SQL was [{call insertvmtemplate(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}] for task [CallableStatementCallback]</error>*

3 9

oVirt Privacy policy change
by Sandro Bonazzola 24 May '18

24 May '18

*As part of an oVirt project review, we're publishing an updated privacy policy.You should read the statement fully, but the key updates include:* Clearer descriptions of how oVirt uses your personal data to provide services;* Additional detail on how your personal data may be shared to serve the public interest and that of the open source community; and* More focus on how you can review, modify, and update your personal data.You can find the new statement on the oVirt website at this location: https://ovirt.org/site/privacy-policy/ <https://ovirt.org/site/privacy-policy/>oVirt website pages have been updated to include links to the privacy policy. The new privacy statement takes effect on Friday, May 25, 2018. * -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

Planned restart of production services
by Evgheni Dereveanchin 23 May '18

23 May '18

Hi everyone, I will be restarting several production systems within the following hour to apply security updates. The following services may be unreachable for some period of time: - www.ovirt.org - project website - resources.ovirt.org - package repositories - gerrit.ovirt.org - code review - jenkins.ovirt.org - CI master It will not be possible to submit/review patches, clone repositories or run CI jobs during this period. Package repositories and the website will also be unreachable for a short period of time. I will announce you once the maintenance is complete. -- Regards, Evgheni Dereveanchin

2 2

[FC28] PostgreSQL 10
by Sandro Bonazzola 23 May '18

23 May '18

2018-05-09 10:04 GMT+02:00 Benny Zlotnik <bzlotnik(a)redhat.com>: > I've had an issue[1] running engine, it looks like it's related to Fedora > 28 coming with postgresql 10. > I managed to workaround it by upgrading locally the jdbc driver to the > latest 42.2.2 > Dropping infra, adding Martin and Eli. Also changing subject > > > > [1] > 2018-05-09 10:59:26,303+03 ERROR [org.jboss.as.controller.management-operation] > (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - > address: ([("deployment" => "engine.ear")]) - failure description: > {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\" > engine.ear\".\" > bll.jar\".component.Backend.START" => "java.lang.IllegalStateException: > WFLYEE0042: Failed to construct component instance > Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to > construct component instance > Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: > WELD-000049: Unable to invoke protected void org.ovirt.engine.core. > bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@891dc3a > Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: > Unable to invoke protected void org.ovirt.engine.core.bll. > TagsDirector.init() > on org.ovirt.engine.core.bll.TagsDirector@891dc3a > Caused by: java.lang.reflect.InvocationTargetException > Caused by: org.springframework.jdbc.BadSqlGrammarException: > PreparedStatementCallback; bad SQL grammar [select * from > gettagsbyparent_id()]; n > ested exception is org.postgresql.util.PSQLException: ERROR: function > gettagsbyparent_id() does not exist > Hint: No function matches the given name and argument types. You might > need to add explicit type casts. > Position: 16 > Caused by: org.postgresql.util.PSQLException: ERROR: function > gettagsbyparent_id() does not exist > Hint: No function matches the given name and argument types. You might > need to add explicit type casts. > Position: 16"}} > > > On Wed, May 9, 2018 at 10:38 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > >> Hi, >> if you're not yet on Fedora 28, please consider updating to it. >> On master we are aiming to support Fedora 28 and we are dismissing any >> older Fedora jobs in Jenkins soon. >> >> As a reminder Fedora 26 support is going to be EOL on Tuesday, May 29th, >> 2018. >> >> Thanks, >> -- >> >> SANDRO BONAZZOLA >> >> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D >> >> Red Hat EMEA <https://www.redhat.com/> >> >> sbonazzo(a)redhat.com >> <https://red.ht/sig> >> <https://redhat.com/summit> >> >> _______________________________________________ >> Infra mailing list -- infra(a)ovirt.org >> To unsubscribe send an email to infra-leave(a)ovirt.org >> >> > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

4 4

[ACTION REQUIRED] Sun-setting oVirt 4.1 in CI
by Barak Korren 21 May '18

21 May '18

Hi all, Given that oVirt 4.1 has now gone EOL, we're going to start dropping all relates assets in the CI system. This includes: - All 4.1 jobs - All 4.1 change queues - The 4.1 'tested' repositories - The 4.1 'nightly snapshot' repositores. Maintainers, if your projects have any dependencies on the resources above, please be sure to update them to more up to date or stable resources. In particular, to depend on any 4.1 packages, please use the 4.1 released repo at: http://resources.ovirt.org/pub/ovirt-4.1/ Thanks, -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

3 2

engine communication with clients
by Anastasiya Ruzhanskaya 21 May '18

21 May '18

Hello! I have a question about communication between end users (clients) and engine. From the documentation I see that it was planned to transfer everything to REST API. Is it achieved already? Or do some types of connection still use RPC protocol ( I know that engine and vdsm use libvirt, but not sure about engine and clients).

2 1

openSUSE Leap 15.0 and Tumbleweed now supported on COPR
by Neal Gompa 20 May '18

20 May '18

Hey, As of now, Fedora COPR can now build packages for openSUSE Leap 15.0 and Tumbleweed, in addition to CentOS 6/7 with EPEL, Mageia 6 and Cauldron, and of course, Fedora 26+ (including Rawhide). Sandro mentioned on IRC that it might be a good idea to mention this in the devel ML for folks who work on oVirt packaging to know about this, so that things like "ovirt-guest-agent" could be provided via COPR relatively up to date for a wider variety of Linux distributions, hence this email. :) -- 真実はいつも一つ！/ Always, there's only one truth!

1 0

[FYI] Blog entry about oVirt on the mainframe
by Viktor VM Mihajlovski 18 May '18

18 May '18

Hi, as some of you know the support for s390x KVM hosts has been in oVirt for a while now - without raising too much attention. The following article highlights the availability and describes how to add a mainframe to an oVirt cluster: https://kvmonz.blogspot.co.uk/2018/05/knowledge-series-managing-kvm-on-ibm-… -- Regards, Viktor Mihajlovski

2 1

Rerun-Hooks Functionality is Restored in Gerrit
by Anton Marchukov 17 May '18

17 May '18

Hello All. We have fixed the Rerun-Hooks comment functionality on gerrit.ovirt.org and you should be able to start using it now. The most common use case for this is to rerun all patchset-created hooks on a patch. Just leave a comment with: Rerun-Hooks: all and shortly you will get the hooks to be re-executed and output delivered as a gerrit comment (same as you would just submitted the patch). This also supports rerunning individual hooks. But it is a bit less straightforward as you need to know the hook file name. E.g. the following is possible: Rerun-Hooks: patchset-created.bz.1.check_bug_url, patchset-created.bz.2.check_product you can see the default hooks list at [1]. I think most of the time "Rerun-Hooks: all" will do the job and it is all you need to remember. Note that currently it is possible to rerun online patchset-created hooks. Anton. [1] https://gerrit.ovirt.org/gitweb?p=gerrit-admin.git;a=tree;f=hooks/default-h… -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

2 2

Fwd: [CentOS-devel] [Storage] Mountpoint.io: Software Defined Storage event in Vancouver in August
by Sandro Bonazzola 17 May '18

17 May '18

FYI ---------- Forwarded message ---------- From: Rich Bowen <rbowen(a)redhat.com> Date: 2018-05-16 21:47 GMT+02:00 Subject: [CentOS-devel] [Storage] Mountpoint.io: Software Defined Storage event in Vancouver in August To: "The CentOS developers mailing list." <centos-devel(a)centos.org> Forwarding on an announcement from a colleague, for those of you interested in Software-defined Storage: Our first mountpoint is coming! Software-defined Storage (SDS) is changing the traditional way we think of storage. Decoupling software from hardware allows you to choose your hardware vendors and provides enterprises with more flexibility. Attend mountpoint on August 27 - 28, 2018 in Vancouver, BC, before Open Source Summit North America for this first time event. We are joining forces with the Ceph and Gluster communities, SDS experts, and partners to bring to you an exciting 2 day event. Help lead the conversation on open source software defined storage and share your knowledge! Our CFP is open on May 3rd through June 15th, 2018. More details available, including sponsorship: https://mountpoint.io/ -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166 _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org https://lists.centos.org/mailman/listinfo/centos-devel -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

Re: Mailing-Lists upgrade
by Marc Dequènes (Duck) 17 May '18

17 May '18

I forgot to cross-post to other lists. Please read announcement below. On 05/08/2018 12:45 PM, Marc Dequènes (Duck) wrote: > Quack, > > On 04/28/2018 09:34 AM, Marc Dequènes (Duck) wrote: > >> A few months ago we had to rollback the migration because of a nasty >> bug. This is fixed in recent versions of Mailman 3 so we're rescheduling >> it on Tuesday 8th during the slot 11:00-12:00 JST. > > Just a word to say the migration happened and no problem was detected. > > The archive posts reindexation is not finished yet, and greylisting is > slowing down things a bit, but it should soon be over. Some information > like post count and little graphs in the web UI are handled via regular > cron jobs and should also soon be accurate. > > Old links to the archives, for pre-migration posts, are still working. > Posts URLS were not stable in Mailman 2 but been synced in > https://lists.ovirt.org/pipermail/ > > You can contact me directly by mail or IRC, or open a JIRA ticket if you > hit any problem. > > \_o< >

9 20

ovirt-engine travis CI
by Sandro Bonazzola 16 May '18

16 May '18

Hi, today I pushed a fix for Travis CI on oVirt Engine. While discussing the fix it has been asked why we need Travis CI in first place, isn't our Jenkins testing enough? Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

4 6

[ANN] introducing ovirt-openshift-extensions
by Roy Golan 15 May '18

15 May '18

Hi all, Running Openshift on oVirt seems more and more attractive and is starting to get attention. It is very easy to do so today without needing any special configuration, however, to tighten the integration and to take advantage of the underlying infra provider(ovirt) we can do better. For example, oVirt can connect various storage providers, and serve disk space to containers[1][2]. Also, Openshift can ask oVirt for VMs and deploy them as master or application nodes for its usage, without making the administrator doing all that manually. This project[1] is the home for the ovirt-flexvolume-driver and ovirt-provisioner[3] and merging ovirt-cloudprovider[4] is a work in progress. The code under this repository is work-in-progress and moving quickly, however, it has automation (stdci v2 :)) and is working and does at least what you observe in the demo videos. Yet I highly appreciate if any of you that will try will provide feedback be that #ovirt channel/ mailing list or to report bugs directly in the Github project page <https://github.com/oVirt/ovirt-openshift-extensions> [1] https://github.com/oVirt/ovirt-openshift-extensions [2] https://ovirt.org/blog/2018/02/your-container-volumes-served-by-ovirt/ [3] https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/ [4] https://github.com/rgolangh/ovirt-k8s-cloudprovider Thanks, Roy

1 0

Terraform provider for oVirt
by Sandro Bonazzola 15 May '18

15 May '18

Hi, just following up from twitter[1], if any developer within oVirt knows about Terraform, there's interest on their side for collaboration developing a provider. For more info, see the github issue: https://github.com/hashicorp/terraform/issues/16150 [1] https://twitter.com/jepeltw/status/955647436931858432 -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

3 7

Uploaded ISO images
by Sandro Bonazzola 14 May '18

14 May '18

Hi, Just noticed that when I upload an ISO into a data domain from the browser, the content is detected as ISO but once upload finishes it's listed as Type:Image. Shouldn't it be Type:ISO? Software Version:4.2.3.5-1.el7.centos Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

4 7

Propose Dominik Holler as a Network-Backend Maintainer
by Alona Kaplan 14 May '18

14 May '18

Hi all, Dominik Holler has been working on the oVirt project for more than 1.5 years. To share some of Dominik's great stats - ~ 120 patches related to the network backend/ui ~ 95 patches for ovirt-provider-ovn ~ 44 vdsm patches ~ 80 bug fixes He was the feature owner of 'auto sync network provider', 'lldp-reporting' and 'network-filter-parameters'. For the last few months Dominik is helping review network-backend related patches and is doing a great and thorough work. Dominik showed a deep understanding of all the parts of code that he touched or reviewed. He learns fast, thorough and uncompromising. I've reviewed most of Dominik's engine related work (code and reviews). I trust his opinion and think he will be a good addition to the maintainers team. I would like to propose Dominik as a Network backend maintainer. Thanks, Alona.

10 12

[ANNOUNCE] Introducing STDCI V2
by Barak Korren 13 May '18

13 May '18

The CI team is thrilled to announce the general availability of the second version of the oVirt CI standard. Work on this version included almost a complete rewrite of the CI backend. The major user-visible features are: - Project maintainers no longer need to maintain YAML in the ‘jenkins’ repository. Details that were specified there, including targeted distributions, architectures and oVirt versions should now be specified in a YAML file under the project’s own repository (In a different syntax). - We now support “sub stages” which provide the ability to run multiple different scripts in parallel within the same STDCI stage. There is also a conditional syntax which allows controlling which scripts get executed according to which files were changed in the patch being tested. - The STDCI script file names and locations can now be customized via the above mentioned YAML file. This means that for e.g. using the same script for different stages can now be done by assigning it to the stages in the YAML file instead of by using symlinks. Inspecting job results in STDCI V2 ---------------------------------- As already mentioned, the work on STDCI V2 consisted of a major rewrite of the CI backend, one of the changes made is switching from using multiple “FreeStyle” type jobs per project to just two (pre-merge and post-merge) pipeline jobs. This has implications for the way job results are to be inspected. Since all the different parallel tasks now happen within the same job, looking at the job output can be rather confusing as it includes the merged output of all the tasks. Instead, the “Blue Ocean” view should be used. The “Blue Ocean” view displays a graphical layout of the job execution allowing one to quickly learn which parts of the job failed. It also allows drilling down and viewing the logs of individual parts of the job. Apart from using the “Blue Ocean” view, job logs are also stored as artifact files. The ‘exported-artifacts’ directory seen in the job results will now include different subdirectories for the different parts of the job. Assuming we have a ‘check-patch’ stage script running on ‘el7/x86_64’, we can find its output under ‘exported-artifacts’ in: check-patch.el7.x86_64/mock_logs/script/stdout_stderr.log Any additional artifacts generated by the script would be present in the ‘check-patch.el7.x86-64’ directory as well. I have a CI YAML file in my project already, is this really new? ---------------------------------------------------------------- We’ve been working on this for a while, and occasionally introduced V2 features into individual projects as needed. In particular, our GitHub support was always based on STDCI V2 code, so all GitHub projects (except Lago, which is ‘special’…) are already using STDCI V2. A few Gerrit-based projects have already been converted to V2 as well as part of our efforts to test and debug the V2 code. Most notably, the “OST” and “Jenkins” projects have been switched, although they are running the STDCI V1 jobs as well for the time being. What is the process for switching my project to STDCI V2? --------------------------------------------------------- The CI team is going to proactively work with project maintainers to switch them to V2. The process for switching is as follows: - Send a one-line patch to the ‘jenkins’ repo to enable the V2 jobs for the project - at this point the V2 jobs will run side-by-side with the V1 jobs, and will execute the STDCI scripts on el7/x86_64. - Create an STDCI YAML file to define the target distributions, architectures and oVirt versions for the project. (See below for a sample file that would be equivalent to what many projects have defined in V1 currently). As soon as a patch with the new YAML file is submitted to the project, the V2 job will parse it and follow the instructions in it. This allows for an easy verification of the file functionality in CI. - Remove the STDCI V1 job configuration from the ‘jenkins’ repo. This should be the last patch project maintainers have to send to the ‘jenkins’ repo. What does the new YAML file look like? -------------------------------------- We defined multiple optional names for the file, so that each project owner can choose which name seems most adequate. The following names can be used: - stdci.yaml - automation.yaml - ovirtci.yaml A dot (.) can also optionally be added at the beginning of the file name to make the file hidden, the file extension could also be “yml”. If multiple matching files exist in the project repo, the first matching file according to the order listed above will be used. The file conforms to the YAML syntax. The key names in the file are case-agnostic, and hyphens (-) underscores (_) and spaces ( ) in key names are ignored. Additionally we support multiple forms of the same word so you don’t need to remember if the key should be ‘distro’, ‘distros’, ‘distributions’, ‘operating-systems’ or ‘OperatingSystems’ as all these forms (and others) will work and mean the same thing. To create complex test/build matrices, ‘stage’, ‘distribution’, ‘architecture’ and ‘sub-stage’ definitions can be nested within one another. We find this to be more intuitive than having to maintain tedious ‘exclude’ lists as was needed in V1. Here is an example of an STDCI V2 YAML file that is compatible with the current master branch V1 configuration of many oVirt projects: --- Architectures: - x86_64: Distributions: [ "el7", "fc27" ] - ppc64le: Distribution: el7 - s390x: Distribution: fc27 Release Branches: master: ovirt-master Note: since the file is committed into the project’s own repo, having different configuration for different branches can be done by simply having different files in the different branches, so there is no need for a big convoluted file to configure all branches. Since the above file does not mention stages, any STDCI scripts that exists in the project repo and belong to a particular stage will be run on all specified distribution and architecture combinations. Since it is sometimes desired to run ‘check-patch.sh’ on less platforms then build-artifacts for example, a slightly different file would be needed: --- Architectures: - x86_64: Distributions: [ “el7”, “fc27” ] - ppc64le: Distribution: el7 - s390x: Distribution: fc27 Stages: - check-patch: Architecture: x86_64 Distribution: el7 - build-artifacts Release Branches: master: ovirt-master The above file makes ‘check-patch’ run only on el7/x86_64, while build-artifacts runs on all platforms specified and check-merged would not run at all because it is not listed in the file. Great efforts have been made to make the file format very flexible but intuitive to use. Additionally there are many defaults in place to allow specifying complex behaviours with very brief YAML code. For further details about the file format, please see the documentation linked below. About the relation between STDCI V2 and the change-queue -------------------------------------------------------- In STDCI V1 the change queue that would run the OST tests and release a given patch was determined by looking at the “version” part of the name of the project’s build-artifacts jobs that got invoked for the patch. This was confusing for people as most people understood “version” to mean the internal version for their own project rather then the oVirt version. In V2 we decided to be more explicit and simply include a map from branches to change queues in the YAML configuration under the “release-branches” option, as can be seen in the examples above. We also chose to no longer allow specifying the oVirt version as a shorthand for the equivalent queue name (E.g specifying ‘4.2’ instead of ‘ovirt-4.2’), this should reduce the chance for confusing between project versions and queue names, and also allows us to create and use change queues for projects that are not oVirt. A project can choose not to include a “release-branches” option, in which case its patches will not get submitted to any queues. Further information ------------------- The documentation for STDCI can be found at [1]. The documentation update for V2 are still in progress and expected to be merged soon. In the meatine, the GitHub-specific documentation [2] already provides a great deal of information which is relevant for V2. [1]: http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards [2]: http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub --- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

3 4

[ OST Failure Report ] [ oVirt Master (otopi+imgbased) ] [ 11-05-2018 ] [ 001_initialize_engine.test_initialize_engine ]
by Dafna Ron 11 May '18

11 May '18

Hi, We are failing in 001_initialize_engine.test_initialize_engine in the upgrade suite. the issue seems to be related to ovn configuration. The changes reported by CQ are not the cause of this failure and I may be mistaken but I suspect it may be related to one of the below changes. *Link and headline of suspected patches: * *https://gerrit.ovirt.org/#/c/90784/ <https://gerrit.ovirt.org/#/c/90784/> - network: default ovn provider client is returned by fixturehttps://gerrit.ovirt.org/#/c/90327/ <https://gerrit.ovirt.org/#/c/90327/> - backend, packing: Add default MTU for tunnelled networksLink to Job:* *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/>* http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ *Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact…>(Relevant) error snippet from the log: <error>* 2018-05-11 04:14:34,940-0400 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/network/ovirtproviderovn.py", line 779, in _customization self._query_install_ovn() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/network/ovirtproviderovn.py", line 399, in _query_install_ovn default=True File "/usr/lib/python2.7/site-packages/ovirt_setup_lib/dialog.py", line 47, in queryBoolean default=true if default else false, File "/usr/share/otopi/plugins/otopi/dialog/human.py", line 211, in queryString value = self._readline(hidden=hidden) File "/usr/lib/python2.7/site-packages/otopi/dialog.py", line 248, in _readline raise IOError(_('End of file')) IOError: End of file 2018-05-11 04:14:34,942-0400 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Environment customization': End of file 2018-05-11 04:14:34,972-0400 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: id uid local foreign state pid exe 0: 0 0.0.0.0:111 0.0.0.0:0 LISTEN 1829 /usr/sbin/rpcbind 1: 29 0.0.0.0:662 0.0.0.0:0 LISTEN 1868 /usr/sbin/rpc.statd 2: 0 0.0.0.0:22 0.0.0.0:0 LISTEN 970 /usr/sbin/sshd 3: 0 192.168.201.2:3260 0.0.0.0:0 LISTEN UnknownPID UnknownEXE 4: 0 192.168.200.2:3260 0.0.0.0:0 LISTEN UnknownPID UnknownEXE 5: 0 0.0.0.0:892 0.0.0.0:0 LISTEN 1874 /usr/sbin/rpc.mountd 6: 0 0.0.0.0:2049 0.0.0.0:0 LISTEN UnknownPID UnknownEXE 7: 0 0.0.0.0:32803 0.0.0.0:0 LISTEN UnknownPID UnknownEXE 8: 0 192.168.201.2:22 192.168.201.1:33338 ESTABLISHED 5544 /usr/sbin/sshd 2018-05-11 04:14:34,973-0400 DEBUG otopi.context context.dumpEnvironment:859 ENVIRONMENT DUMP - BEGIN 2018-05-11 04:14:34,973-0400 DEBUG otopi.context context.dumpEnvironment:869 ENV BASE/error=bool:'True' 2018-05-11 04:14:34,973-0400 DEBUG otopi.context context.dumpEnvironment:869 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.IOError'>, IOError('End of file',), <traceback object at 0x239ab90>)]' 2018-05-11 04:14:34,974-0400 DEBUG otopi.context context.dumpEnvironment:873 ENVIRONMENT DUMP - END 2018-05-11 04:14:34,975-0400 INFO otopi.context context.runSequence:741 Stage: Clean up 2018-05-11 04:14:34,975-0400 DEBUG otopi.context context.runSequence:745 STAGE cleanup 2018-05-11 04:14:34,976-0400 DEBUG otopi.context context._executeMethod:128 Stage cleanup METHOD otopi.plugins.otopi.dialog.answer_file.Plugin._generate_answer_file 2018-05-11 04:14:34,977-0400 DEBUG otopi.context context.dumpEnvironment:859 ENVIRONMENT DUMP - BEGIN 2018-05-11 04:14:34,977-0400 DEBUG otopi.context context.dumpEnvironment:869 ENV DIALOG/answerFileContent=str:'# OTOPI answer file, generated by human dialog [environment:default] ' *</error>Thanks, Dafna*

3 3

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 10-05-2018 ] [ 001_upgrade_engine.test_initialize_engine ]
by Dafna Ron 11 May '18

11 May '18

Hi, We are failing on deploying engine (test: 001_upgrade_engine.test_initialize_engine) duet to version bump for package vdsm-jsonrpc. Can you please revert the change or add the missing package? Please note that all ovirt-engine changes are failing and there are a few. *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/91084/ <https://gerrit.ovirt.org/#/c/91084/> - jsonrpc: version bump Link to Job:* *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7281/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7281/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7281/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7281/artifact>(Relevant) error snippet from the log: <error>* [ INFO ] Checking for an update for Setup... [ ERROR ] Yum [u'ovirt-engine-backend-4.3.0-0.0.master.20180509105818.gitf6b5283.el7.centos.noarch requires vdsm-jsonrpc-java >= 1.4.13'] [ INFO ] Yum Performing yum transaction rollback [ ERROR ] Failed to execute stage 'Environment customization': [u'ovirt-engine-backend-4.3.0-0.0.master.20180509105818.gitf6b5283.el7.centos.noarch requires vdsm-jsonrpc-java >= 1.4.13'] [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20180509074146-er3dzr.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20180509074148-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed ("FATAL Internal error (main): [u'ovirt-engine-backend-4.3.0-0.0.master.20180509105818.gitf6b5283.el7.centos.noarch requires vdsm-jsonrpc-java >= 1.4.13']",) lago.ssh: DEBUG: Command f3aaeaac on lago-upgrade-from-release-suite-master-engine errors: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in main installer.execute() File "/usr/lib/python2.7/site-packages/otopi/main.py", line 157, in execute self.context.runSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 771, in runSequence util.raiseExceptionInformation(infos[0]) File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in raiseExceptionInformation exec('raise info[1], None, info[2]') File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py", line 417, in _customization ) = self._checkForProductUpdate() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py", line 248, in _checkForProductUpdate if mpm.buildTransaction(): File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 920, in buildTransaction raise yum.Errors.YumBaseError(msg) YumBaseError: [u'ovirt-engine-backend-4.3.0-0.0.master.20180509105818.gitf6b5283.el7.centos.noarch requires vdsm-jsonrpc-java >= 1.4.13'] *</error>*

4 11

Jupiter isn't just a planet - it's how we test things in the Engine
by Allon Mureinik 10 May '18

10 May '18

Hi all, Over the past couple of days I've merged a series of patches that upgrade the Engine's usage of JUnit to JUnit Jupiter 5.2 in order to make it easier to write new tests. Despite the patches being quite straight-forward, since Jupiter is **not** backwards compatible to JUnit 4, or even JUnit 5 Vintage, here's the short version of what you need to know: 1. You no longer use annotations from the org.junit package, but the junit.org.jupiter.api packages. @Before and @After have been replaced with @BeforeEach and AfterEach respectively, and @BeforeClass and @AfterClass have been replaced with @BeforeAll and @AfterAll. 2. Assertions now live in the org.junit.jupiter.api.Assertions class. Note that the optional message parameter is now the **last** parameter in all the assertions, not the first. Also worth noting that assertThat has been removed. More often than not, assertTrue can be used with a Supplier<Boolean>, but if you absolutely need an assertThat method, just use the one that Hamcrest provides. 3. Similarly, assumptions live in org.junit.jupiter.api.Assumptions. 4. No more runners - extending tests in JUnit Jupiter is done with Extensions. There's no longer a need for the Parameterized and Theories runners, as you can just use the built-in @ParameterizedTest annotation. Instead of the MockitoJUnitRunner we used to heavily rely on, you should now use MockitoExtension. 5. No more Rules - these too were replaced with extensions. Our custom rules were replaced with extensions, which are pretty well documented both in their javadoc and in wiki under [1] For additional information, you could take a look at the official documentation [2] Happy testing! Allon [1] https://ovirt.org/develop/dev-process/unit-testing-utilities/ [2] https://junit.org/junit5/docs/current/user-guide/

1 0

Jupiter isn't just a planet - it's how we test things in the Engine
by Allon Mureinik 10 May '18

10 May '18

Hi all, Over the past couple of days I've merged a series of patches that upgrade the Engine's usage of JUnit to JUnit Jupiter 5.2 in order to make it easier to write new tests. Despite the patches being quite straight-forward, since Jupiter is **not** backwards compatible to JUnit 4, or even JUnit 5 Vintage, here's the short version of what you need to know: 1. You no longer use annotations from the org.junit package, but the junit.org.jupiter.api packages. @Before and @After have been replaced with @BeforeEach and AfterEach respectively, and @BeforeClass and @AfterClass have been replaced with @BeforeAll and @AfterAll. 2. Assertions now live in the org.junit.jupiter.api.Assertions class. Note that the optional message parameter is now the **last** parameter in all the assertions, not the first. Also worth noting that assertThat has been removed. More often than not, assertTrue can be used with a Supplier<Boolean>, but if you absolutely need an assertThat method, just use the one that Hamcrest provides. 3. Similarly, assumptions live in org.junit.jupiter.api.Assumptions. 4. No more runners - extending tests in JUnit Jupiter is done with Extensions. There's no longer a need for the Parameterized and Theories runners, as you can just use the built-in @ParameterizedTest annotation. Instead of the MockitoJUnitRunner we used to heavily rely on, you should now use MockitoExtension. 5. No more Rules - these too were replaced with extensions. Our custom rules were replaced with extensions, which are pretty well documented both in their javadoc and in wiki under [1] For additional information, you could take a look at the official documentation [2] Happy testing! Allon [1] https://ovirt.org/develop/dev-process/unit-testing-utilities/ [2] https://junit.org/junit5/docs/current/user-guide/

1 0

CentOS 7.5.1804 is now officially available
by Sandro Bonazzola 10 May '18

10 May '18

FYI, CentOS 7.5.1804 is now officially available. See announce here: https://lists.centos.org/pipermail/centos-announce/2018-May/022829.html Users: I suggest to upgrade in order to get latest features, fixes and security fixes. Just a note for ppc64le users, there's a known bug with libguestfs requiring qemu-kvm-ma instead of qemu-kvm that may cause upgrade issues. This should be fixed in next update which should land in CentOS in ~2 weeks. If you are still on 4.1, please change your centos repos to point to http://mirror.centos.org/centos/7.4.1708/ instead of http://mirror.centos.org/centos/7. Then please update to latest 4.1 and then to oVirt 4.2 + CentOS 7.5 as soon as you can. Devel: please cross check your jenkins jobs, especially those having to do something with 4.1 since CentOS 7.5 is not supporting oVirt 4.1 anymore. See above. Infra: please schedule a mass update of oVirt infrastructure to CentOS 7.5 + oVirt 4.2.3 ASAP. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

3 5

Work-Around for Access Problem to resources.ovirt.org and jenkins.ovirt.org
by Anton Marchukov 09 May '18

09 May '18

Hello All. Please note that ovirt.org got HSTS setting enabled. The way this change was rolled was not authorised by us. The setting contains “includeSubDomains” parameter that ask browser to access all resources inside *.ovirt.org using https://. The problem is that not all resources on *.ovirt.org are https-enabled. And this will prevent you from being able to access http://resources.ovirt.org http://jenkins.ovirt.org This setting is cached in your browser and then applied with no exceptions even if you explicitly specify http:// the browser will rewrite to https and then connection to above mentioned resources will fail. The only immediate work-around for you is to clear the HSTS flag in your browser, please find the instructions for Firefox and Chrome [1]. Please note that you will get that setting back by visiting ovirt.org website until we clear it from there. We are currently working on this setting to be soften or disabled till all resources are https enabled that is also in progress. This is only related to access via the web browser. Accessing using yum or automated scripts should work fine as they usually do not observe and cache HSTS. Anton. [1] https://www.thesslstore.com/blog/clear-hsts-settings-chrome-firefox/

3 2

Please update your Fedora
by Sandro Bonazzola 09 May '18

09 May '18

Hi, if you're not yet on Fedora 28, please consider updating to it. On master we are aiming to support Fedora 28 and we are dismissing any older Fedora jobs in Jenkins soon. As a reminder Fedora 26 support is going to be EOL on Tuesday, May 29th, 2018. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

2 1

Fwd: [JIRA] (OVIRT-2005) jira.ovirt.org redirect doesn't work anymore, redirects instead to https://jira.ovirt.org/ovirt.apps/
by Eyal Edri 09 May '18

09 May '18

FYI, It seems jira.ovirt.org redirect doesn't work, since we don't own the jira instance ( cloud provided by Attlasian ) it might be a change done on their side. We'll investigate and check possible solutions. Until then, please use the full URL for the JIRA instance - https://ovirt-jira.atlassian.net ---------- Forwarded message ---------- From: eyal edri (oVirt JIRA) <jira(a)ovirt-jira.atlassian.net> Date: Wed, May 9, 2018 at 10:11 AM Subject: [JIRA] (OVIRT-2005) jira.ovirt.org redirect doesn't work anymore, redirects instead to https://jira.ovirt.org/ovirt.apps/ To: infra(a)ovirt.org [ https://ovirt-jira.atlassian.net/browse/OVIRT-2005?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2005: Epic Link: OVIRT-403 jira.ovirt.org redirect doesn't work anymore, redirects instead to https://jira.ovirt.org/ovirt.apps/ Key: OVIRT-2005 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2005 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri Assignee: infra Priority: High [~ederevea] any idea what could cause this? maybe Atlassian blocked us or IP was changed? cc [~ena(a)redhat.com] [~bkorren(a)redhat.com] — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083) _______________________________________________ Infra mailing list -- infra(a)ovirt.org To unsubscribe send an email to infra-leave(a)ovirt.org -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

oVirt Orb 4.2.3 is now available
by Sandro Bonazzola 09 May '18

09 May '18

oVirt Orb image has been updated with oVirt 4.2.3 content[1] oVirt Orb is a project that allows anyone to easily take an oVirt for a ride, test and play with it. See oVirt Orb documentation for using it[2] [1] http://resources.ovirt.org/pub/ovirt-4.2/ovirt-orb/ [2] https://ovirt.org/documentation/ovirt-orb/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

3 5

Tracking down a vdsm memory leak
by Chris Adams 08 May '18

08 May '18

I have a problem with a memory leak in vdsm. I have a dev cluster that right now is: - two nodes - CentOS 7.4 (up to date) - oVirt 4.2.2 (installed as 3.5 and upgraded version by version) - hosted engine (no other running VM at the moment) - iSCSI storage I have a script that writes the vdsm RSS to a file every five minutes, and on the node holding the hosted engine, vdsm RSS grows around 300-1500KB every snapshot. I maintain several oVirt clusters for others, and they all seem to have this problem. The production clusters are all still on oVirt 4.1, but they all have this problem too, so I guess it is something about how I set them up? On a couple I just checked, the vdsm RSS is over 1G. Any tips on instrumenting vdsm to track this down? I am unfortunately only passingly familiar with python (I can make small changes, but not knowledgeable enough to figure this out). -- Chris Adams <cma(a)cmadams.net>

3 8

oVirt messages from engine to vdsm
by Anastasiya Ruzhanskaya 08 May '18

08 May '18

Hello everyone! Currently I want to determine what information is included in messages passing from oVirt engine to VDSM on ovirt-node. I made up a really simple configuration with one VM representing engine, another - node, a managed to successfully launch a single VM on this node. However, I have chosen to configure everything automatically. Currently traffic is encrypted with default certificates. So, there are three options for me and no one of them really works. 1) Find the format of messages ( what the fields are, session id for example) in docs, but I didn't manage to find it; 2) Use wireshark to decrypt the traffic and the apply maybe a json -dissector to the decrypted data. I have tried many solutions ( thanks god I have rsa private and public keys but there is another session key which is generated every time engine starts to communicate with vdsm, which I cannot get with the help of sslkeylog file or ld_preload technology. Maybe someone knows the exact methodology how to do this correctly? 3) Turn off ssl in oVirt. It is simple to do that for vdsm, but for engine, according to answers on oVirt site, I should do 2 requests to the database. I was really surprised that psql was not installed by oVirt on my system. How did it then created a default database? ( I have chosen to create all locally and with default configurations). I mean these two commands : https://www.ovirt.org/develop/ developer-guide/vdsm/connecting-development-vdsm-to-engine/ . I have a following error there : psql: FATAL: Peer authentication failed for user "engine" Could you please guide my what method is the best and how should I correct my faults there?

3 10

OST: oVirt version used in basic-suite-4.2
by Milan Zamazal 07 May '18

07 May '18

Hi, I wonder why is ovirt-4.2 repo, rather than ovirt-4.2-snapshot or so, used in reposync-config for basic-suite-4.2? Packages in ovirt-4.2 are relatively old and the suite may fail on bugs that are already fixed. Shouldn't a more up-to-date repo be used in basic-suite-4.2? Thanks, Milan

3 3

ovirt-host-deploy and python3
by Tomáš Golembiovský 07 May '18

07 May '18

Hi, I'm trying to reinstall a CentOS host (using master-snapshot) and I noticed otopi is trying to use python3 while the ovirt-host-deploy is not yet fully python3 compatible: > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:39 SYSTEM INFORMATION - BEGIN > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:40 executable /bin/python3 > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:41 python version 3.4.8 (default, Mar 23 2018, 10:04:27) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:42 python /bin/python3 > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:43 platform linux > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:44 distribution ('CentOS Linux', '7.4.1708', 'Core') > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:45 host 'ovirt-host2' > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:51 uid 0 euid 0 gid 0 egid 0 > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:53 SYSTEM INFORMATION - END and then later: > 2018-05-03 21:35:56,912+0200 DEBUG otopi.context context._executeMethod:128 Stage init METHOD otopi.plugins.ovirt_host_deploy.node.detect.Plugin._init > 2018-05-03 21:35:56,914+0200 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-a0GNITSwX9/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-a0GNITSwX9/otopi-plugins/ovirt-host-deploy/node/detect.py", line 131, in _init > odeploycons.FileLocations.OVIRT_NODE_VARIANT_VAL) > File "/tmp/ovirt-a0GNITSwX9/otopi-plugins/ovirt-host-deploy/node/detect.py", line 69, in hasconf > io.StringIO('[default]\n' + f.read().decode('utf-8')) > AttributeError: 'str' object has no attribute 'decode' > 2018-05-03 21:35:56,915+0200 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Initializing': 'str' object has no attribute 'decode' There is definitely a bug (or at least weirdness) in host-deploy -- why use .decode() on object returned by codecs.open()? But also, should host-deploy be already python3 compatible and is this otopi behaviour expected? Tomas -- Tomáš Golembiovský <tgolembi(a)redhat.com>

6 12

oVirt RPC messages
by Anastasiya Ruzhanskaya 07 May '18

07 May '18

Hello! Do messages sent from ovirt-engine to ovirt-node in RPC format contain the session number or any user information?

2 3