January 2016 - Devel - oVirt List Archives

TransactionSupport during command validation
by Tomer Saban 13 Jan '16

13 Jan '16

Hi, I wanted to draw your attention to something I found out while fixing a bug involving the use of transactions in commands. When calling a command using getBackend().runAction() when another transaction is open, by default the command will become part of the open transaction because by default CommandBase specifies TransactionScopeOption.Required as the default 'scope'. Unfortunately, validation function(formerly CanDoAction()) will not be aware of the opened transaction. This get be problematic in cases where the validation() method check things that are fixed in the opened transaction and not committed yet. For example, In my case I'm using the AddVdsGroupCommand which creates a new cluster (In an open tranasction) and then, calls the AddCpuProfileCommand which creates a default cpu profile. The default cpu profile validation() check then, Check if the cluster exists which fails because it's not part of the opened transaction. They way to over come this is to add the validation() method to the open transaction by adding @ValidateSupportsTransaction annotation on the command. The associated part of the code in CommandBase(line 817) : """ if (!isValidateSupportsTransaction()) { transaction = TransactionSupport.suspend(); } """ isValidateSupportsTransaction() - Checks that the annotation exists and if it's not it suspends the TransactionSupport. FYI, Tomer

1 0

Non Responding Treatment not working?
by Roy Golan 13 Jan '16

13 Jan '16

I have seen 2 diferent installations not moving a host to non responsive. One host was failing to install and stayed in "Installing" and on my setup a host just stays in "Connecting" and the treatment doesn't kick in. Anyone seen this?

2 6

Request permissions for ovirt-host-deploy maintainership
by Sandro Bonazzola 12 Jan '16

12 Jan '16

Hi, ovirt-host-deploy access lists have as unique member Alon Bar-Lev which recently left the project. Since the python part is otopi based and I already had worked on it on the past, I'm stepping in, proposing myself as maintainer for that project. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 6

oVirt 3.6.2 RC2 build starting
by Sandro Bonazzola 12 Jan '16

12 Jan '16

Fyi oVirt products maintainers, An oVirt build for an official release candidate is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Vdsm sync 5/1 summary after short delay
by Yaniv Bronheim 11 Jan '16

11 Jan '16

(fromani, nsoffer, ybronhei, alitke) - Removing xmlrpc for good - who should accept it? where do we stand with full jsonrpc client ? (we didn't get to any conclusions and said that we'll reraise this topic next week with pioter) - Moving from nose to pytest - generally good approach to achieve. It requires some changes in current testlib.py code. must be an item for next major version (nir already managed to run most of the tests with it, and stated few gaps) - Exception patches - still on progress, please review ( https://gerrit.ovirt.org/48868) - python3 effort to cover all asyncProc usage, and allowing utils import without having python3-cpopen - https://gerrit.ovirt.org/51421 https://gerrit.ovirt.org/49441 . still under review We didn't take notes during that talk, so if I forgot to mention something I apologize. Feel free to reply and raise it Greetings, -- *Yaniv Bronhaim.*

6 7

oVirt Community Newsletter, December 2015
by Mikey Ariel 11 Jan '16

11 Jan '16

Happy 2016! December was a great closing month for 2015, with more FOSDEM updates, software releases, technical articles, and some new meetups! Check out the newsletter for all the updates. ----------------- Software Releases ----------------- oVirt 3.6.2 First Release Candidate is now available for testing http://lists.ovirt.org/pipermail/announce/2015-December/000224.html Async release for ovirt-hosted-engine-ha is now available http://lists.ovirt.org/pipermail/announce/2015-December/000223.html oVirt 3.6.1 Final Release is now available http://lists.ovirt.org/pipermail/announce/2015-December/000220.html oVirt 3.5 won't receive further updates http://lists.ovirt.org/pipermail/announce/2015-December/000213.html oVirt 3.5.6 Final Release is now available http://lists.ovirt.org/pipermail/announce/2015-December/000212.html ---------------- In the Community ---------------- oVirt goes to FOSDEM 2016 - Devroom, Stand, Social Event http://lists.ovirt.org/pipermail/users/2016-January/037091.html All oVirt-related sessions at FOSDEM 2016 https://fosdem.org/2016/schedule/event/virt_iaas_host_lifecycle_content_man… https://fosdem.org/2016/schedule/event/virt_iaas_reactive_processing_ovirt/ https://fosdem.org/2016/schedule/event/virt_iaas_sweep_away_the_garbage/ https://fosdem.org/2016/schedule/event/managing_ceph_through_cinder_using_o… https://fosdem.org/2016/schedule/event/virt_iaas_ovirt_hyperconverge/ https://fosdem.org/2016/schedule/event/virt_iaas_containers_and_virtualizat… Cockpit 0.87 is released, contains candidate bits for oVirt node https://lists.fedorahosted.org/archives/list/cockpit-devel%40lists.fedoraho… A Puzzle Called oVirt Node Next http://dummdida.tumblr.com/post/135713197955/a-puzzle-called-ovirt-node-next Global view of oVirt (and friends) meetups http://ovirt.meetup.com/ ------------------------------------ Deep Dives and Technical Discussions ------------------------------------ How to fix oVirt error: “Failed to attach Storage Domain [ ] to Data Center [ ]” https://bobcares.com/blog/how-to-fix-ovirt-error-failed-to-attach-storage-d… oVirt VM “unknown status” solved http://matthewxspencer.com/2015/12/17/196/ How we setup high availability in oVirt cloud system https://bobcares.com/blog/how-we-setup-high-availability-in-ovirt-cloud-sys… Converting Debian/Ubuntu to oVirt http://andrewwippler.com/2015/12/18/converting-debianubuntu-to-ovirt/ How to backup and restore oVirt engine https://bobcares.com/blog/how-to-backup-and-restore-ovirt-engine/ oVirt Integration with Satellite/Foreman https://www.runlevelone.net/wordpress/index.php/2015/12/31/ovirt-integratio… Building an open source Cloud Hosting solution using oVirt (open virtualization) https://bobcares.com/blog/building-a-cost-effective-cloud-hosting-solution-… Converting VMs for oVirt http://andrewwippler.com/2015/12/11/converting-vms-for-ovirt/ New article series: oVirt Virtualization http://blog.vikki.in/ovirt-virtualization-part-1/ Planning the Deployment of oVirt http://andrewwippler.com/2015/12/04/planning-the-deployment-of-ovirt/ -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady

1 0

Installing the oVirt Node Next Early-Preview
by Fabian Deutsch 11 Jan '16

11 Jan '16

Hey, finally we've got continous builds of [oVirt Node Next](http://www.ovirt.org/Node/4.0) in [oVirt's jenkins instance](http://jenkins.ovirt.org/user/fabiand/my-views/view/Node.next/job… which are consumable by Anaconda. **Note:** This is an early preview, the basic oVirt bit's (vdsm) are there and you should be able to add such a host to Engine. But updates are not yet working, and if they were, then they'd be broken. You want to try it? Read on. ## Starting the anaconda installer Independently if you continue with a VM or a bare metal server, the host you will use - needs at least 3GB of free space - is connected to the internet ### Using a VM The safe way to try the oVirt Node Next is to install it into a VM, this is quite easy: qemu-img create -f qcow2 dst.img 20G qemu-system-x86_64 \ -enable-kvm \ -m 2048 \ -cdrom http://jenkins.ovirt.org/job/fabiand_boo_build_testing/lastSuccessfulBuild/… \ -hda dst.img \ -serial stdio \ -net nic -net user,hostfwd=tcp::19090-:9090 Now select _"Interactive installation"_ and wait for the anaconda installer to come up, this can take a while, as data is downloaded from the internet. ### Using bare metal (easy - iPXE ISO) Trying oVirt node Next on bare metal is not much more difficult. 1. Download our pre-built PXE ISO: <http:> 2. Write the `ovirt-ipxe.iso` onto a CD-ROM, DVD, USB, virtual media 3. Boot your bare metal server using the previously created media Now select _"Interactive installation"_ and wait for the anaconda installer to come up, this can take a while, as data is downloaded from the internet. ### Using bare metal (medium - CentOS 7 ISO + kernel arguments) Trying oVirt Node Next on bare metal is not much more difficult. 1. Grab a CentOS 7 (Node Next is based on CentOS 7) netinstall `boot.iso` from a [mirror close to you](http://mirror.centos.org/centos-7/7/os/x86_64/images/boot.iso). 2. Boot the `boot.iso` on your bare metal server and wait for ISOLINUX bootloader 3. Select the default entry and append the following arguments: `inst.ks=https://gerrit.ovirt.org/gitweb?p=ovirt-node-ng.git;a=blob_plain;f=docs/kickstart/minimal-kickstart.ks;hb=HEAD inst.updates=http://jenkins.ovirt.org/job/fabiand_boo_build_testing/lastSuc… inst.stage2=http://mirror.centos.org/centos-7/7/os/x86_64/` Now wait for the anaconda installer to come up, this can take a while, as data is downloaded from the internet. # Performing the installation Once anaconda is up you need to answer a few questions 1. Select your prefered language and continue 2. On the next page, select your keyboard layout and timezone 3. Select the disk to be used - Enter the spoke (the thing which opens when you click on the disk icon), and select the disk to use. Sometimes you need to deselect and select the disk icon again. **Note: Leave the partitioning to automatic. If you are brave you can do your own partitioning layout, but ensure to use LVM thin-provisioning.** 4. Now you should have answered all necessary questions, and can proceed by hitting `Continue` 5. The installation is started, use the time to at least set a _root_ user password. **Note: The installation can take a while, because now the installation image is pulled from our jenkins instance (~500MB).** 6. Once the installation is done and you've set a password, you can reboot the host and it should be ready to use. The host can now be added to Engine. **Note:** In case you encounter issues, enable permissive mode on the host by calling `setenforce 0` ## Trying Cockpit This is an early preview with cockpit installed. But currently cockpit is not enabled and the firewall prevents access. Yes, it will be fixed. Until then: Perform the following steps to take a look at cockpit: 1. Use the VM installation above 2. After installation, log intot the VM 3. Start cockpit: `systemctl start cockpit` 4. Stop firewalld: `systemctl stop firewalld` 5. Browse to <http:> (on the host, not inside the VM), this request will be forwarded to port 9090 inside the VM, where cockpit is running. ## Feedback Is this working for you or not? Could you install Node? Could you add Node? Could you browse Cockpit? Or did your host explode? Let us know what you think. ## Next steps The next big step is to enable updates. On behalf of the Node Team - fabian

1 1

oVirt 3.6.2 RC2 merge / tag / bugzilla reminder
by Sandro Bonazzola 11 Jan '16

11 Jan '16

All stable branch maintainers, please make sure to - merge all relevant open bugs until Tuesday morning 11:00 AM TLV time. - https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Every package build (i.e oVirt product) - please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-3.6.2.5, tr: 3.6.2.5) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt 3.6.2 RC2 build planned
by Simone Tiraboschi 11 Jan '16

11 Jan '16

Fyi oVirt developers, An oVirt build is planned for this Tuesday 11:00 AM, please make sure to backport any open patches to the stable branch for review by the stable branch maintainers. Here's a list of open blockers: https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.…

2 2

[VDSM] exceptions cleanup
by Nir Soffer 10 Jan '16

10 Jan '16

Hi all, I started the exceptions topic[1], trying to: - gather all exceptions in vdsm.exception - make all exceptions inherit from same base class - add exceptions for virt errors, currently managed in vdsm.define (unfinished) - add missing tests for the exception logic Having exceptions for all api errors, we can simplify error handling in virt so you can raise an exception in any level, and have one top level error handler that knows how to create an error response. See Piotr patch [2] adding such handler. One issue raised by Pitor was ensuring that we don't have duplicate error codes. We have tests/main.py, checking that storage exceptions and gluster exceptions use unique error codes. Another issue raised by Pitor is having single location for vdsm error codes, instead of duplicating the information in both vdsm and engine. Actually this info is duplicated also in hosted engine setup and agent, and maybe in other places. I think the best solution for this is to generate the java module used by engine from vdsm.exception. Python applications can depend on vdsm-api package, and import vdsm.exception. Future changes: - Merge storage_exception, into vdsm.exception - Move vdsm.exception into api pacakge - Cover all exceptions in the unique error code tests - Replace the error response dict in all verbs with raising an exception - Dropping the error handler in vdsm.storage.dispatcher. The first 4 patches in [1] should be ready for merge. Thoughts? [1] https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:e… [2] https://gerrit.ovirt.org/#/c/51549/2/vdsm/rpc/Bridge.py Nir

1 0

[VDSM] Vdsm weekly call
by Nir Soffer 10 Jan '16

10 Jan '16

Hi all, We are having vdsm call each Tuesday, 17:00 – 17:30 at https://bluejeans.com/2061366027 Topics for this week call: - jsonrpc client - Killing vdsClient - Removing xmlrpc - Anything else *you* like to discuss Cheers, Nir

2 2

Obfuscated UI exception message debugging
by Alexander Wels 08 Jan '16

08 Jan '16

Hi, With the release of oVirt 3.6 the UI team added a handler for any uncaught exceptions. This handlers shows a popup that basically says the following: Uncaught exception occurred. Please try reloading the page. Details: [some information] With the some information giving some indication of what happened. Usually that information is less than helpful. You can see the associated stack trace in the browser console, but since all the code is obfuscated the stack trace is usually pretty useless as well. I have been seeing a lot of bugs being opened about the popup. In an effort to help everyone understand what is going on and help us debug the root cause of the problem I created a wiki page [1] that shows some steps to 'de-obfuscate' manually the stack trace and provide hopefully some useful information. Doing all of this labor intensive and not very intuitive, so in an effort to automate the process, I have also created a patch that sends the obfuscated stack trace to the engine and some code to automatically de-obfuscate the stack trace and write it to a UI specific log [2]. Once that patch is merged looking up UI exceptions should be as simple as looking in that log. Hopefully the above will aid everyone in debugging any strange exceptions generated by the UI. Alexander [1] http://www.ovirt.org/OVirt_Engine_Debug_Obfuscated_UI [2] https://gerrit.ovirt.org/#/c/51558/

1 0

[VDSM] [REVIEW] Introduce commands package to separate execCmd and AsyncProc from utils
by Nir Soffer 08 Jan '16

08 Jan '16

Hi all, This patch moves execCmd and friends to new commands module, so code not using these can be ported to Python 3. More work is needed to make execCmd compatible with Python 3, and we don't want to delay the work on other modules that do not depend on it, but import utils. Since this change touches all sub systems in vdsm, subsystems maintainers should review and *verify* that it does not break anything. Please review and verify: https://gerrit.ovirt.org/51421 We are going to merge it on end of next week, so better check that it does not break your code before that. Thanks, Nir

1 0

[oVirt jenkins] Weekly report on open tasks for ovirt-engine
by jenkins＠ovirt.org 08 Jan '16

08 Jan '16

1 0

fyi - vdsm check-patch for el7 has been disabled due to tests errors unattended
by Eyal Edri 06 Jan '16

06 Jan '16

FYI, The vdsm job [1] has been failing for quite some time now, without any resolution so far. In order to reduce noise and false positive for CI it was disabled until the relevant developers will ack it it stable and can be re-enabled. Please contact the infra team if you need any assistance testing it on a non-production job. [1] http://jenkins.ovirt.org//job/vdsm_3.5_check-patch-el7-x86_64/ -- Eyal Edri Associate Manager EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

3 5

com.google.gwt.event.shared.UmbrellaException
by Sandro Bonazzola 06 Jan '16

06 Jan '16

Hi, not sure the following traceback is enough, but I've the system still around and can provide more logs / info if needed. Adding one host, in the dialog select use foreman / satellite, disable the checkbox. An exception is reported on the top of the admin interface and in firefox console I see: Wed Dec 23 08:23:59 GMT+100 2015 SEVERE: Uncaught exception: com.google.gwt.event.shared.UmbrellaException: Exception caught: Exception caught: (TypeError) __gwt$exception: <skipped>: zab(...) is null at Unknown.ms(Unknown Source) at Unknown.us(Unknown Source) at Unknown.e3(Unknown Source) at Unknown.h3(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g$(Unknown Source) at Unknown.Km(Unknown Source) at Unknown.Vm(Unknown Source) at Unknown.$Ve(Unknown Source) at Unknown.$Xe(Unknown Source) at Unknown.Yt(Unknown Source) at Unknown.au(Unknown Source) at Unknown._t/<(Unknown Source) at Unknown.anonymous(Unknown Source) Caused by: com.google.gwt.event.shared.UmbrellaException: Exception caught: (TypeError) __gwt$exception: <skipped>: zab(...) is null at Unknown.ms(Unknown Source) at Unknown.us(Unknown Source) at Unknown.e3(Unknown Source) at Unknown.h3(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g2(Unknown Source) at Unknown.N4e(Unknown Source) at Unknown.B$(Unknown Source) at Unknown.C2(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g$(Unknown Source) at Unknown.Km(Unknown Source) at Unknown.Vm(Unknown Source) at Unknown.$Ve(Unknown Source) at Unknown.$Xe(Unknown Source) at Unknown.Yt(Unknown Source) at Unknown.au(Unknown Source) at Unknown._t/<(Unknown Source) at Unknown.anonymous(Unknown Source) Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError) __gwt$exception: <skipped>: zab(...) is null at Unknown.s2u(Unknown Source) at Unknown.RHr(Unknown Source) at Unknown.hno(Unknown Source) at Unknown.xno(Unknown Source) at Unknown.n1u(Unknown Source) at Unknown.p2u(Unknown Source) at Unknown.RHr(Unknown Source) at Unknown.hno(Unknown Source) at Unknown.xno(Unknown Source) at Unknown.o4u(Unknown Source) at Unknown.s4u(Unknown Source) at Unknown.Tuk(Unknown Source) at Unknown.Zuk(Unknown Source) at Unknown.f2(Unknown Source) at Unknown.C2(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g2(Unknown Source) at Unknown.N4e(Unknown Source) at Unknown.B$(Unknown Source) at Unknown.C2(Unknown Source) at Unknown.s2(Unknown Source) at Unknown.Im(Unknown Source) at Unknown.Sm(Unknown Source) at Unknown.g$(Unknown Source) at Unknown.Km(Unknown Source) at Unknown.Vm(Unknown Source) at Unknown.$Ve(Unknown Source) at Unknown.$Xe(Unknown Source) at Unknown.Yt(Unknown Source) at Unknown.au(Unknown Source) at Unknown._t/<(Unknown Source) at Unknown.anonymous(Unknown Source) com.google.gwt.event.shared.UmbrellaException -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 7

Failure running engine-setup on latest master
by Alexander Wels 06 Jan '16

06 Jan '16

Hi, I am trying to run engine-setup on latest master and it is failing on the database upgrade portion. The relevant part of the log is here. Can anyone help me solve this? psql:/home/awels/ovirt-**FILTERED**/share/ovirt- **FILTERED**/dbscripts/common_sp.sql:1117: NOTICE: drop cascades to function fn_db_get_async_tasks() NOTICE: drop cascades to trigger delete_disk_image_dynamic_for_image on table images psql:/home/awels/ovirt-**FILTERED**/share/ovirt- **FILTERED**/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql:57: ERROR: integer out of range FATAL: Cannot execute sql command: --file=/home/awels/ovirt- **FILTERED**/share/ovirt- **FILTERED**/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql 2016-01-05 09:18:21 DEBUG otopi.context context._executeMethod:156 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 146, in _executeMethod method['method']() File "/home/awels/ovirt-**FILTERED**/share/ovirt- **FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt- **FILTERED**/db/schema.py", line 291, in _misc o**FILTERED**cons.EngineDBEnv.PGPASS_FILE File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 946, in execute command=args[0], RuntimeError: Command '/home/awels/ovirt-**FILTERED**/share/ovirt- **FILTERED**/dbscripts/schema.sh' failed to execute Thanks, Alexander

3 2

FAIL: testEnablePromisc (ipwrapperTests.TestDrvinfo) - bad test? ci issue?
by Nir Soffer 06 Jan '16

06 Jan '16

Hi all, We see this failure again in the ci - can someone from networking take a look? 18:16:52 ====================================================================== 18:16:52 FAIL: testEnablePromisc (ipwrapperTests.TestDrvinfo) 18:16:52 ---------------------------------------------------------------------- 18:16:52 Traceback (most recent call last): 18:16:52 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/ipwrapperTests.py", line 130, in testEnablePromisc 18:16:52 "Could not enable promiscuous mode.") 18:16:52 AssertionError: Could not enable promiscuous mode. 18:16:52 -------------------- >> begin captured logging << -------------------- 18:16:52 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /usr/sbin/brctl show (cwd None) 18:16:52 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 18:16:52 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link add name vdsm-fS38VL type bridge (cwd None) 18:16:52 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 18:16:52 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev vdsm-fS38VL up (cwd None) 18:16:52 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 18:16:52 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev vdsm-fS38VL promisc on (cwd None) 18:16:52 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 18:16:52 --------------------- >> end captured logging << --------------------- http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/1838/conso… Thanks, Nir

3 2

4.0 GenericApiGWTService responses no longer being gzipped.
by Alexander Wels 05 Jan '16

05 Jan '16

Hi, While I was the network traffic in my browser for an issue I was working on. I noticed the response sizes being unusually large. When I compared it against a similar sized 3.6 installation the response was huge. Checking the headers it appears that the response no longer is gzipped before being send to the user. Does anyone know of any changes to that recently? I am unsure of what exactly gzipped the responses to begin with. I was assuming either a filter or some jboss setting. If anyone could shed some light on this it would be appreciated. Thanks, Alexander

2 3

Jenkins server restarted
by Barak Korren 05 Jan '16

05 Jan '16

The oVirt Jenkins server seems to have gone into a particularly long garbage collection process, so I just restarted it 10 minutes ago to make it responsive again. If you had jobs running at that time they will never finish, or finish with failure, please restart them. -- Barak Korren bkorren(a)redhat.com RHEV-CI Team

1 0

New network test failure on jenkins
by Nir Soffer 05 Jan '16

05 Jan '16

Hi all, There is a new networking test failure in the ci: 16:18:11 ====================================================================== 16:18:11 ERROR: test_dump_bonding_name2numeric (toolBondingTests.TestToolBonding) 16:18:11 ---------------------------------------------------------------------- 16:18:11 Traceback (most recent call last): 16:18:11 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testValidation.py", line 97, in wrapper 16:18:11 return f(*args, **kwargs) 16:18:11 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/modprobe.py", line 58, in wrapper 16:18:11 return f(*args, **kwargs) 16:18:11 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/toolBondingTests.py", line 37, in test_dump_bonding_name2numeric 16:18:11 opt_map = _get_bonding_options_name2numeric() 16:18:11 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/tool/dump_bonding_opts.py", line 94, in _get_bonding_options_name2numeric 16:18:11 opts[mode] = bond_opts_name2numeric_filtered(bond_name) 16:18:11 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/netinfo/bonding.py", line 203, in bond_opts_name2numeric_filtered 16:18:11 in _bond_opts_name2numeric(bond).iteritems() 16:18:11 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/netinfo/bonding.py", line 238, in _bond_opts_name2numeric 16:18:11 _bond_opts_name2numeric_scan(path) 16:18:11 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/netinfo/bonding.py", line 247, in _bond_opts_name2numeric_scan 16:18:11 numeric_val) 16:18:11 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/netinfo/bonding.py", line 259, in _bond_opts_name2numeric_getval 16:18:11 opt_write_file.flush() 16:18:11 IOError: [Errno 16] Device or resource busy: 'opt[/sys/class/net/Z7PxqN9gLALvKkE/bonding/lacp_rate], numeric_val[1]' See http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/1831/conso… Can someone from networking check this? Thanks, Nir

2 3

oVirt 3.6.2 RC2 merge / tag / bugzilla reminder
by Simone Tiraboschi 04 Jan '16

04 Jan '16

All stable branch maintainers, please make sure to merge all relevant open bugs until Tuesday morning 11:00 AM TLV time (10:00 CET). https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Every package build (i.e oVirt product) - please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag will be: ovirt-engine-3.6.2, and target release must be: 3.6.2)

1 0

Re: [ovirt-devel] [ovirt-users] Nested KVM - vdsm-hook-nestedvt
by Eyal Edri 03 Jan '16

03 Jan '16

adding also devel, some developers might be able to help. e. On Fri, Jan 1, 2016 at 4:32 PM, Winfried de Heiden <wdh(a)dds.nl> wrote: > Hi all and happy new year! > > I'm running oVirt 3.6 on EL7. > > In order to test nested-kvm I installed vdsm-hook-nestedvt on the > hypervisor and put "fake_kvm_support = true" in /etc/vdsm/vdsm.conf. > > However, afterwards the hypervisor host cannot connect to the ovirt > Manager, on ovirt Manager the engine.log will tell: > > 2016-01-01 15:21:42,105 WARN > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (DefaultQuartzScheduler_Worker-76) [71d1638c] Correlation ID: 29daf92c, > Call Stack: null, Custom Event ID: -1, Message: Host bigvirt moved to > Non-Operational state as host does not meet the cluster's minimum CPU > level. Missing CPU features : model_Opteron_G3 > > After removing the option all works well again, but I'ḿ lacking the nested > kvm option :( Is nested kvm only supported on a limited cpu's?? > > Winny > > Information from /proc/cpuinfo: > > processor : 0 > vendor_id : AuthenticAMD > cpu family : 16 > model : 10 > model name : AMD Phenom(tm) II X6 1055T Processor > stepping : 0 > microcode : 0x10000bf > cpu MHz : 2800.000 > cache size : 512 KB > physical id : 0 > siblings : 6 > core id : 0 > cpu cores : 6 > apicid : 0 > initial apicid : 0 > fpu : yes > fpu_exception : yes > cpuid level : 6 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc > extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm > extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt > cpb hw_pstate npt lbrv svm_lock nrip_save pausefilter > bogomips : 5625.54 > TLB size : 1024 4K pages > clflush size : 64 > cache_alignment : 64 > address sizes : 48 bits physical, 48 bits virtual > power management: ts ttp tm stc 100mhzsteps hwpstate cpb > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > -- Eyal Edri Associate Manager EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Re: [ovirt-devel] [VDSM] Running make check on *your* development machine
by Nir Soffer 03 Jan '16

03 Jan '16

On Tue, Dec 29, 2015 at 7:04 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: > On Tue, Dec 29, 2015 at 6:29 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> Hi all, >> >> Recently we added a new test, breaking make check when run on a >> development >> machine as non-privileged user. >> https://gerrit.ovirt.org/50984 >> >> This test pass on the CI environment, because the tests are running as >> root. > > > Should we do something different in CI? We should, but I want to discuss this in the devel mailing list. Nir > Y. > >> >> >> Please verify that "make check" is successful on your development >> environment. >> otherwise, you may break the tests for others using this practice. >> >> >> Best practice for running the tests: >> >> 1. Run the tests for the module you change: >> >> $ ./run_tests_local.sh rwlock_test.py >> nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] >> rwlock_test.RWLockStressTests >> test_fairness(1, 2) SKIP: >> Stress tests are disabled >> test_fairness(2, 8) SKIP: >> Stress tests are disabled >> test_fairness(3, 32) SKIP: >> Stress tests are disabled >> test_fairness(4, 128) SKIP: >> Stress tests are disabled >> rwlock_test.RWLockTests >> test_concurrent_readers OK >> test_demotion_no_waiters OK >> test_demotion_with_blocked_reader SKIP: >> Slow tests are disabled >> test_demotion_with_blocked_writer SKIP: >> Slow tests are disabled >> test_exclusive_context_blocks_reader SKIP: >> Slow tests are disabled >> test_exclusive_context_blocks_writer SKIP: >> Slow tests are disabled >> test_fifo SKIP: >> Slow tests are disabled >> test_promotion_forbidden OK >> test_recursive_read_lock OK >> test_recursive_write_lock OK >> test_release_other_thread_read_lock OK >> test_release_other_thread_write_lock OK >> test_shared_context_allows_reader OK >> test_shared_context_blocks_writer SKIP: >> Slow tests are disabled >> test_wakeup_all_blocked_readers SKIP: >> Slow tests are disabled >> test_wakeup_blocked_reader SKIP: >> Slow tests are disabled >> test_wakeup_blocked_writer SKIP: >> Slow tests are disabled >> >> ---------------------------------------------------------------------- >> Ran 21 tests in 0.005s >> >> This should be very fast and should run after every change. >> >> 2. Check that slow and stress tests pass >> >> Some modules have @slowtest and @stresstest, which are skipped by default. >> When modifying such modules, enable also these tests: >> >> $ ./run_tests_local.sh rwlock_test.py --enable-slow-tests >> --enable-stress-tests >> nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] >> rwlock_test.RWLockStressTests >> test_fairness(1, 2) OK >> test_fairness(2, 8) OK >> test_fairness(3, 32) OK >> test_fairness(4, 128) OK >> rwlock_test.RWLockTests >> test_concurrent_readers OK >> test_demotion_no_waiters OK >> test_demotion_with_blocked_reader SKIP: >> Known issue in current code >> test_demotion_with_blocked_writer OK >> test_exclusive_context_blocks_reader OK >> test_exclusive_context_blocks_writer OK >> test_fifo OK >> test_promotion_forbidden OK >> test_recursive_read_lock OK >> test_recursive_write_lock OK >> test_release_other_thread_read_lock OK >> test_release_other_thread_write_lock OK >> test_shared_context_allows_reader OK >> test_shared_context_blocks_writer OK >> test_wakeup_all_blocked_readers OK >> test_wakeup_blocked_reader OK >> test_wakeup_blocked_writer OK >> >> ---------------------------------------------------------------------- >> Ran 21 tests in 14.054s >> >> This may take more time. >> >> 3. When the module tests pass, run "make check" >> >> make check >> >> This takes about 90 seconds. >> >> To run all tests, including slow and stress tests, use: >> >> make check-all >> >> This may take couple of minutes, so it is not recommended. >> >> Thanks, >> Nir >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel > >

2 1