[VDSM] network test fails again on ovirt-4.0 branch
by Nir Soffer
Hi all,
This test seems to fail too much. Maybe we should mark it as broken in ovirt-4.0
branch?
I tried 2 builds in a raw and it failed in both. The patch is of
course not related,
increating ioprocess required version.
14:14:04 ======================================================================
14:14:04 FAIL: test_events_keys (netlinkTests.NetlinkEventMonitorTests)
14:14:04 ----------------------------------------------------------------------
14:14:04 Traceback (most recent call last):
14:14:04 File
"/home/jenkins/workspace/vdsm_3.6_check-patch-fc23-x86_64/vdsm/tests/testValidation.py",
line 105, in wrapper
14:14:04 return f(*args, **kwargs)
14:14:04 File
"/home/jenkins/workspace/vdsm_3.6_check-patch-fc23-x86_64/vdsm/tests/netlinkTests.py",
line 133, in test_events_keys
14:14:04 % (1 + len(expected_events)))
14:14:04 AssertionError: 5 expected events have not been caught (in
the right order)
14:14:04 -------------------- >> begin captured logging << --------------------
14:14:04 root: DEBUG: /usr/bin/taskset --cpu-list 0-3 /sbin/ip link
add name dummy_7odCO type dummy (cwd None)
14:14:04 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0
14:14:04 root: DEBUG: /usr/bin/taskset --cpu-list 0-3 /sbin/ip -4 addr
add dev dummy_7odCO 192.0.2.1/24 (cwd None)
14:14:04 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0
14:14:04 root: DEBUG: /usr/bin/taskset --cpu-list 0-3 /sbin/ip link
set dev dummy_7odCO up (cwd None)
14:14:04 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0
14:14:04 root: DEBUG: /usr/bin/taskset --cpu-list 0-3 /sbin/ip link
del dev dummy_7odCO (cwd None)
14:14:04 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0
14:14:04 --------------------- >> end captured logging << ---------------------
Nir
7 years, 7 months
Updating permissions on gerrit.ovirt.org
by Shlomo Ben David
Hi All,
On the upcoming days i'm going to update permissions on gerrit.ovirt.org
server.
The changes shouldn't reflect on the current state but if you'll encounter
with any permission issues or other issues related to gerrit.ovirt.org
server please let me or infra(a)ovirt.org to know and we'll handle it ASAP.
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
7 years, 7 months
Fwd: [Fedora Update] [comment] unboundid-ldapsdk-3.2.0-1.fc25
by Sandro Bonazzola
Hi, can you please verify and provide karma / feedback?
Let me know if you want it in fedora 24 / el7 for 4.1.
Thanks,
---------- Forwarded message ----------
From: <updates(a)fedoraproject.org>
Date: Fri, Sep 23, 2016 at 5:48 PM
Subject: [Fedora Update] [comment] unboundid-ldapsdk-3.2.0-1.fc25
To: sbonazzo(a)redhat.com
The following comment has been added to the unboundid-ldapsdk-3.2.0-1.fc25
update:
bodhi - 2016-09-23 15:48:04.354424 (karma: 0)
This update has been submitted for testing by sbonazzo.
To reply to this comment, please visit the URL at the bottom of this mail
============================================================
====================
unboundid-ldapsdk-3.2.0-1.fc25
============================================================
====================
Update ID: FEDORA-2016-8d76d37c62
Release: Fedora 25
Status: pending
Type: enhancement
Karma: 0
Request: testing
Bugs: 1378924 - None
Notes: See upstream announcements: [UnboundID LDAP SDK for Java
: 3.2.0](https://github.com/UnboundID/ldapsdk/releases/t
: ag/3.2.0)
Submitter: sbonazzo
Submitted: 2016-09-23 15:48:03.985342
Comments: bodhi - 2016-09-23 15:48:04.354424 (karma 0)
This update has been submitted for testing by
sbonazzo.
https://bodhi.fedoraproject.org/updates/FEDORA-2016-8d76d37c62
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
<https://www.redhat.com/it/about/events/red-hat-open-source-day-2016>
7 years, 8 months
[VDSM] Improving vdsm logging format
by Nir Soffer
Hi all,
We are reviewing patches for improving vdsm log format.
The goal is to have more standard logging format, similar to engine
logs and other logs in the ovirt project, to make it easier to debug
and support the system.
We know that this change will break tools people wrote to parse vdsm
logs (I wrote couple), but we find vdsm log format too painful to work
with, and we hope this is be useful in the long term.
Please review.
https://gerrit.ovirt.org/#/q/topic:log-format
Thanks,
Nir
7 years, 8 months
[VDSM] New network test failure - ctypes.ArgumentError: argument 3: <class 'TypeError'>: wrong type
by Nir Soffer
Failed only one patch when building 4, so this looks like
a random failure, but the error is disturbing.
See http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/2255/con...
17:00:31 ======================================================================
17:00:31 ERROR: test_bond_create_failure_on_slave_add
(network.link_bond_test.LinkBondTests)
17:00:31 ----------------------------------------------------------------------
17:00:31 Traceback (most recent call last):
17:00:31 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/network/link_bond_test.py",
line 83, in test_bond_create_failure_on_slave_add
17:00:31 base_bond.add_slaves((nic1, nic2))
17:00:31 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/lib/vdsm/network/link/bond.py",
line 153, in add_slaves
17:00:31 with _preserve_iface_state(slave):
17:00:31 File "/usr/lib64/python3.5/contextlib.py", line 59, in __enter__
17:00:31 return next(self.gen)
17:00:31 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/lib/vdsm/network/link/bond.py",
line 214, in _preserve_iface_state
17:00:31 dev_was_up = iface.is_up(dev)
17:00:31 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/lib/vdsm/network/link/iface.py",
line 54, in is_up
17:00:31 return is_admin_up(dev)
17:00:31 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/lib/vdsm/network/link/iface.py",
line 58, in is_admin_up
17:00:31 return is_link_up(get_link(dev)['flags'], check_oper_status=False)
17:00:31 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/lib/vdsm/network/netlink/link.py",
line 56, in get_link
17:00:31 with _get_link(name=name, sock=sock) as link:
17:00:31 File "/usr/lib64/python3.5/contextlib.py", line 59, in __enter__
17:00:31 return next(self.gen)
17:00:31 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/lib/vdsm/network/netlink/link.py",
line 199, in _get_link
17:00:31 err = _rtnl_link_get_kernel(sock, index, name, byref(link))
17:00:31 ctypes.ArgumentError: argument 3: <class 'TypeError'>: wrong type
17:00:31 -------------------- >> begin captured logging << --------------------
17:00:31 2016-09-20 17:00:12,586 WARNING [py.warnings] (MainThread)
/usr/lib/python3.5/site-packages/nose/util.py:453: DeprecationWarning:
inspect.getargspec() is deprecated, use inspect.signature() instead
17:00:31 inspect.getargspec(func)
17:00:31 (inspect:1041)
17:00:31 2016-09-20 17:00:12,587 INFO [root] (MainThread) Bond
check_7lzvb has been created. (bond:142)
17:00:31 2016-09-20 17:00:12,598 INFO [root] (MainThread) Bond
check_7lzvb has been destroyed. (bond:149)
17:00:31 2016-09-20 17:00:12,598 DEBUG [root] (MainThread)
/usr/bin/taskset --cpu-list 0-15 /sbin/ip link add name dummy_Dmwc5
type dummy (cwd None) (commands:69)
17:00:31 2016-09-20 17:00:12,607 DEBUG [root] (MainThread) SUCCESS:
<err> = b''; <rc> = 0 (commands:93)
17:00:31 2016-09-20 17:00:12,608 DEBUG [root] (MainThread)
/usr/bin/taskset --cpu-list 0-15 /sbin/ip link add name dummy_xIK5C
type dummy (cwd None) (commands:69)
17:00:31 2016-09-20 17:00:12,615 DEBUG [root] (MainThread) SUCCESS:
<err> = b''; <rc> = 0 (commands:93)
17:00:31 2016-09-20 17:00:12,617 INFO [root] (MainThread) Bond
bond_rwTTFu has been created. (bond:142)
17:00:31 2016-09-20 17:00:12,634 INFO [root] (MainThread) Bond
bond_rwTTFu has been destroyed. (bond:149)
17:00:31 2016-09-20 17:00:12,634 DEBUG [root] (MainThread)
/usr/bin/taskset --cpu-list 0-15 /sbin/ip link del dev dummy_Dmwc5
(cwd None) (commands:69)
17:00:31 2016-09-20 17:00:12,658 DEBUG [root] (MainThread) SUCCESS:
<err> = b''; <rc> = 0 (commands:93)
17:00:31 2016-09-20 17:00:12,659 DEBUG [root] (MainThread)
/usr/bin/taskset --cpu-list 0-15 /sbin/ip link del dev dummy_xIK5C
(cwd None) (commands:69)
17:00:31 2016-09-20 17:00:12,676 DEBUG [root] (MainThread) SUCCESS:
<err> = b''; <rc> = 0 (commands:93)
17:00:31 --------------------- >> end captured logging << ---------------------
7 years, 8 months
[Review-request] feature page for gdeploy cockpit integration
by Ramesh Nachimuthu
------=_Part_588440_2098117827.1474467174872
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Hi,
We are planning to integrate gdeploy with cockpit-ovirt plugin to improve the deployment of Hyper-Converged oVrt-Gluster solution. I have sent a pull request to add a feature page for the same. It will helpful if you can review and provide your valuable feedback.
Pull request : https://github.com/oVirt/ovirt-site/pull/480
Regards,
Ramesh
------=_Part_588440_2098117827.1474467174872
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>
</div><p>Hi,<br>
<br>
We are planning to integrate <a href="https://github.com/gluster/gdeploy" target="_blank">gdeploy</a> with
cockpit-ovirt plugin to improve the deployment of Hyper-Converged
oVrt-Gluster solution. I have sent a <a href="https://github.com/oVirt/ovirt-site/pull/480" target="_blank">pull request
</a>to add a feature page for the same. It will helpful if you can
review and provide your valuable feedback. <br>
</p><div>
</div><p>Pull request : <a href="https://github.com/oVirt/ovirt-site/pull/480" target="_blank"></a><a class="moz-txt-link-freetext" href="https://github.com/oVirt/ovirt-site/pull/480" target="_blank">https://github.com/oVirt/ovirt-site/pull/480</a></p><div>
Regards,<br>
Ramesh<br>
</div></div></body></html>
------=_Part_588440_2098117827.1474467174872--
7 years, 8 months
Best (and up-to-date) practices for developers?
by Martin Sivak
Hi,
I just wanted to find out if we have some documentation for the
developers that would give hint on different aspects of the engine
development in terms of coding.
Like:
- code style (we have the config in sources)
- what libraries are (not) allowed (guava..ehm..)
- how should CDI be used (see https://gerrit.ovirt.org/#/c/63747/)
- what files need to be touched to properly support translations
- ...
It would be cool to have something brief we can search easily. I know
it can get outdated fast, but if we use it only for the important
stuff and review it for each major release (as the major rules do not
change much) we should be able to keep it usable.
--
Martin Sivák
SLA / oVirt
7 years, 8 months
Proposing Martin Sivak as a Backend Maintainer for SLA & Scheduling
by Doron Fediuck
Hi All,
Martin Sivak has been working on the oVirt engine since June 2013.
His main focus over the years was around MoM, external scheduler,
hosted-engine, and
related engine code.
In the past year Martin took over many of the oVirt scheduler related
work and did a lot of improvements there. In total Martin has around
170 engine patches already merged.
Within these you will find improving the scheduler's notifications and
error handling, rewriting the pending resource mechanism which
resolved many issues, VM affinity, affinity labels and multiple
improvements for our scheduling policies and hosted engine.
I would like to thank Martin for his great contribution and hope for
many more patches to come :)
I would also like to propose Martin as an engine maintainer for SLA
and Scheduling.
Thanks, Doron
7 years, 8 months
Upgrade storage domains' version to V4 for 4.1 DCs
by Maor Lipchuk
Hi all,
Few moments ago I've merged the Data Center 4.1 upgrade patches (see [1])
The patches introduce a change in the storage domains' meta data to version
4 which are attached to a 4.1 Data Center
Currently, there are no differences between version 3 and version 4, but
the plan will be to add extra functionalities to V4 storage domains such as
supporting qcow 1.1
For those of you which already have a 4.1 DC, you might encounter some
problems since your storage domains are still configured as V3 and should
be upgraded.
For your master environment to be compatible with those changes the
following changes should be performed:
* In the engine side:
1. Change the storage domains version from V3 to V4:
update storage_domain_static set storage_domain_format_type = 4 where id
= (SELECT id from storage_domains where storage_pool_name = '{Data Center
name}');
2. Change the storage pool format type to 4:
update storage_pool set storage_pool_format_type = 4 where name = '{Data
Center name}';
* In the VDSM side:
1. call the upgradeStoragePool verb:
vdsClient -s 0 upgradeStoragePool {storage_pool_id} 4
Please let me know if you encounter any issues
Regards,
Maor
[1]
https://gerrit.ovirt.org/#/c/63637/
https://gerrit.ovirt.org/#/c/63717/
https://gerrit.ovirt.org/#/c/63547/
7 years, 8 months
