March 2016 - Devel - oVirt List Archives

Progress report on Vdsm Debian packaging
by Milan Zamazal 21 May '16

21 May '16

I made progress with Debian packaging of Vdsm. We have all the supporting packages (cpopen, ioprocess, mom, pthreading, safelease, sanlock) in Debian now. I took over maintenance of sanlock Debian package, updated it and made a lot of fixes, including preparing the previously unavailable python-sanlock package. As for Vdsm itself, the package can be installed now and Vdsm can be started. It doesn't work with Engine, which is no big surprise. We can't simply reinstall a Debian host from Engine, so we need to find some way how to initialize the host properly. And it's likely there are distribution specific pieces inside Vdsm and elsewhere. All the package sources, including not yet uploaded Vdsm package, are available on http://git.debian.org . How you can help: - Obviously, we need to make Vdsm hosts working, so any help in this area is welcome. - Reviewing and testing Vdsm Debian package (without actually using it) is also very helpful, I'm sure there are things to fix or improve. - There are some Lintian warnings in the packages, fixing them would be nice. - We should also review Debian patches in the packages, decide what should be changed upstream and report it. - You can help with anything else you consider useful.

4 6

Vdsm api package
by Nir Soffer 29 Apr '16

29 Apr '16

Hi all, In the Vdsm call, we discussed a way to expose vdsm errors to its clients (e.g, engine, hosted engine agent/setup). The idea is to have a vdsmapi package, holding: - errors.py - all public errors - events.py - all events sent by vdsm - client.py - library for communicating with vdsm - schema.py - the client will use this to autogenerate online help and validate messages - schema.yaml - we probably need several files (gluster, events, etc.) This will allow other projects talking with vdsm to do: from vdsmapi import client, errors ... try: client.list(vmId="xxxyyy") except errors.NoSuchVM: ... (this is a fake example, the real api may be different) Engine can build-require vdsmapi, and generate java module with the public errors from vdsmapi/errors.py module, instead of keeping this hardcoded in engine, and updating it every time vdsm adds new public error. Vdsm will use this package when building response to clients. Edi was concerned about sharing the errors module, so maybe we need a package: vdsmapi/ errors/ network.py virt.py storage.py gluster.py We can still expose all the errors via errors/__init__.py, so clients do not have to care about the area of the application the error come from. Thoughts? Nir

5 7

Maintenance Notification: *.ovirt.org Services Today at 18:00 IST (17:00 CET)
by Anton Marchukov 31 Mar '16

31 Mar '16

Hello All. Today at 18:00 IST (17:00 CET) we plan to do hardware upgrades at the datacenter where most of ovirt.org services are hosted. Although we plan to minimize the services downtime, it might still be needed. This does not affect gerrit.ovirt.org but may impact jenkins and other services. The maintenance window is scheduled to last for 2 hours. Anton. -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

1 0

are there any ways to disable the log file?
by zhukaijie 31 Mar '16

31 Mar '16

"Since oVirt 3.5.0 (VDSM 4.16.0), VDSM does not enable the overly verbose libvirt debug logs automatically." from http://www.ovirt.org/develop/developer-guide/vdsm/log-files/. So my problem is. Each running VM has it's command line logged in /var/log/libvirt/qemu/${vmname}. And now I'd like to disable this log function, that is to say, not to record the QEMU command line of VM. So could oVirt or VDSM disable this qemu command line log file just like libvirt debug logs? Thank you.

2 1

[ANN] oVirt 3.6.5 First Release Candidate is now available for testing
by Sandro Bonazzola 31 Mar '16

31 Mar '16

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.5 for testing, as of March 31st, 2016 This release is available now for: * Fedora 22 * Red Hat Enterprise Linux 6.7 * CentOS Linux 6.7 (or similar) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 22 This release is also available with experimental support for: * Debian 8.3 Jessie This release candidate includes the following updated packages: - ovirt-engine - ovirt-engine-reports - ovirt-engine-sdk-python - ovirt-engine-sdk-java - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO will be available soon [2]. * Mirrors[3] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.5/ * 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/3.6.5/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Re: [ovirt-devel] virt-v2v become zombie via python cpopen on error
by Michal Skrivanek 31 Mar '16

31 Mar '16

> On 30 Mar 2016, at 11:49, Richard W.M. Jones <rjones(a)redhat.com> wrote: > > On Wed, Mar 30, 2016 at 12:19:35PM +0300, Shahar Havivi wrote: >> Hi, >> >> We encounter a problem in VDSM project that virt-v2v become zombie task while >> importing vm from vmware. >> When virt-v2v is in 'copy disk' mode and we someone deletes the vm at vmware >> the process hang in read() method, >> I am pretty sure that its not virt-v2v problem because when I run it from the >> shell virt-v2v exit with an error, still maybe someone have an idea.... >> >> I wrote a small python script that encounter the problem: >> >> ---------------------------------------------------------------------------- >> from cpopen import CPopen >> >> env = {'LIBGUESTFS_BACKEND': 'direct'} >> cmd = ['/usr/bin/virt-v2v', '-ic', >> 'vpx://....', '-o', >> 'local', '-os', '/tmp', '-of', 'raw', '-oa', 'sparse', >> '--password-file', '/tmp/passwd', '--machine-readable', 'bbb'] >> p = CPopen(cmd, env=env) >> while p.returncode is None: >> c = p.stdout.read(1) >> print c >> ---------------------------------------------------------------------------- > > An actual zombie task? That would indicate that the parent process > (your Python program) wasn't doing a wait system call. > > I downloaded the cpopen-1.4 program, and it doesn't appear to call any > of the wait*(2) system calls anywhere, so that could be the problem. I suppose the cpopen parameters are not alright…I’m sure vdsm developers can help with that. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-p2v converts physical machines to virtual machines. Boot with a > live CD or over the network (PXE) and turn machines into KVM guests. > http://libguestfs.org/virt-v2v

4 4

oVirt Node Next builds are currently broken
by Fabian Deutsch 31 Mar '16

31 Mar '16

Hey, just a quick heads up that our oVirt Node Next jenkins builds are currently broken. Some of the symptoms are that the installation is failing and that no new updates are available. We are working on a solution. - fabian

1 0

Get Involved with oVirt project! Spring edition
by Sandro Bonazzola 30 Mar '16

30 Mar '16

Hi, Have you got some free time and do you want to get involved in oVirt project? Do you like the idea of having fresh disk images of recent distribution in oVirt Glance repository? You can help us by testing existing online images ensuring they works with cloud-init or creating one yourself and report your success to devel(a)ovirt.org. We'll be happy to upload the images once these are ready. Do you like Debian and do you have some programming or packaging skills? Help us getting Vdsm running on it! We work on inclusion of Vdsm into Debian. We need to test and fix Vdsm Debian packages to make them working before the next Debian freeze. You can find all current Debian work (Vdsm and related packages) in Debian git repositories [10]. You can follow the progress and participate on oVirt development mailing list [11]. Here are some bugs you can try to help with: 1159784 ovirt-engine Documentation NEW [RFE] Document when and where new features are available ... 1074301 ovirt-engine-cli RFEs NEW [RFE] ovirt-shell has no man page 772931 ovirt-engine-reports RFEs NEW [RFE] Reports should include the name of the oVirt engine 1120585 ovirt-image-uploader Documentation NEW update image uploader documentation 1120586 ovirt-iso-uploader Documentation NEW update iso uploader documentation 1120588 ovirt-log-collector Documentation NEW update log collector documentation 1237132 ovirt-engine Setup.Engine NEW [TEXT] New package listing of engine-setup when upgrading... 1115059 ovirt-engine General ASSIGNED Incomplete error message when adding VNIC profile to runn... Are you great at packaging software? Do you prefer a distribution which is currently unsupported by oVirt? Do you want to have packages included in your preferred distribution? Help getting oVirt ported there! Fedora: http://lists.ovirt.org/pipermail/devel/2015-September/011426.html CentOS: https://wiki.centos.org/SpecialInterestGroup/Virtualization Gentoo: https://wiki.gentoo.org/wiki/OVirt (GSoC: https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2016/Ideas ) Debian: http://www.ovirt.org/develop/release-management/features/debian-support-for… Archlinux: http://www.ovirt.org/develop/developer-guide/arch-linux/ OpenSUSE: https://build.opensuse.org/project/show/Virtualization:oVirt Do you love "DevOps?", you count stable builds in jenkins ci while trying to fall a sleep? Then oVirt infra team is looking for you!, join the infra team and dive in to do the newest and coolest devops tools today! Here are some of our open tasks you can help with: https://ovirt-jira.atlassian.net/secure/RapidBoard.jspa?rapidView=6 You can also help us by sharing how you use oVirt in your DevOps environment (please use [DevOps] in the subject). You can check out more docs on the DevOps side of oVirt in [12][13] You don't have programming skills, not enough time for DevOps but you want still to contribute? Here are some bugs you can take care of, also without writing a line of code: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… Do you prefer to test things? We have some test cases[5] you can try using nightly snapshots[6]. Do you want to contribute test cases? Most of the features[7] included in oVirt are missing a test case, you're welcome to contribute one! Do you want to contribute artworks? oVirt Live backgrounds and covers, release banners, stickers, .... Take a look at Fedora Artworks[9] as an example of what you can do Is this the first time you try to contribute to oVirt project? You can start from here [1][2]! You don't know gerrit very well? You can find some more docs here [3]. Any other question about development? Feel free to ask on devel(a)ovirt.org or on irc channel[4]. You don't really have time / skills for any development / documentation / testing related task? Spread the word[8]! Let us know you're getting involved, present yourself and tell us what you're going to do, you'll be welcome! [1] http://www.ovirt.org/develop/ [2] http://www.ovirt.org/develop/dev-process/working-with-gerrit/ [3] https://gerrit-review.googlesource.com/Documentation [4] http://www.ovirt.org/community/ [5] http://www.ovirt.org/develop/infra/testing/ [6] http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/ [7] http://www.ovirt.org/develop/release-management/features/ [8] http://www.zdnet.com/article/how-much-longer-can-red-hats-ovirt-remain-cove… [9] https://fedoraproject.org/wiki/Artwork#Resources [10] http://git.debian.org [11] http://lists.ovirt.org/mailman/listinfo/devel [12] http://ovirt-infra-docs.readthedocs.org/en/latest/ [13] http://www.ovirt.org/develop/infra/infrastructure-documentation/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

ovirt 3.5 to 3.6 upgrade
by Paul Dyer 30 Mar '16

30 Mar '16

Hi, after upgrade to ovirt 3.6, the ovirt-release35 repo remains on the manager machine (non-hosted engine). There is also a list of rpms from the 3.5 repo. Should the 3.5 repo be removed? What about the rpms from the 3.5 repo? Should they stay or go? Here is a list of 3.5 repo rpms still installed: # yum list installed |grep ovirt-3.5 ovirt-engine-jboss-as.x86_64 7.1.1-1.el6 @ovirt-3.5 patternfly1.noarch 1.3.0-1.el6 @ovirt-3.5-patternfly1-noarch-epel python-daemon.noarch 1.5.2-1.el6 @ovirt-3.5-epel python-kitchen.noarch 1.1.1-1.el6 @ovirt-3.5-epel python-lockfile.noarch 0.8-3.el6 @ovirt-3.5-epel python-ply.noarch 3.4-4.el6 @ovirt-3.5-epel python-websockify.noarch 0.6.0-3.el6 @ovirt-3.5-epel xalan-j2.noarch 2.7.1-8.jbossorg_1.jpp6 @ovirt-3.5-jpackage-6.0-generic Thanks, Paul -- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750

2 1

[vdsm] new internal stable modules + proposal
by Francesco Romani 30 Mar '16

30 Mar '16

Hi, in the last Vdsm developer call we agreed to promote a few modules in the common repository. The common repository provides the additional guarantees over regular modules in lib/vdsm/ - stable API - (thus) safe to use across verticals the planned moves are: lib/vdsm/schedule.py -> lib/vdsm/common/schedule.py lib/vdsm/periodic.py -> lib/vdsm/common/periodic.py lib/vdsm/virt/api.py -> lib/vdsm/common/api.py Question is if those modules should go under common/ or under another subdirectory, maybe infra? Lastly, i have a proposal about better handling of those modules. First, the mere fact a module is placed under lib/vdsm/common provides the extra guarantees I mentioned. But should we added more annotations? for example something like __API__ = {} near the top of the module if this attribute exist, then the module is safe to use across verticals, has stable API and so forth (this is _in addition_ to the common/ package, not as replacement). Like: __API__ = { "introduced-in": "4.14.0", "deprecated-from": "4.18.0", "removed-at": "4.20.0", "contact": "fromani(a)redhat.com" } We could refine further this concept if we like it. The idea is to be lightweight as possible while carrying all the information we need. Comments welcome as usual bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

3 7

[ATN] [ACTION REQUIRED] Tweaking engine CI flow
by Roy Golan 30 Mar '16

30 Mar '16

Hi all, Eyal and I sat together to analyse and tweak the engine CI and this is what we came up with: - dao test excludes updated - exclude dal/src/main/bundles from invoking dao tests A trivial update of validation messages without any db change would trigger dao test without any need. This is one less job run for lots of patches. This change is effective now. - Spare CI re-run on trivial rebases Gerrit trigger supports suppressing itself if the change to the tree was trivial. Most of the waste of resources(time and IO :) ) is around rebasing a change and waiting for CI to rerun. if Change1 is ci+1 and Change2 is ci+1 the chances that they will break CI together is very small and taking that risk is most probably worth it due to the huge resources waste This change isn't effective yet - *Please reply here* if you agree or not to make this change available. All of this is 'master' - 3.6 will follow if we will agree on activating that change. Thanks, Roy

4 6

[VDSM] Vdsm build requires now python 3 on EL7
by Nir Soffer 30 Mar '16

30 Mar '16

Hi all, Since commit f247a0cff310 (el7: require newly available python34-nose), building vdsm requires Python 3 on EL7. Unfortunately, it seems that ovirt-release-master that should add all the dependencies needed for vdsm does is not configured properly, so building vdsm will fail. I heard that installing epel7 repo fixes this issue. Cheers, Nir [1] https://github.com/oVirt/vdsm/commit/f247a0cff310dbbf62b07e779adbe9973734a9…

6 6

Failing to run ovirt-system-tests using lago due to missing rpms
by Eyal Edri 29 Mar '16

29 Mar '16

Hi, Anyone encountered these errors when running 3.6 basic suite on RHEL 7.2? * STDERR Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-iso-uploader >= 3.6.0 Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: slf4j >= 1.7.0 Available: slf4j-1.5.8-8.el6.noarch (base) slf4j = 1.5.8-8.el6 Error: Package: ovirt-engine-backend-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-host-deploy-java >= 1.4.0 Error: Package: ovirt-engine-vmconsole-proxy-helper-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-vmconsole-proxy Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-image-uploader >= 3.6.0 Error: Package: ovirt-engine-backend-3.6.4.1-1.el6.noarch (localsync) Requires: ebay-cors-filter Error: Package: ovirt-engine-setup-base-3.6.4.1-1.el6.noarch (localsync) Requires: otopi >= 1.4.0 Error: Package: ovirt-engine-setup-plugin-ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-engine-extension-aaa-jdbc Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-engine-wildfly >= 8.2.1 Error: Package: ovirt-engine-setup-plugin-ovirt-engine-common-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-setup-lib Error: Package: ovirt-engine-backend-3.6.4.1-1.el6.noarch (localsync) Requires: vdsm-jsonrpc-java >= 1.1.8 Error: Package: ovirt-engine-backend-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-engine-extension-aaa-jdbc # [Thread-3] Deploy VM lago_basic_suite_3_6_engine: ERROR (in 0:01:59) Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 46, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 472, in _deploy_host host.name(), RuntimeError: /home/eedri/lago/ovirt-system-tests/basic_suite_3.6/deploy-scripts/setup_engine.sh failed with status 1 on lago_basic_suite_3_6_engine @ Deploy oVirt environment: ERROR (in 0:01:59) Error occured, aborting Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 248, in do_run self.cli_plugins[args.ovirtverb].do_run(args) File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 180, in do_run self._do_run(**vars(args)) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 501, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 512, in wrapper return func(*args, prefix=prefix, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 174, in do_deploy prefix.deploy() File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 598, in wrapper func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 52, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 480, in deploy self._deploy_host, self.virt_env.get_vms().values() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 88, in invoke_in_parallel vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 46, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 472, in _deploy_host host.name(), RuntimeError: /home/eedri/lago/ovirt-system-tests/basic_suite_3.6/deploy-scripts/setup_engine.sh failed with status 1 on lago_basic_suite_3_6_engine -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Engine 3.6.5 has been branched out
by Tal Nisan 29 Mar '16

29 Mar '16

A new branch ovirt-engine-3.6.5 has been branched out from the ovirt-engine-3.6 branch please note that: - 3.6.5 patches will now have to be backported to the new branch as well as the 3.6 branch - 3.6.6 patches should only be merged to the 3.6 branch only All 3.6.6 patches that were backported to the 3.6 and were pending the branching out can now be merged, please rebase and verify again.

2 1

Hello and a question about QEMU log
by zhukaijie 29 Mar '16

29 Mar '16

Hello, Each running VM has it's command line logged in /var/log/libvirt/qemu/${vmname}. And now I'd like to disable this log function, that is to say, not to record the QEMU command line of VM. Could you please tell me will can I configure it? Best wishes.

2 1

[ANN] oVirt 3.6.4 Final Release is now available
by Sandro Bonazzola 29 Mar '16

29 Mar '16

The oVirt Project is pleased to announce today the general availability of oVirt 3.6.4. This latest community release includes numerous bug fixes for - ovirt-engine - vdsm - ovirt-hosted-engine-setup - ovirt-hosted-engine-ha oVirt is an open-source, openly-governed enterprise virtualization management application, developed by a global community. You can use the oVirt management interface (oVirt Engine) to manage hardware nodes, storage and network resources, and to deploy and monitor virtual machines running in your data center. If you are familiar with VMware products, oVirt is conceptually similar to vSphere. oVirt serves as the bedrock for Red Hat's Enterprise Virtualization product, and it is the "upstream" project where new features are developed prior to their inclusion in Red Hat's supported product offering. Additional Resources: * Read more about the oVirt 3.6.4 release highlights: http://www.ovirt.org/release/3.6.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/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

HEADS UP: otopi - enforce priority and other changes
by Yedidyah Bar David 29 Mar '16

29 Mar '16

Hi all, In two days or so, we are going to merge [1]. Without it, if you have events (functions with a '@plugin.event' decoration) that due to before=/after= requirements, otopi could not comply with their priority=, it will continue, ignoring this and only writing a message to the console if you set OTOPI_DEBUG=1. With this change, it will fail. Under normal circumstances, you'll see nothing in the console or the log, just an exit code of 1. If you set an environment variable OTOPI_DEBUG=1, it will emit a "RuntimeError: Priorities were reversed during buildSequence" error, see examples below. You can restore the existing behavior by setting another env var OTOPI_ALLOW_PRIORITY_OVERRIDE=1 . Soon thereafter, we are going to merge [2]. This will replace the algorithm that is used to decide what to run when. In principle, after [1] is merged, they should be compatible. However, the new algorithm does not allow overriding priorities. To revert to the old algorithm, you can set env var OTOPI_ALLOW_LEGACY_BUILDSEQ=1 . The old algorithm (and this option) is intended to be removed eventually, probably after oVirt 4.0 is released. Patches to make engine-setup (engine+dwh+reports) and host-deploy compatible with the new behavior were already merged to master branches. Still we most likely forgot some other tools/flows/etc., so if you encounter such failures please open a bug against the relevant tool. On a more positive (?) side, we also recently added a new package to master, called otopi-debug-plugins. It currently includes two plugins, which are not enabled by default. One of them allows you to get a prompt 'Press Enter to continue' on [ERROR], so it's easier to have a look at the system before the tool might try to rollback or something, the other allows you to enforce a failure at a certain stage, which might be useful to debug/verify failures and especially rollbacks. More details about these are in a new README file [3]. [1] https://gerrit.ovirt.org/55329 [2] https://gerrit.ovirt.org/28775 [3] https://gerrit.ovirt.org/gitweb?p=otopi.git;a=blob;f=README.debug-plugins Examples: 1. # ovirt-host-deploy # echo $? 1 2. # OTOPI_DEBUG=1 ovirt-host-deploy 2>&1 | tail Priorities were reversed during buildSequence: method <bound method ?._init of <otopi.plugins.otopi.core.log.Plugin object at 0x7f9827c9fe10>> with priority 2000 appears after method <bound method ?._preinit of <otopi.plugins.ovirt_host_deploy.core.misc.Plugin object at 0x1032990>> with priority 5000 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 151, in execute self.context.buildSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 400, in buildSequence raise RuntimeError(msg) RuntimeError: Priorities were reversed during buildSequence: method <bound method ?._init of <otopi.plugins.otopi.core.log.Plugin object at 0x7f9827c9fe10>> with priority 2000 appears after method <bound method ?._preinit of <otopi.plugins.ovirt_host_deploy.core.misc.Plugin object at 0x1032990>> with priority 5000 ('FATAL Internal error (main): Priorities were reversed during buildSequence: method <bound method ?._init of <otopi.plugins.otopi.core.log.Plugin object at 0x7f9827c9fe10>> with priority 2000 appears after method <bound method ?._preinit of <otopi.plugins.ovirt_host_deploy.core.misc.Plugin object at 0x1032990>> with priority 5000',) 3. # OTOPI_DEBUG=1 OTOPI_ALLOW_PRIORITY_OVERRIDE=1 ovirt-host-deploy ... Priorities were reversed during buildSequence: method <bound method ?._init of <otopi.plugins.otopi.core.log.Plugin object at 0x7fbe17f51e10>> with priority 2000 appears after method <bound method ?._preinit of <otopi.plugins.ovirt_host_deploy.core.misc.Plugin object at 0x107f8d0>> with priority 5000 [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor. Are you sure you want to continue? (yes/no) And with [2]: 4. # OTOPI_DEBUG=1 ovirt-host-deploy ... _toposortBuildSequence failed: Cyclic dependencies found ('FATAL Internal error (main): Cyclic dependencies found',) 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 151, in execute self.context.buildSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 665, in buildSequence self._sequence = self._toposortBuildSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 624, in _toposortBuildSequence raise RuntimeError(_('Cyclic dependencies found')) RuntimeError: Cyclic dependencies found 5. # OTOPI_DEBUG=1 OTOPI_ALLOW_PRIORITY_OVERRIDE=1 ovirt-host-deploy (fails the same way as (4.)) 6. # OTOPI_ALLOW_LEGACY_BUILDSEQ=1 OTOPI_DEBUG=1 ovirt-host-deploy (fails similarly to (2.) - you'll see more-or-less outputs of (4.) then (2.) combined) 7. # OTOPI_ALLOW_LEGACY_BUILDSEQ=1 OTOPI_DEBUG=1 OTOPI_ALLOW_PRIORITY_OVERRIDE=1 ovirt-host-deploy (succeeds like (3.), but with part of the output of (4.) before that) Best regards, -- Didi

1 0

Workaround for Gerrit 'Internal Server Error' after deleting draft
by Tomer Saban 28 Mar '16

28 Mar '16

Hi, I came across a bug in Gerrit when trying to delete a draft. It seems that it ruins the patchset(Gerrit doens't set the new last revision properly). So, in order to fix this issue we need to reset the last revision. In order, to do that you need to find the last revision after deleting the draft(Let's assume it's 23). Once, you have that you need to number of the patch in gerrit. For example, the number in: https://gerrit.ovirt.org/#/c/51636/ is 51636. Last, You need to run the following line from the shell: ssh gerrit.ovirt.org gerrit review --rebase 51636,23 FYI, Tomer

2 1

VDSM Network Tests
by Paul Maidment 27 Mar '16

27 Mar '16

I notice that on my build of VDSM, the network test. functional/networkTests.py:testDhcpReplaceNicWithBridge Fails on the assertion that the address will not change (the dnsmasq dhcp server returns a new address for the same mac) Can anyone reproduce this?

2 1

ovirtm Hosts reinstall button
by Paul Dyer 27 Mar '16

27 Mar '16

Hi, can anyone explain what this button does? I have looked in the documentation but have found no reference to it. Will reinstall only install packages and setting for the host, and leave cluster/storage/networks alone? I have a cluster version 3.6.2 that will not Activate the host because the message "Host .. is compatible with versions (3.0,3.1,3.2,3.3,3.4,3.5) and cannot join Cluster...". The host was part of a 3.5 cluster until the upgrade to 3.6.2. Thanks a million, Paul -- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750

5 10

Heads up: Engine 3.6.5 branching out next week
by Tal Nisan 24 Mar '16

24 Mar '16

Hey everyone, Around mid next week Engine 3.6.5 will be branched out from the ovirt-engine-3.6 branch. This gives the teams a few days of grace to be able to close 3.6.5 issues with a single backport so now will be a good time to go over the patches in the branch and review/verify so they can get merged. Right after the branching out all 3.6.5 patches will have to be backported both to the 3.6 branch and the 3.6.5 branch whereas 3.6.6 patches will be backported to the 3.6 branch only. Another heads up on a related issue: there are currently 38 open patches in the 3.6 branch some of which date as far as January. As this clutters my everyday work on the branch, right after branching out I'm going to clear out stale patches and I'm going to keep abandoning patches in the stable branch that are stale for too long. Bear in mind that in 99.9% of the cases there is no reason for a patch to be open on the stable branch for more that 2 weeks after it's merged on master.

1 0

Reviews needed for ovirt-system-tests
by Eyal Edri 24 Mar '16

24 Mar '16

Hi, There has been progress with fixing a few issues on ovirt-system-tests and patches were submitted [1]. We would like to merge them ASAP so the ovirt tests for 3.6 and 4.0 can get one more step closer to working and being stable both for developers and for CI. Can you please review the pending patches so we can merge them TODAY? [1] https://gerrit.ovirt.org/#/c/53534 - needs a review https://gerrit.ovirt.org/#/c/53518/ - +1, probably can be merged. https://gerrit.ovirt.org/#/c/54738/ - +1, can get merged. https://gerrit.ovirt.org/#/c/54721/ - +1, can get merged https://gerrit.ovirt.org/#/c/51566/4 - +1, can get merged https://gerrit.ovirt.org/#/c/52681/ - not sure about this one -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[vdsm][virt] what's new in virt (20151215)
by Francesco Romani 23 Mar '16

23 Mar '16

Hi all, I'm happy to start a weekly summary of what's going on on virt's world (VDSM edition). General topics * I've got some mixed feedback about my Vm-on-a-diet effort. I still believe that fat trimming is a worthwhile goal per se, but I'm willing to adapt the strategy responding to the comments, so we will focus on virt-specific topics. * As consequence of the above, I'm focusing on the last bits of device fixing, which involves - fixing all device to update themselves from libvirt XML after domain boot, instead using all the getUnderyling* methods - switch the devices related code to use Etree instead of minidom. This will involve changes to the domain_descriptor. I estimate this task will still trim ~600 lines out of vm.py, so it still somehow gets some size trimming done, albeit not intensive as planned. This is a complex topic, will post plan and ideas on a separate mail * Finally, some series are still worth pushing forward, see below. Patches in need of attention * topic branches - mpolednik started a much needed cleanup and fixing of fake_qemu and fake_kvm code, with the ultimate goal to move all the remaining bits into the faqemu hook, and to make it useful on ppc64. Lots of refactoring is needed to support this change, and that produced https://gerrit.ovirt.org/#/q/topic:cpuinfo - we want to improve the reporting in case of migratio aborted. The ultimate goal is to let Engine (thus the User) know why a migration failed. To export this information, however, we need some cleanup before. Hence: https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:m… - last and less urgent: here's some cleanup about existing getUnderlying* methods of Vm class, preparing the last step of the big vmdevices split. I believe this is useful anyway https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v… * single patches - https://gerrit.ovirt.org/#/c/46846 this is the first of a series aiming to improve migration support in 4.0. Probably worth merging all together, even though this one seems ready for broader review to me. - https://gerrit.ovirt.org/#/c/49173/ Notified just to raise awareness, still working on ensuring backward compatibility and smooth upgrade - https://gerrit.ovirt.org/#/c/48672 v2v xen support - https://gerrit.ovirt.org/#/c/49951/ OVA support improvements. Worth a look, but note that we are working toward a split of this big patch - https://gerrit.ovirt.org/#/c/49636 V2V refactoring, also almost ready - https://gerrit.ovirt.org/#/c/49570/ still in the context of migration enhancements. We want to throttle incoming migrations, to do so we want to use a sempahore which needs to be held by the creation thread until VM is created. This helper makes this possible, using an uniform interface for both this case and the common, simpler case. That's all for now, as usual, reviews welcome! :) -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

4 14

removing old ovirt-engine unit tests jobs
by Eyal Edri 23 Mar '16

23 Mar '16

Hi, I'd like to remove the following jobs from CI [1], since they are not adding any benefit over existing logic provided by the standard ci jobs (i.e checkstyle & unit tests already run there). Pros from removing: --------------------------- - reduce time needed to wait on patch verification - reduce load on jenkins - reduce possibility of false positive errors (since they are not running on mock) - reduce load on jenkins in general & maintainability Possible cons: ------------------ - output on unit tests failure might be not nice as existing jobs, but will still provide the relevant error. there is an open ticket on adding support for UI on STD ci, so it will there in the future. If I won't get any rejections or justified concerns on this thread, I will start with disabling them and if all goes well removing them after 1 week. [1] ovirt-engine_3.6_style_gerrit ovirt-engine_master_style_gerrit ovirt-engine_3.6_unit-tests_gerrit ovirt-engine_3.6_unit-tests_merged ovirt-engine_master_unit-tests_gerrit ovirt-engine_master_unit-tests_merged -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Maintenance Notification: gerrit.ovirt.org Upgrade Today at 15:00 IST (14:00 CET) - Tentative Time
by Anton Marchukov 23 Mar '16

23 Mar '16

Hello All. We plan to upgrade gerrit to a new version today starting tentatively at 15:00 IST (14:00 CET). However it might be postponed to a later time if we did not manage to get snapshot by that time. During the upgrade the gerrit will not be available. This should not take longer than few hours and I will keep you updated on the progress. Please note that we plan to upgrade to the latest major version 2.12.2. First of all we hope that stability issues that we face are solved there. Besides that consecutive upgrade was required to be able to use online re-indexing limiting downtime. The version has the following core features: - Significant online edit UI improvements - New change submission workflows: Submit Whole Topic and Submitted Together. - Support for GPG Keys and signed pushes. Please let us know if there is anything critical that is preventing us from this upgrade. You can follow up release notes at [1], [2] and [3]. [1] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [2] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [3] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… Anton -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

3 8