all the way to 4.1)?
> ## change in python class name??
> When I copied svdsm.logger.conf.rpmnew over svdsm.logger.conf, it could
> start up.
Seems like I already bumped in such issue awhile ago -
but now I see what's wrong - it happens after failing to read
/etc/vdsm/svdsm.logger.conf for some reason
then we have a bug in our fallback which tries to run
On Wed, Dec 28, 2016 at 3:43 PM, Nathanaël Blanchet
> On my 4.1 Second Beta test platform, I meet this issue on the three hosts
> : VDSM gaua3 command failed: 'exceptions.AttributeError'>:'NoneType'
> object has no attribute 'statistics'">
In oVirt-4.0 we introduced integration with metrics collectors, In  you
will find a guide for utilizing your environment to retrieve visualized
reports about hosts and vms statistics.
I encourage to try that out and send us requests for additional valuable
metrics that you think vdsm
This error means that the restAPI request to foreman returned an error.
Most of the time it is a communication issue.. but we can't know much from
Can you please share the production.log file from your foreman host?
Better to try to add the server as provider, get the
I'm testing ovirt-live which takes me more than 1 day
I followed the instructions in http://wiki.ovirt.org/OVirt_Live#VM to run in on
a local vm
the iso file I tried to took from latest build
(jenkins.ovirt.org/job/ovirt_live_create_iso/) and sent mail to infra maillist
that the link
we found this yum bug and still struggling with more issuing according to the
relation between those packages
if we drop vdsm-python-cpopen the requirement in vdsm takes python-cpopen
in python-cpopen we have the same code base and it provides all
- Original Message -
From: Nicholas Kesick cybertimber2...@hotmail.com
To: oVirt Mailing List firstname.lastname@example.org
Sent: Friday, November 22, 2013 6:55:23 PM
Subject: [Users] Trouble Upgrading (Fedora)
I am having trouble upgrading on Fedora 19 to 3.3.1.
checking the process, thanks for noticing
- Original Message -
From: Itamar Heim ih...@redhat.com
To: Sander Grendelman san...@grendelman.com, email@example.com, Yaniv
Cc: Federico Simoncelli fsimo...@redhat.com, Dan Kenigsberg
For the pep8 issue, as mentioned you should check pep8 --version and use 1.4.6.
If you use older version, just upgrade with python-pip
(yum install python-pip , and then `pip-install install pep8 --upgrade`)
Second, try to follow http://www.ovirt.org/Vdsm_Developers , it specifies
From: Alon Bar-Lev alo...@redhat.com
To: Thomas Suckow thomas.suc...@pnnl.gov, Yaniv Bronheim
ybron...@redhat.com, Yair Zaslavsky
Sent: Tuesday, August 27, 2013 8:55:06 AM
Subject: Re: [Users] Compliance problem with ovirt 3.3 on Fedora 19
From: Sven Knohsalla s.knohsa...@netbiscuits.com
To: Yaniv Bronheim ybron...@redhat.com
Sent: Thursday, May 9, 2013 9:30:09 AM
Subject: AW: [Users] oVirt 3.0 - known issue with live migration
the config on all servers were fine (with SSL).
check your conf files, if you use secure connection to host you should check
in /etc/conf/vdsm/vdsm.conf - check that ssl=True under [var]
in /etc/conf/libvirt/qemu.conf - check for spice_tls =1
Supervdsm allows vdsm to run root commands, like mount, dmidecode, lsblk, scan
folders that are unprivileged for vdsm user, and more. Due to this method we
avoid executing root commands using execv with sudo, that way we don't create
subprocess for each operation.
We have to
For your question, VDSM creates external processes for each storage operation
it performs. Using external process allows to make parallel operations without
being blocked on IO tasks, which can cause denial of service (like reading
files on unreachable mount).
To save kernel time that
...@gmail.com, Yaniv Bronheim
Cc: Joop jvdw...@xs4all.nl, firstname.lastname@example.org, vdsm-de...@fedorahosted.org
Sent: Friday, April 12, 2013 12:33:07 AM
Subject: Re: [Users] vdsm unresponsive with python exception
On Thu, Apr 11, 2013 at 03:51:07PM -0500, Tony Feldmann wrote
Do you run it after full installation or by standalone.sh ?
In order to by pass those errors in full installation do:
1. create a file /usr/share/ovirt-engine/conf/engine.conf.defaults
2. Add the following properties to the file:
ENGINE_USR=[the username which runs the engine]
I didn't notice the personal reply. Any news with the tests? did you try
running the tests locally?
- Forwarded Message -
From: Yaniv Bronheim ybron...@redhat.com
To: bigclouds bigclo...@163.com
Sent: Saturday, March 2, 2013 11:45:41 AM
Subject: Re: [Users] build vdsm
Its not easy :) I hope it would
Vdsm its a multiprocess program. It runs simultaneously tasks and monitors
them. You can use GDB to debug the main process and watch threads step (if you
want more information about that i can help)
Otherwise I prefer the oldschool print debuging.. it always works
Mail list logo