[ovirt-devel] oVirt Node Next - Sprint 2 Summary

[Fabian Deutsch]

Hey,

during our second sprint, lasting 3 weeks, ending on January 15, the
Node team worked on the following items:

Add ovirt-release-host-node
---
This subpackage of ovirt-release now has all teh dependencies which
are expected to be available on node. In addition to vdsm, this
package also depends on cockpit and imgbased.
In addition this file carries systemd presets, to enable the relevant
services, it also provides the firewalld configuration of Node.
It also set's the VARIANT fields in teh os-release file to identify
node in a non-invasive way.
https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=tree;f=ovirt-release-master;h=92d417ad14a854f3f8872c90a97cb4f48a383ca8;hb=HEAD

Add branding to ovirt-release-host-node

This is part of the next sprint but already completed: The release
file now also provides oVirt branding for cockpit!
https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=tree;f=ovirt-release-master/host-node/cockpit;h=7a4149adb1aa14d004dad7fcb5fb6fb9baa19d27;hb=HEAD

Move imgbased to gerrit
---
imgbased is the component taking care of the image management on node.
Previously it was hosted on github, now it's on gerrit:
https://gerrit.ovirt.org/gitweb?p=imgbased.git

Yaml-ize imgbased and ovirt-node-ng jobs

The ovirt-node-ng repository holds the image recipe (and nothing
else), this repo was created adn yaml-ized and is building on jenkins.
The job for imgbased was also yamlized and is alos building on jenkins:
http://jenkins.ovirt.org/job/imgbased_master_build-artifacts-el7-x86_64/
http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc23-x86_64/

Next
---
In the next sprint - 3 - the team will focus on further stabilizing
the jenkins builds, creating the update rpm and creating the required
disk layout during installation.


The bottom line is that the ovirt-node-ng image is now regularly build
in u/s - still a bit flaky, but it's there. The squashfs can be used
for installing node, as described here:
http://lists.ovirt.org/pipermail/devel/2016-January/012073.html


On behalf of the Node team
fabian
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] vdsm] tag and branch ovirt 3.6.2 RC3

[Francesco Romani]

Hi,

Sorry for the short notice of this email.

the state of branch ovirt-3.6 is as follows

tag sha subject 
bug target release  
--
de54e59 virt: Don't expose GuestAgent.guestInfo directly
1295428 3.6.3
83c4ac8 supervdsm: failed validateAccess leaves pipes open  
1271575 3.6.3
37bda50 vm: safer handling of conf in restore   
1296936 3.6.3
57b1814 virt: safer handling of migration parameters
1296936 3.6.3
9b29ddd lun: Serial attr should not passed to libvirt for lun disks.
1291930 3.6.2 
7b94531 migration: use context manager for semaphore
1296936 3.6.3   
508b2fd virt: Correct epoll unregistration usage in vmchannels  
1226911 3.6.3
68a1b69 virt: Set cloexec flag on channel sockets   
1226911 3.6.3
4.17.17 505026d spec: require libvirt to fix hotplugging

So, for the next tag the plan is to

1. branch out ovirt-3.6.2 from tag 4.17.17. This branch is expected to be 
short-lived (basically only for this RC).
2. apply commit 9b29ddd only
3. tag 4.17.18 from branch ovirt-3.6.2

I see we have only two patches in queue for ovirt-3.6

https://gerrit.ovirt.org/#/c/52346/
https://gerrit.ovirt.org/#/c/52348/

Do we need them in this build?

Should we require another 3.6.2 build, backports will be needed ALSO on branch 
ovirt-3.6.2.

Will start implement the plan before lunch if noone objects.

Thanks

-- 
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] oVirt 3.6.2 RC3 build starting

[Sandro Bonazzola]

Fyi oVirt products maintainers,
An oVirt build for an official release 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
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Jenkins overload and cancellation of ~1000 jobs

[David Caro]

Hi everyone,

Earlier today there was a huge load peak in jenkins that ended up with
a job queue > 1000, we just removed from the queue most of the jobs to
avoid stop servicing other projects (like for example the jobs related
to releases and similar).


That means that a lot of patches (mostly ovirt-engine) might get -1 or
at least an error from jenkins, feel free to manually retrigger those
patches here [1]


[1] http://jenkins.ovirt.org/gerrit_manual_trigger/


Sorry for the inconveniences,

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Hello statement on Ovirt VM.

[신민수]

 Here is South Korea. Current through the ovirt engin you try to install the 
VM after creating Mint OS. Not install the screen moves during setup, it will 
stop as it is. We will let you know you do not have the support for possibly is 
Once from ovirt engin mint os. Website address of mint OS is, http: 
//hamonikr.org/ is here. Without download and install the Live CD, we will 
contact you. Could you please confirm. Thank you very much. 
  
=
(주)강원시스템 영동지사 신민수 대리
Tel : 033-631-8501, 8502 
Fax : 033-631-8503
Mob : 010-8713-1314 
e-mail : mss...@kwsystem.co.kr
mss...@naver.com
add : 강원도 속초시 교동 737-7 아남프라자 1314호 
(주)강원시스템 영동지사
=___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [vdsm] New schema format proposal

[Piotr Kliczewski]

I would like to propose new format for schema that we use in vdsm. I
started to work on a patch [1] where I explore how the new file should
look like. I have couple of goals which I would like to achieve by
doing this transformation:
1. I would like to use this file to verify engine code. Currently we
check only vdsm which leads to compatibility issues.
2. I would like to base new jsonrpc based replacement for vdsClient on
it. I want to create dynamic client which would use new format
(description used as help when calling verbs)
3. Simplify Bridge.py
4. Extend the schema to add events
5. Explore ideas around api evolution and contract definition.

Once we agree on the format I will work on script which will translate
one format to the other.

Thanks,
Piotr

[1] https://gerrit.ovirt.org/#/c/52404
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [vdsm] New schema format proposal

[Vinzenz Feenstra]

> On Jan 19, 2016, at 10:45 AM, Piotr Kliczewski  
> wrote:
> 
> I would like to propose new format for schema that we use in vdsm. I
> started to work on a patch [1] where I explore how the new file should
> look like. I have couple of goals which I would like to achieve by
> doing this transformation:
> 1. I would like to use this file to verify engine code. Currently we
> check only vdsm which leads to compatibility issues.
> 2. I would like to base new jsonrpc based replacement for vdsClient on
> it. I want to create dynamic client which would use new format
> (description used as help when calling verbs)
> 3. Simplify Bridge.py
> 4. Extend the schema to add events
> 5. Explore ideas around api evolution and contract definition.

+1 on the general direction

YAML is much more friendly to write by hand

nitpick on the format:


values: ['status', 'on', 'off', 'reboot'] 

vs 

values:
- status
- on
- off
- reboot

The result of the latter is also a list of strings which I find personally much 
more readable
Having to put there quotes is just a pain I really disliked about the JSON 
style description of our API schema

Anyway thanks :-)

> 
> Once we agree on the format I will work on script which will translate
> one format to the other.
> 
> Thanks,
> Piotr
> 
> [1] https://gerrit.ovirt.org/#/c/52404
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] vdsm] tag and branch ovirt 3.6.2 RC3

[Francesco Romani]

Done.

Pushed branch ovirt-3.6.2.

Also, tagged v4.17.18 from that branch

The only change since previous tag (4.17.17) is

tag v4.17.18
Tagger: Francesco Romani 
Date:   Tue Jan 19 13:08:36 2016 +0100

oVirt 3.6.2 RC3

commit 4b350cf86537f48cdbe4bbd5993bc4d761990aa1
Author: Maor Lipchuk 


Should we need another 3.6.2 build, please don't forget to push patches to 
3.6.2 branch as well.

Bests,

- Original Message -
> From: "Francesco Romani" 
> To: "devel" 
> Sent: Tuesday, January 19, 2016 9:59:59 AM
> Subject: [ovirt-devel] vdsm] tag and branch ovirt 3.6.2 RC3
> 
> Hi,
> 
> Sorry for the short notice of this email.
> 
> the state of branch ovirt-3.6 is as follows
> 
> tag   sha subject 
> bug target release
> --
>   de54e59 virt: Don't expose GuestAgent.guestInfo directly
> 1295428 3.6.3
>   83c4ac8 supervdsm: failed validateAccess leaves pipes open  
> 1271575 3.6.3
>   37bda50 vm: safer handling of conf in restore   
> 1296936 3.6.3
>   57b1814 virt: safer handling of migration parameters
> 1296936 3.6.3
>   9b29ddd lun: Serial attr should not passed to libvirt for lun disks.
>   1291930 3.6.2 
>   7b94531 migration: use context manager for semaphore
> 1296936 3.6.3
>   508b2fd virt: Correct epoll unregistration usage in vmchannels  
> 1226911
>   3.6.3
>   68a1b69 virt: Set cloexec flag on channel sockets   
> 1226911 3.6.3
> 4.17.17   505026d spec: require libvirt to fix hotplugging
> 
> So, for the next tag the plan is to
> 
> 1. branch out ovirt-3.6.2 from tag 4.17.17. This branch is expected to be
> short-lived (basically only for this RC).
> 2. apply commit 9b29ddd only
> 3. tag 4.17.18 from branch ovirt-3.6.2
> 
> I see we have only two patches in queue for ovirt-3.6
> 
> https://gerrit.ovirt.org/#/c/52346/
> https://gerrit.ovirt.org/#/c/52348/
> 
> Do we need them in this build?
> 
> Should we require another 3.6.2 build, backports will be needed ALSO on
> branch ovirt-3.6.2.
> 
> Will start implement the plan before lunch if noone objects.
> 
> Thanks
> 
> --
> Francesco Romani
> RedHat Engineering Virtualization R & D
> Phone: 8261328
> IRC: fromani
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
> 

-- 
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Vdsm sync 19/1

[Yaniv Bronheim]

Hi all,

(Participated: Piotr, Francesco, Adam, Nir, Edy and I)

We discussed about the following topics:

Python3  - terminating contextmanager is ready
https://gerrit.ovirt.org/51407  - this allows us to remove deathSignal
usages and safely kill processes on failures.
Francesco already covered one location (https://gerrit.ovirt.org/#/c/52349/)
this week I hope we'll *start* the work to cover the rest of the code as
follow:
vdsm/storage/mount.py
vdsm/storage/iscsiadm.py
vdsm/storage/imageSharing.py
vdsm/storage/hba.py
vdsm/storage/blockSD.py
vdsm/v2v.py
If any gaps or dependencies are raised I asked to state it in python3 work
sheet (
https://docs.google.com/spreadsheets/d/180F-C1jU54ajUn7TuR-NwrKRZY1IiZI1Z8U5HWbvEvM/edit#gid=0)
and we'll discuss it in next call.

next will be to remove all deathSignal usages - currently there are
redundant place where its being used that can be removed today:
lib/vdsm/qemuimg.py
vdsm/storage/curlImgWrap.py
vdsm/storage/storage_mailbox.py
vdsm/storage/misc.py
vdsm/API.py

Hopefully patches for that will be posted during the week.
Next step will be to use Popen where cpopen is not available (
https://gerrit.ovirt.org/48384) and we'll move forward with migrate more
tests to python3.

- Vdsm communicate - we did a little summary about what was explored and
what we want to have. It was only a discussion to see where we're heading.
 External Broker - In the past we checked Cupid (IMQP) and ActiveMQ (STOMP).
In cupid we found many bugs and gaps, we thought about using only the
client of it for point to point communication, but then found it too
complex. actionMQ is in java and found to be too slow and consume a lot of
memory so we thought about having only one instance in cluster, or maybe
run it in external host that doesn't run vdsm, or put it with the engine
host - for that we will need to change all "host lifecycle" that we have
today so we left it as well (piotr, fill me up if I missed something)
We have implementation for "mini borker" as part of vdsm which perform what
we need to run it as external process to vdsm and forward messages to
clients. there are alternatives as ZeroMQ that we can explore.
Bottom line - we want to approve the communicate inside the host, between
vdsm to other services such as supervdsm, mom and maybe later we'll split
the current implementation of vdsm to more services that will run in
parallel (such as vm monitoring, vdsm-storage and so on. For that we can
use dbus, multiprocessing(uds), or some kind of a broker.
This leaded us to talk about service separation which we want to design
soon.

- Vdsm contract - Piotr sent yaml schema plan in
https://gerrit.ovirt.org/#/c/52404 - please ack that you agree with the
concept. Piotr moves on with that and start to migrate all verbs to that
form. For next version we shell have both types of schema available, and
start to add new verbs and events structures in the new yaml format.

- Exceptions - Nir raises that we should define Virt specific exceptions -
Francesco can elaborate about the plans next week.

- Network updates - Edy checks how to improve network configuration time.
Currently vdsm modifies ifcfg files, which after changing them it takes
time for the update to catch.

Interesting call guys, I encourage more developers to participate, listen
and influence vdsm 4.0 directions.

See you next week.

-- 
*Yaniv Bronhaim.*
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Missing admin permissions.

[Alexander Wels]

On Tuesday, January 19, 2016 09:50:44 AM Fred Rolland wrote:
> I think this should help:
> https://www.mail-archive.com/devel%40ovirt.org/msg05152.html
> 

Strange that the admin@internal didn't get this by default, but after adding 
that following the mail in the archive, I can once again create VMs.

> On Mon, Jan 18, 2016 at 11:38 PM, Yaniv Kaul  wrote:
> > On Mon, Jan 18, 2016 at 11:00 PM, Alexander Wels  wrote:
> >> Hi,
> >> 
> >> Somewhere during master upgrades somehow my admin@internal did not get
> >> permissions to create VMs. Its is compiling about no permissions to
> >> assign a
> >> CPU profile. Its been a while since I tried creating a VM. Can any one
> >> point me
> >> to what is missing and how to fix it?
> > 
> > Perhaps it's https://bugzilla.redhat.com/show_bug.cgi?id=1293338 , and
> > the workaround is to re-run engine-setup, I believe.
> > Y.
> > 
> >> This is the error in the log:
> >> 2016-01-18 15:59:46,843 INFO  [org.ovirt.engine.core.bll.AddVmCommand]
> >> (default task-56) [a6fd12b] Lock Acquired to object 'EngineLock:
> >> {exclusiveLocks='[=]',
> >> sharedLocks='[----= >> ACTION_TYPE_FAILED_TEMPLATE_IS_USED_FOR_CREATE_VM$VmName >]'}'
> >> 2016-01-18 15:59:46,893 WARN  [org.ovirt.engine.core.bll.AddVmCommand]
> >> (default task-56) [] Validation of action 'AddVm' failed for user
> >> admin@internal. Reasons:
> >> 
> >> VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_NO_PERMISSION_TO_ASSIGN_CPU_PR
> >> OFILE, $cpuProfileId f9a05b39-9f57-4655-aab2-2846fe6519f6,$cpuProfileName
> >> DEV35 2016-01-18 15:59:46,894 INFO 
> >> [org.ovirt.engine.core.bll.AddVmCommand] (default task-56) [] Lock freed
> >> to object 'EngineLock:
> >> {exclusiveLocks='[=]',
> >> sharedLocks='[----= >> ACTION_TYPE_FAILED_TEMPLATE_IS_USED_FOR_CREATE_VM$VmName >]'}'
> >> 
> >> ___
> >> Devel mailing list
> >> Devel@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/devel
> > 
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [vdsm][virt] what's new in virt (20160119)

[Francesco Romani]

Hi all,

Here it is a new weekly summary about what's going on on virt's world (VDSM 
edition).
Since last week we made some good progress, thanks to all the reviewer and to 
all the maintainers
which helped; patches are receiving attention and are under active work, so 
this is a boring report :)

General direction:
* Francesco: is working on few bugfixes ended up in a few topic branches, 
currently addressing
  comments and backports.
* MartinPolednik: is working on his 'cpuarch/cpuinfo' topic. Since the last 
week most of cpuarch
  parts are merged, now focus is moving onc puinfo.
  - 
https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:cpuinfo
* Milan: is working on bugfixes as well
  - no specific topic
* Shahar: is working on extending v2v to support Xen
  - 
https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v2v-xen
* Vinzenz: completeded the epoll unregistrating issue, and more bugfixes for 
Guest Agent

Patch topics in need of attention
* Francesco: it seems the patches are receiving attention
  - recovery will receive some cleanup, but not really urgent

https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:bz1253043
* MartinPolednik: it seems the patches are receiving attention
* Milan: it seems the patches are receiving attention
* Shahar: it seems the patches are receiving attention
* Vinzenz: it seems the patches are receiving attention

Single patches in need of attention
* Francesco:
  - N/A
* MartinPolednik:
  - N/A
* Milan:
  - N/A
* Shahar:
  - N/A
* Vinzenz:
  - N/A
  
Tht's all for this week!

-- 
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] No more "vds group" in master code , instead please use "cluster"

[Eli Mesika]

Hi all 

Please note that there is still a problem on engine-setup I have already a 
fixing draft [1]
Meanwhile, until this is verified and merged please do before engine-setup from 
dbscripts/upgrade dir

psql -U engine -f 04_00_0210_add_vds_group_view.sql 

Thanks and sorry for that, this will be fixed ASAP and reported in this thread.

Eli

[1] https://gerrit.ovirt.org/#/c/52454/
- Original Message -
> From: "Idan Shaby" 
> To: "Eli Mesika" 
> Sent: Tuesday, January 19, 2016 10:10:17 AM
> Subject: Re: [ovirt-devel] No more "vds group" in master code , instead 
> please use "cluster"
> 
> Hi Eli,
> 
> I've fetched and rebased master, and got this error while running
> engine-setup:
> 
> [ INFO  ] Stage: Setup validation
> [WARNING] Cannot validate host name settings, reason: resolved host does
> not match any of the local addresses
> [ ERROR ] Failed to execute stage 'Setup validation': relation "vds_groups"
> does not exist LINE 2: SELECT compatibility_version FROM
> vds_groups...   ^
> [ INFO  ] Stage: Clean up
>   Log file is located at
> /home/ishaby/ovirt-engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20160119100829-tebscp.log
> [ INFO  ] Generating answer file
> '/home/ishaby/ovirt-engine/var/lib/ovirt-engine/setup/answers/20160119100830-setup.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Execution of setup failed
> 
> Any idea?
> 
> 
> Regards,
> Idan
> 
> On Sun, Jan 17, 2016 at 4:50 PM, Eli Mesika  wrote:
> 
> >
> >
> > - Original Message -
> > > From: "Eli Mesika" 
> > > To: "Jakub Niedermertl" 
> > > Cc: "devel" 
> > > Sent: Sunday, January 17, 2016 1:32:27 PM
> > > Subject: Re: [ovirt-devel] No more "vds group" in master code , instead
> > please use "cluster"
> > >
> > >
> > >
> > > - Original Message -
> > > > From: "Jakub Niedermertl" 
> > > > To: "Eli Mesika" 
> > > > Cc: "devel" 
> > > > Sent: Thursday, January 14, 2016 7:48:12 PM
> > > > Subject: Re: [ovirt-devel] No more "vds group" in master code ,
> >  instead
> > > > please use "cluster"
> > > >
> > > > Hi Eli,
> > > >
> > > > thank you, it helped. Now `engine-setup` works fine. However engine
> > itself
> > > > reports following in a few seconds after start:
> > > >
> > > > ERROR: relation "clusters_storage_domain" does not exist
> > > >
> > > > Relevant part of engine log: http://pastebin.test.redhat.com/340672
> > > > Tested on current master (commit 8561bb69560686d0) and clean db.
> > >
> > > You are right, sorry for that ...
> > > This patch fixes that issue
> > > https://gerrit.ovirt.org/#/c/51929
> >
> > Patch merged please re-base on master and try again
> >
> >
> > >
> > > >
> > > > - Original Message -
> > > > > From: "Eli Mesika" 
> > > > > To: "Jakub Niedermertl" 
> > > > > Cc: "devel" 
> > > > > Sent: Thursday, January 14, 2016 1:10:42 AM
> > > > > Subject: Re: [ovirt-devel] No more "vds group" in master code ,
> >  instead
> > > > > please use "cluster"
> > > > >
> > > > >
> > > > >
> > > > > - Original Message -
> > > > > > From: "Jakub Niedermertl" 
> > > > > > To: "Eli Mesika" 
> > > > > > Cc: "devel" 
> > > > > > Sent: Wednesday, January 13, 2016 9:18:57 PM
> > > > > > Subject: Re: [ovirt-devel] No more "vds group" in master code ,
> > instead
> > > > > > please use "cluster"
> > > > > >
> > > > > > Hi Eli,
> > > > > >
> > > > > > are db migration scripts supposed to handle this change? My
> > > > > > `engine-setup`
> > > > > > failed with following message in log:
> > > > >
> > > > > Hi Jakub
> > > > >
> > > > > Please re-base on latest master, there was an issue with that and it
> > was
> > > > > solved in https://gerrit.ovirt.org/#/c/51784/
> > > > >
> > > > >
> > > > > >
> > > > > > """
> > > > > > 2016-01-13 20:02:57 DEBUG
> > > > > > otopi.ovirt_**FILTERED**_setup.**FILTERED**_common.database
> > > > > > database.execute:172 Database: 'None', Statement: '
> > > > > > SELECT compatibility_version FROM cluster;;
> > > > > > ', args: {}
> > > > > > 2016-01-13 20:02:57 DEBUG
> > > > > > otopi.ovirt_**FILTERED**_setup.**FILTERED**_common.database
> > > > > > database.execute:177 Creating own connection
> > > > > > 2016-01-13 20:02:57 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
> > > > > >
> >  
> >