[ovirt-devel] make check on master fails due to UnicodeDecodeError

2018-04-10 Thread Shani Leviim
Hi there, I'm trying to run make check, and I have ~13 tests on vdsm/tests which failes due to the following: File "/home/sleviim/git/vdsm/lib/vdsm/api/vdsmapi.py", line 212, in __init__ loaded_schema = pickle.load(f) File "/usr/lib64/python3.6/encodings/ascii.py", line 26, in decode

Re: [ovirt-devel] make check on master fails due to UnicodeDecodeError

2018-04-10 Thread Shani Leviim
Hi, Yes, I did clean the root directory but it didn't solve the issue. I'm currently running the tests on fedora27, using python version 2.1.14. Thanks to Dan's help, it seems that we found the root cause: I had 2 pickle files under /var/cache/vdsm/schema: vdsm-api.pickle and

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-10 Thread Alona Kaplan
Hi all, Looking at the log it seems that the new GetCapabilitiesAsync is responsible for the mess. - * 08:29:47 - engine loses connectivity to host 'lago-basic-suite-4-2-host-0'.* *- Every 3 seconds a getCapabalititiesAsync request is sent to the host (unsuccessfully).* * before each

Re: [ovirt-devel] make check on master fails due to UnicodeDecodeError

2018-04-10 Thread Nir Soffer
On Tue, Apr 10, 2018 at 5:21 PM Shani Leviim wrote: > Hi, > > Yes, I did clean the root directory but it didn't solve the issue. > I'm currently running the tests on fedora27, using python version 2.1.14. > > Thanks to Dan's help, it seems that we found the root cause: > > I

Re: [ovirt-devel] make check on master fails due to UnicodeDecodeError

2018-04-10 Thread Nir Soffer
On Tue, Apr 10, 2018 at 2:52 PM Shani Leviim wrote: > Hi there, > I'm trying to run make check, and I have ~13 tests on vdsm/tests which > failes due to the following: > > File "/home/sleviim/git/vdsm/lib/vdsm/api/vdsmapi.py", line 212, in > __init__ > loaded_schema =

[ovirt-devel] dynamic ownership changes

2018-04-10 Thread Martin Polednik
Hey, I've created a patch[0] that is finally able to activate libvirt's dynamic_ownership for VDSM while not negatively affecting functionality of our storage code. That of course comes with quite a bit of code removal, mostly in the area of host devices, hwrng and anything that touches

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-10 Thread Gal Ben Haim
I'm seeing the same error in [1], during 006_migrations.migrate_vm. [1] http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1650/ On Tue, Apr 10, 2018 at 4:14 PM, Alona Kaplan wrote: > Hi all, > > Looking at the log it seems that the new GetCapabilitiesAsync is >

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-10 Thread Ravi Shankar Nori
Working on a patch will post a fix Thanks Ravi On Tue, Apr 10, 2018 at 9:14 AM, Alona Kaplan wrote: > Hi all, > > Looking at the log it seems that the new GetCapabilitiesAsync is > responsible for the mess. > > - > * 08:29:47 - engine loses connectivity to host

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-10 Thread Ravi Shankar Nori
This [1] should fix the multiple release lock issue [1] https://gerrit.ovirt.org/#/c/90077/ On Tue, Apr 10, 2018 at 3:53 PM, Ravi Shankar Nori wrote: > Working on a patch will post a fix > > Thanks > > Ravi > > On Tue, Apr 10, 2018 at 9:14 AM, Alona Kaplan

[ovirt-devel] planned Jenkins restart

2018-04-10 Thread Evgheni Dereveanchin
Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new jobs will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin ___ Devel mailing list Devel@ovirt.org

Re: [ovirt-devel] planned Jenkins restart

2018-04-10 Thread Evgheni Dereveanchin
Maintenance completed, Jenkins back up and running. The OS, Jenkins core and all plugins were updated: *https://ovirt-jira.atlassian.net/browse/OVIRT-1937 * As always - if you see any issues please report them to Jira. Regards, Evgheni