- Devel - oVirt List Archives

VDSM review & development tools
by Martin Polednik 07 Dec '16

07 Dec '16

Hello developers, this e-mail is mostly aimed at VDSM contributors (current and potential) and should serve as continuation of the idea started at our weekly meeting. We've had a proposal of moving the project to github[1] and using reviewable[2] as a code review due to github's code review interface. I would like to start a *discussion* regarding how we would like to develop VDSM in future. So far, the suggested options were (1st implied): 1) gerrit (stay as we are), 2) github & reviewable, 3) mailing list. What would be your favorite review & development tool and why? Do you hate any of them? Let the flamewar^Wconstructive discussion begin! :) <subjective part> My preferred tool is mailing list with the main tree mirrored to github. Why mailing list in 2016 (almost 2017)? a) stack - We're built on top of libvirt, libvirt is built on top of qemu and qemu utilizes kvm which is a kernel module. Each of this projects uses mailing lists for development. b) tooling - Everyone is free to use tools of choice. Any sane e-mail client can handle mailing list patches, and it's up to reviewers to choose the best way to handle the review. As for sending the patches, there is the universal fallback in the form of git-send-email. c) freedom - It's up to us to decide how would we handle such development. As many system-level projects already use mailing lists (see a), there is enough inspiration for workflow design[3]. d) accessibility - VDSM is in unfortunate position between "cool", high level projects and "boring" low level projects. I believe that we should be more accessible to the developers from below the stack rather than to general public. Having unified workflow that doesn't require additional accounts and is compatible with their workflows makes that easier. </subjective part> [1] https://github.com/ [2] https://reviewable.io/ [3] e.g. https://www.kernel.org/doc/Documentation/SubmittingPatches Regards, mpolednik

3 2

ovirt_4.0_he-system-tests job failed
by Shlomo Ben David 07 Dec '16

07 Dec '16

Hi, The [1] job failed with the following error: 2016-12-07 02:40:43,805::ssh.py::ssh::96::lago.ssh::DEBUG::Command 8b25fff2 on lago-he-basic-suite-4-0-host0 errors: Error: Package: ovirt-hosted-engine-setup-2.0.4.2-0.0.master.20161201083322.gita375924.el7.centos.noarch (alocalsync) Requires: ovirt-engine-sdk-python >= 3.6.3.0 [1] - http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/584/console Best Regards, Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

3 2

test-repo_ovirt_experimental_4.0
by Shlomo Ben David 07 Dec '16

07 Dec '16

Hi All, The [1] job is failing with the following error: *+ yum install --nogpgcheck -y --downloaddir=/dev/shm ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' Error: Package: ovirt-engine-cli-3.6.9.3-0.1.20161202.git61c5da9.el7.centos.noarch (alocalsync) Requires: ovirt-engine-sdk-python >= 3.6.0.0 [0m [36m * [Thread-4] Deploy VM lago-basic-suite-4-0-engine: [31mERROR [0m (in 0:01:51) [0m [31mError while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1242, in _deploy_host host.name <http://host.name>(), RuntimeError: /home/jenkins/workspace/test-repo_ovirt_experimental_4.0/ovirt-system-tests/deployment-basic-suite-4.0/default/scripts/_home_jenkins_workspace_test-repo_ovirt_experimental_4.0_ovirt-system-tests_basic-suite-4.0_.._common_deploy-scripts_setup_engine.sh failed with status 1 on lago-basic-suite-4-0-engine [0m [36m # Deploy environment: [31mERROR [0m (in 0:01:51) [0m [36m@ Deploy oVirt environment: [31mERROR [0m (in 0:01:51) [0m [31mError occured, aborting Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 264, in do_run self.cli_plugins[args.ovirtverb].do_run(args) File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run self._do_run(**vars(args)) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 489, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 500, in wrapper return func(*args, prefix=prefix, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 187, in do_deploy prefix.deploy() File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 621, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line 67, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 198, in deploy return super(OvirtPrefix, self).deploy() File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 621, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1249, in deploy self._deploy_host, self.virt_env.get_vms().values() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 97, in invoke_in_parallel vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1242, in _deploy_host host.name <http://host.name>(), RuntimeError: /home/jenkins/workspace/test-repo_ovirt_experimental_4.0/ovirt-system-tests/deployment-basic-suite-4.0/default/scripts/_home_jenkins_workspace_test-repo_ovirt_experimental_4.0_ovirt-system-tests_basic-suite-4.0_.._common_deploy-scripts_setup_engine.sh failed with status 1 on lago-basic-suite-4-0-engine [0m * [1] - http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3416/console Could you please check this issue? Thanks in advanced, Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

3 6

Re: [ovirt-devel] ovirt-appliance (today) is 1.5G...
by Ryan Barry 06 Dec '16

06 Dec '16

We may also want to do this with Node/RHV-H eventually (since the updates there are already 500MB). I don't think we currently ship deltarpm on RHV-H, but it's a very small addition. The question is whether makedeltarpm can actually do anything meaningful with something which is already a sparsified image wrapped in an RPM, but I'll test... On Sun, Oct 9, 2016 at 6:35 AM, Doron Fediuck <dfediuck(a)redhat.com> wrote: > FYI > > ---------- Forwarded message ---------- > From: Yaniv Kaul <ykaul(a)redhat.com> > Date: Thu, Oct 6, 2016 at 11:13 AM > Subject: [ovirt-devel] ovirt-appliance (today) is 1.5G... > To: devel <devel(a)ovirt.org> > > > I'm sure it was less just days ago, but now[1] it is again quite big. > 4.0's is 'only' 1G in size[2]. > Which anyway raises the question - should we provide delta RPMs for it? > > Thanks, > Y. > > [1] http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm > /el7/noarch/ovirt-engine-appliance-4.1-20160927.1.el7.centos.noarch.rpm > [2] http://resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm/el > 7/noarch/ovirt-engine-appliance-4.0-20161003.1.el7.centos.noarch.rpm > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > >

2 2

master/4.1 now requires el7.3 for 4.1 Cluster Level
by Michal Skrivanek 06 Dec '16

06 Dec '16

Dear developers, patch requiring 7.3-based qemu-kvm machine type[1] has been merged to master For using the 4.1 Cluster Level please make sure you have qemu-kvm-rhev 2.6 and libvirt 2.0+ on RHEL 7.3, CentOS 7.3 prerelase repo ([2], I suppose[3] too, and [4]), or Fedora 24+virt-preview repo If you are unable to update your hosts please do use 4.0 compatibility clusters Also note that previous 4.1 or master deployments, including oVirt 4.1 beta from last week, do not properly update the machine type in 4.1 clusters, so please update that manually in the db Thanks, michal [1] https://gerrit.ovirt.org/#/c/65979/ [2] http://buildlogs.centos.org/c7.1611.00/ [3] http://buildlogs.centos.org/c7.1611.01/ [4] https://cbs.centos.org/koji/buildinfo?buildID=13884

2 3

planned jenkins restart
by Evgheni Dereveanchin 05 Dec '16

05 Dec '16

Hi everyone, I am going to restart Jenkins in order to update several plugins. No new builds will be scheduled during this maintenance period. I will announce you once it is finished. Regards, Evgheni Dereveanchin

1 1

master is broken - can't add host - due to vdsm/gluster/__init__.pyc conflicts
by Yaniv Kaul 05 Dec '16

05 Dec '16

Getting: file /usr/lib/python2.7/site-packages/vdsm/gluster/__init__.pyc conflicts between attempted installs of vdsm-python-4.18.999-1059.git63f9e2f.el7.centos.noarch and vdsm-4.18.999-1059.git63f9e2f.el7.centos.x86_64 Thanks, Y.

5 7

[Call to Action] packaging for your preferred distribution
by Sandro Bonazzola 05 Dec '16

05 Dec '16

Hi, we released oVirt 4.1 beta last week providing RPMs for latest Red Hat Enterprise Linux release and its derivatives like CentOS Linux and Scientific Linux and Fedora or similar distributions. Virt support for Fedora is provided as tech preview / best effort being Fedora so fast moving which is too difficult to stay aligned with. We have still 2 months to GA so if you'd like to get oVirt 4.1 on your preferred distribution and you've packaging skills, this is a good chance to start packaging it playing with 4.1 beta released code. You can find some information about porting oVirt to your preferred distribution starting from [1] [1] https://www.ovirt.org/develop/developer-guide/porting-ovirt/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Call to Action] oVirt 4.1 translation
by Sandro Bonazzola 05 Dec '16

05 Dec '16

Hi, we released 4.1 beta 1 last week and we're going fast toward the GA currently scheduled for January 24th[1]. We have a scheduled string freeze on December 21st to allow translators to complete the translations but looking at zanata[2] I think it's time to go there and start translating to your preferred language. [1] http://www.ovirt.org/develop/release-management/releases/4.1/release-manage… [2] https://translate.zanata.org/project/view/ovirt?dswid=9807 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Re: [ovirt-devel] Experimental Flow for Master Fails to Run a VM
by Yaniv Kaul 04 Dec '16

04 Dec '16

On Dec 4, 2016 10:57 PM, "Eyal Edri" <eedri(a)redhat.com> wrote: tests are back to stable, but with a cost of not testing 4.1 CL. DC level. But we are not explicitly using any of the 4.1 features for the time being. (I'd like to believe implictly we did, qcow2v3 for example). Iets hope we get centos 7.3 soon. Indeed - but we also need virt-builder image for it. Y. On Dec 4, 2016 22:41, "Yaniv Kaul" <ykaul(a)redhat.com> wrote: > > > On Dec 4, 2016 6:42 PM, "Arik Hadas" <ahadas(a)redhat.com> wrote: > > Yaniv will try to lower the cluster level used in the system-tests to 4.0 > - this is supposed to solve the issue. > > > Done. > Y. > > If it won't help (we will know it in about an hour), we'll add a db-script > that changes the rng device of the blank template only. > > On Sun, Dec 4, 2016 at 3:34 PM, Eyal Edri <eedri(a)redhat.com> wrote: > >> FYI, >> >> I opened a bug [1] to track this issue since I don't see any attempts to >> resolve the issue on the thread, hopefully a bug will get more attention. >> Opened on VDSM since we see the libvirt error there, feel free to move >> product/team. >> >> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1401303 >> >> On Sun, Dec 4, 2016 at 1:23 PM, Eyal Edri <eedri(a)redhat.com> wrote: >> >>> Not sure if relevant, but Juan posted a fix for SDK4 last time it >>> happened ( but different failure on log-collector ): >>> >>> https://gerrit.ovirt.org/#/c/67213/ >>> >>> * Added `urandom` to the `RngSource` enumerated type. >>> >>> On Sun, Dec 4, 2016 at 9:17 AM, Eyal Edri <eedri(a)redhat.com> wrote: >>> >>>> And its still failing from Friday, >>>> Since we don't have official Centos 7.3 repos yet ( hopefully we'll >>>> have it this week, but as of this moment its not published yet ) , we have >>>> to either revert the offending patch >>>> or send a quick fix. >>>> >>>> Right now all experimental flows for master are not working and nightly >>>> rpms are not refreshed with new RPMs. >>>> >>>> >>>> >>>> On Fri, Dec 2, 2016 at 9:41 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: >>>> >>>>> >>>>> >>>>> On Dec 2, 2016 2:11 PM, "Anton Marchukov" <amarchuk(a)redhat.com> wrote: >>>>> >>>>> Hello Martin. >>>>> >>>>> Do by outdated you mean the old libvirt? If so that is that livirt >>>>> available in CentOS 7.2? There is no 7.3 yet. >>>>> >>>>> >>>>> Right, this is the issue. >>>>> Y. >>>>> >>>>> >>>>> Anton. >>>>> >>>>> On Fri, Dec 2, 2016 at 1:07 PM, Martin Polednik <mpolednik(a)redhat.com> >>>>> wrote: >>>>> >>>>>> On 02/12/16 10:55 +0100, Anton Marchukov wrote: >>>>>> >>>>>>> Hello All. >>>>>>> >>>>>>> Engine log can be viewed here: >>>>>>> >>>>>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ma >>>>>>> ster/3838/artifact/exported-artifacts/basic_suite_master.sh- >>>>>>> el7/exported-artifacts/test_logs/basic-suite-master/post-004 >>>>>>> _basic_sanity.py/lago-basic-suite-master-engine/_var_log_ovi >>>>>>> rt-engine/engine.log >>>>>>> >>>>>>> I see the following exception there: >>>>>>> >>>>>>> 2016-12-02 04:29:24,030-05 DEBUG >>>>>>> [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] >>>>>>> (ResponseWorker) [83b6b5d] Message received: {"jsonrpc": "2.0", "id": >>>>>>> "ec254aad-441b-47e7-a644-aebddcc1d62c", "result": true} >>>>>>> 2016-12-02 04:29:24,030-05 ERROR >>>>>>> [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) >>>>>>> [83b6b5d] Not able to update response for >>>>>>> "ec254aad-441b-47e7-a644-aebddcc1d62c" >>>>>>> 2016-12-02 04:29:24,041-05 DEBUG >>>>>>> [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] >>>>>>> (DefaultQuartzScheduler3) [47a31d72] Rescheduling >>>>>>> DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.ref >>>>>>> reshLightWeightData#-9223372036854775775 >>>>>>> as there is no unfired trigger. >>>>>>> 2016-12-02 04:29:24,024-05 DEBUG >>>>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (default >>>>>>> task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] Exception: >>>>>>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: >>>>>>> VDSGenericException: VDSNetworkException: Timeout during xml-rpc call >>>>>>> at org.ovirt.engine.core.vdsbroke >>>>>>> r.vdsbroker.FutureVDSCommand.get(FutureVDSCommand.java:73) >>>>>>> [vdsbroker.jar:] >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> 2016-12-02 04:29:24,042-05 ERROR >>>>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (default >>>>>>> task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] Timeout waiting for >>>>>>> VDSM response: Internal timeout occured >>>>>>> 2016-12-02 04:29:24,044-05 DEBUG >>>>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVD >>>>>>> SCommand] >>>>>>> (default task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] START, >>>>>>> GetCapabilitiesVDSCommand(HostName = lago-basic-suite-master-host0, >>>>>>> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', >>>>>>> hostId='5eb7019e-28a3-4f93-9188-685b6c64a2f5', >>>>>>> vds='Host[lago-basic-suite-master-host0,5eb7019e-28a3-4f93-9 >>>>>>> 188-685b6c64a2f5]'}), >>>>>>> log id: 58f448b8 >>>>>>> 2016-12-02 04:29:24,044-05 DEBUG >>>>>>> [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message] (default >>>>>>> task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] SEND >>>>>>> destination:jms.topic.vdsm_requests >>>>>>> reply-to:jms.topic.vdsm_responses >>>>>>> content-length:105 >>>>>>> >>>>>>> >>>>>>> Please note that this runs on localhost with local bridge. So it is >>>>>>> not >>>>>>> likely to be network itself. >>>>>>> >>>>>> >>>>>> The main issue I see is that the VM run command has actually failed >>>>>> due to libvirt no accepting /dev/urandom as RNG source[1]. This was >>>>>> done as engine patch and according to git log, posted around Mon Nov >>>>>> 28. Also adding Jakub - this should either not happen from engine's >>>>>> point of view or the lago host is outdated. >>>>>> >>>>>> [1] >>>>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ma >>>>>> ster/3838/artifact/exported-artifacts/basic_suite_master.sh- >>>>>> el7/exported-artifacts/test_logs/basic-suite-master/post-004 >>>>>> _basic_sanity.py/lago-basic-suite-master-host0/_var_log_vdsm/vdsm.log >>>>>> >>>>>> >>>>>> Anton. >>>>>>> >>>>>>> On Fri, Dec 2, 2016 at 10:43 AM, Anton Marchukov < >>>>>>> amarchuk(a)redhat.com> >>>>>>> wrote: >>>>>>> >>>>>>> FYI. Experimental flow for master currently fails to run a VM. The >>>>>>>> tests >>>>>>>> times out while waiting for 180 seconds: >>>>>>>> >>>>>>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ >>>>>>>> master/3838/testReport/(root)/004_basic_sanity/vm_run/ >>>>>>>> >>>>>>>> This is reproducible over 23 runs of this happened tonight, sounds >>>>>>>> like a >>>>>>>> regression to me: >>>>>>>> >>>>>>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/ >>>>>>>> >>>>>>>> I will update here with additional information once I find it. >>>>>>>> >>>>>>>> Last successful run was with this patch: >>>>>>>> >>>>>>>> https://gerrit.ovirt.org/#/c/66416/ (vdsm: API: move vm parameters >>>>>>>> fixup >>>>>>>> in a method) >>>>>>>> >>>>>>>> Known to start failing around this patch: >>>>>>>> >>>>>>>> https://gerrit.ovirt.org/#/c/67647/ (vdsmapi: fix a typo in string >>>>>>>> formatting) >>>>>>>> >>>>>>>> Please notes that we do not have gating implemented yet, so >>>>>>>> everything >>>>>>>> that was merged in between those patches might have caused this (not >>>>>>>> necessary in vdsm project). >>>>>>>> >>>>>>>> Anton. >>>>>>>> -- >>>>>>>> Anton Marchukov >>>>>>>> Senior Software Engineer - RHEV CI - Red Hat >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Anton Marchukov >>>>>>> Senior Software Engineer - RHEV CI - Red Hat >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>>> Devel mailing list >>>>>>> Devel(a)ovirt.org >>>>>>> http://lists.ovirt.org/mailman/listinfo/devel >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Anton Marchukov >>>>> Senior Software Engineer - RHEV CI - Red Hat >>>>> >>>>> >>>>> _______________________________________________ >>>>> Devel mailing list >>>>> Devel(a)ovirt.org >>>>> http://lists.ovirt.org/mailman/listinfo/devel >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Devel mailing list >>>>> Devel(a)ovirt.org >>>>> http://lists.ovirt.org/mailman/listinfo/devel >>>>> >>>> >>>> >>>> >>>> -- >>>> Eyal Edri >>>> Associate Manager >>>> RHV DevOps >>>> EMEA ENG Virtualization R&D >>>> Red Hat Israel >>>> >>>> phone: +972-9-7692018 >>>> irc: eedri (on #tlv #rhev-dev #rhev-integ) >>>> >>> >>> >>> >>> -- >>> Eyal Edri >>> Associate Manager >>> RHV DevOps >>> EMEA ENG Virtualization R&D >>> Red Hat Israel >>> >>> phone: +972-9-7692018 >>> irc: eedri (on #tlv #rhev-dev #rhev-integ) >>> >> >> >> >> -- >> Eyal Edri >> Associate Manager >> RHV DevOps >> EMEA ENG Virtualization R&D >> Red Hat Israel >> >> phone: +972-9-7692018 >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> > > >

1 0