May 2016 - Devel - oVirt List Archives

[vdsm] what happens to ovirmgmt during new host deployment?
by Kai Kang 31 May '16

31 May '16

Hi, I sent mails to ovirt-user maillist for help. But it seems there is no useful info in vdsm.log and supervdsm.log. I want to debug the code and so ask for help here. I am using ovirt 3.6.4.1 and vdsm 4.17.24. When deploy a new host, bridge ovirtmgmt has been created with port eth0. But it fails with: Host dell12 does not comply with the cluster Default networks, the following networks are missing on host: 'ovirtmgmt' I can make ovirtmgmt work by selecting the tab 'Hosts' -> node name(dell12) -> subtab 'Network Interface', click 'Setup Host Networks', drag ovirtmgmt to link with ethernet interface eth0. What engine did to bridge ovirtmgmt during new host deployment? Just call "getVdsCaps" to check whether ovirtmgmt is ready or sent setupNetwork command to configure ovirtmgmt? Which part of vdsm code should I check please? Thanks a lot. --Kai

3 3

oVirt 3.6.7 rc2 build planned
by Sandro Bonazzola 30 May '16

30 May '16

Same for 3.6.7 rc2 On Mon, May 30, 2016 at 4:12 PM, Simone Tiraboschi <stirabos(a)redhat.com> wrote: > Fyi oVirt developers, > > An oVirt build is planned for this Tuesday 11:00 AM TLV time (10:00 AM > CEST). > Taking into consideration the time it takes for Jenkins to run a full > CI everything need to be backported by Monday 11PM. > Please make sure to mark as verified and CR +2 so it will be ready for > merging Tuesday morning. > > > https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt 4.0 rc1 merge / tag / bugzilla reminder
by Simone Tiraboschi 30 May '16

30 May '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%3A4.0.… 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-4.0.0_rc1, tr: 4.0.0). Please take care that rc1 is something that potentially could be released if ok, so it's the time to drop suffixes like githash, snapshot and so on.

1 0

oVirt 4.0 rc1 build planned
by Simone Tiraboschi 30 May '16

30 May '16

Fyi oVirt developers, An oVirt build is planned for this Tuesday 11:00 AM TLV time (10:00 AM CEST). Taking into consideration the time it takes for Jenkins to run a full CI everything need to be backported by Monday 11PM. Please make sure to mark as verified and CR +2 so it will be ready for merging Tuesday morning. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.…

1 0

[vdsm][heads up] Vdsm branching out for oVirt 4.0.x
by Francesco Romani 30 May '16

30 May '16

Hi all, We will soon create the stable branch for 4.0.x. So far the proposed date is Monday, 30 May 2016 (around noon UTC+2). This date is not yet fully agreed so there still room for change; We should branch out as soon as possible to stabilize the branch, but I know Nir's monitoring enhancement is not yet merged, I think this is important enough to deserve a (small) extension. But I would like to keep this as only extension. Please share your thoughts. Bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

1 1

Weekly bug status for ovirt-system-tests (using Lago) [ 29/05/16 ]
by Eyal Edri 29 May '16

29 May '16

FYI, Some updates from recent activity on ovirt-system-tests running on Lago. *New training videos:* overview of the framework running on Lago - https://bluejeans.com/s/9FaJ/ <https://mojo.redhat.com/external-link.jspa?url=https%3A%2F%2Fbluejeans.com%…> hands on session on installing and running OST - https://bluejeans.com/s/9Iy0/ <https://mojo.redhat.com/external-link.jspa?url=https%3A%2F%2Fbluejeans.com%…> *Open bugs:* https://goo.gl/eUaPUY *Open issues:* Work is being done to allow running OST locally per patch and on CI per merge.. more news to come soon *Open patches:* (reviews are welcome) https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:open * Some patches are open on simplification and cleanup of the tests, should be merged this week. * This is part of preparing ovirt-system-tests to support running tests per commit. *Jenkins jobs: (STABLE!)* http://jenkins.ovirt.org/view/oVirt%20system%20tests/ 3.6 & master tests are stable and running on nightlies - please watch out for any new errors, they probably mean there is a regression! 3.6 NGN job is failing - Tolik/David - do we know what the issue is? *Recently merged patches:* https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:merged+since… > -- 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] Handling of scripts without a .py suffix
by Nir Soffer 29 May '16

29 May '16

Hi all, We have several scripts spread in the source, typically installed in /usr/libexec/vdsm. We had a useless WHITELIST[1], trying to compile these scripts with python3, and we have similar (but working) whitelist for pyflakes and pep8. To simplify the various checks, I think we need to to do this: 1. Keep .py suffix for all python files 2. Move all scripts to helpers/ ([2] handles storage scripts) 3. During installation, strip the .py suffix. With these changes, we can use the various checking commands on the entire source tree. For example, these commands check the entire tree: PYTHONDONTWRITEBYTECODE=1 python3 -m compileall -f -x '(\.tox/|\.git/)' . pep8 . pyflakes . Thoughts? [1] https://gerrit.ovirt.org/58204 [2] https://gerrit.ovirt.org/57363 Nir

3 6

New network test failure
by Nir Soffer 29 May '16

29 May '16

Just found a new failure, I don't remember seeing it - another timing issue? 13:10:47 ====================================================================== 13:10:47 FAIL: test_local_auto_with_static_address_without_ra_server (network.netinfo_test.TestIPv6Addresses) 13:10:47 ---------------------------------------------------------------------- 13:10:47 Traceback (most recent call last): 13:10:47 File "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/testValidation.py", line 97, in wrapper 13:10:47 return f(*args, **kwargs) 13:10:47 File "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/network/netinfo_test.py", line 405, in test_local_auto_with_static_address_without_ra_server 13:10:47 self.assertEqual(1, len(ip_addrs)) 13:10:47 AssertionError: 1 != 2 13:10:47 -------------------- >> begin captured logging << -------------------- 13:10:47 2016-05-29 13:10:39,164 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip link add name dummy_l0sTK type dummy (cwd None) 13:10:47 2016-05-29 13:10:39,193 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 13:10:47 2016-05-29 13:10:39,194 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip -6 addr add dev dummy_l0sTK 2001::88/64 (cwd None) 13:10:47 2016-05-29 13:10:39,236 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 13:10:47 2016-05-29 13:10:39,242 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip link del dev dummy_l0sTK (cwd None) 13:10:47 2016-05-29 13:10:39,289 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 13:10:47 --------------------- >> end captured logging << ---------------------

1 0

mount test failure
by Piotr Kliczewski 26 May '16

26 May '16

I noticed build failure [1] with: 11:03:56 ====================================================================== 11:03:56 ERROR: testLoopMount (mountTests.MountTests) 11:03:56 ---------------------------------------------------------------------- 11:03:56 Traceback (most recent call last): 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testValidation.py", line 97, in wrapper 11:03:56 return f(*args, **kwargs) 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/mountTests.py", line 133, in testLoopMount 11:03:56 m.mount(mntOpts="loop") 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/storage/mount.py", line 219, in mount 11:03:56 timeout=timeout, cgroup=cgroup) 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/storage/mount.py", line 275, in _mount 11:03:56 _runcmd(cmd, timeout) 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/storage/mount.py", line 310, in _runcmd 11:03:56 raise MountError(rc, ";".join((out, err))) 11:03:56 MountError: (32, ';mount: /tmp/tmptchBPu: failed to setup loop device: No such file or directory\n') 11:03:56 -------------------- >> begin captured logging << -------------------- 11:03:56 2016-05-25 07:01:50,432 DEBUG [Storage.Misc.excCmd] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/mkfs.ext2 -F /tmp/tmptchBPu (cwd None) 11:03:56 2016-05-25 07:01:50,848 DEBUG [Storage.Misc.excCmd] (MainThread) SUCCESS: <err> = 'mke2fs 1.42.13 (17-May-2015)\n'; <rc> = 0 11:03:56 2016-05-25 07:01:50,849 INFO [storage.Mount] (MainThread) mounting /tmp/tmptchBPu at /var/tmp/tmpNYrdxK 11:03:56 2016-05-25 07:01:50,849 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /usr/bin/mount -o loop /tmp/tmptchBPu /var/tmp/tmpNYrdxK (cwd None) 11:03:56 --------------------- >> end captured logging << --------------------- 11:03:56 11:03:56 ====================================================================== 11:03:56 ERROR: testSymlinkMount (mountTests.MountTests) 11:03:56 ---------------------------------------------------------------------- 11:03:56 Traceback (most recent call last): 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testValidation.py", line 97, in wrapper 11:03:56 return f(*args, **kwargs) 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/mountTests.py", line 157, in testSymlinkMount 11:03:56 m.mount(mntOpts="loop") 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/storage/mount.py", line 219, in mount 11:03:56 timeout=timeout, cgroup=cgroup) 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/storage/mount.py", line 275, in _mount 11:03:56 _runcmd(cmd, timeout) 11:03:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/storage/mount.py", line 310, in _runcmd 11:03:56 raise MountError(rc, ";".join((out, err))) 11:03:56 MountError: (32, ';mount: /var/tmp/tmp4S4yaR/backing.img: failed to setup loop device: No such file or directory\n') 11:03:56 -------------------- >> begin captured logging << -------------------- 11:03:56 2016-05-25 07:01:51,291 DEBUG [Storage.Misc.excCmd] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/mkfs.ext2 -F /var/tmp/tmp4S4yaR/backing.img (cwd None) 11:03:56 2016-05-25 07:01:52,964 DEBUG [Storage.Misc.excCmd] (MainThread) SUCCESS: <err> = 'mke2fs 1.42.13 (17-May-2015)\n'; <rc> = 0 11:03:56 2016-05-25 07:01:52,964 INFO [storage.Mount] (MainThread) mounting /var/tmp/tmp4S4yaR/link_to_image at /var/tmp/tmp4S4yaR/mountpoint 11:03:56 2016-05-25 07:01:52,964 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /usr/bin/mount -o loop /var/tmp/tmp4S4yaR/link_to_image /var/tmp/tmp4S4yaR/mountpoint (cwd None) 11:03:56 --------------------- >> end captured logging << --------------------- Thanks, Piotr [1] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/2171

2 1

incompatible otopi 1.5.0-rc1 released
by Yedidyah Bar David 26 May '16

26 May '16

Hi all, I now merged and published to maven central otopi-1.5.0-rc1. It includes an incompatible change to the machine dialog protocol. If you have an engine machine with the new otopi and your engine uses an older one, host-deploy will fail with the message: Invalid data recieved during bootstrap To fix, you should rebuild your engine with the new otopi. To get it, either use the one in maven central, or install to your local maven cache by cloning/checking out otopi master branch and: autoreconf -ivf ./configure --enable-java-sdk --with-maven make A patch for the engine to require the newer version [1] will be merged soon. [1] https://gerrit.ovirt.org/57472 Best, -- Didi

1 0