Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-02 Thread Yaniv Bronheim
Did it change the file permissions when you copied
svdsm.logger.conf.rpmnew?
can you reproduce it?

On Tue, Aug 1, 2017 at 3:06 PM Richard Chan <rich...@treeboxsolutions.com>
wrote:

> Hi,
>
> Could this be the cause of the access issue (old system upgraded from 3.4
> all the way to 4.1)?
> ## change in python class name??
>
>  [handler_logfile]
> -class=logUtils.UserGroupEnforcingHandler
> +class=vdsm.logUtils.UserGroupEnforcingHandler
>
> When I copied  svdsm.logger.conf.rpmnew over svdsm.logger.conf, it could
> start up.
>
> Thanks!
>
>
>
> On Tue, Aug 1, 2017 at 5:02 PM, Yaniv Bronheim <ybron...@redhat.com>
> wrote:
>
>> Hi,
>>
>> Seems like I already bumped in such issue awhile ago -
>> https://bugzilla.redhat.com/show_bug.cgi?id=1216880
>> 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
>> logging.basicConfig(filename='/dev/stdout', filemode='w+',
>> level=logging.DEBUG)
>>
>> and this fails while running as systemd daemon
>>
>> sorry about that. check why it can't load  /etc/vdsm/svdsm.logger.conf
>> and update us
>> after fixing the access issue check if you can run
>> logging.config.fileConfig("/etc/vdsm/svdsm.logger.conf" ,
>> disable_existing_loggers=False)
>> Then supervdsmd should start properly
>>
>> I'll reopen the bugzilla and fix the wrong fallback to syslog print
>>
>> Thanks!
>>
>>
>> On Sun, Jul 30, 2017 at 3:23 PM Richard Chan <
>> rich...@treeboxsolutions.com> wrote:
>>
>>> Hi Yaniv,
>>>
>>> On this one node, it happened from 3.6 -> 4.0. It persisted after
>>> 4.0->4.1.
>>> Current: vdsm-4.19.24-1.el7.centos.x86_64
>>>
>>>
>>> In systemd override I now have to have:
>>> StandardOutput=null
>>>
>>>
>>>
>>>
>>> Jul 29 01:19:21  systemd[1]: Starting Auxiliary vdsm service for
>>> running helper functions as root...
>>> Jul 29 01:19:21  python2[39124]: detected unhandled Python
>>> exception in '/usr/share/vdsm/supervdsmServer'
>>> Jul 29 01:19:21  daemonAdapter[39124]: Traceback (most recent
>>> call last):
>>> Jul 29 01:19:21  daemonAdapter[39124]: File
>>> "/usr/share/vdsm/supervdsmServer", line 45, in 
>>> Jul 29 01:19:21  daemonAdapter[39124]: level=logging.DEBUG)
>>> Jul 29 01:19:21  daemonAdapter[39124]: File
>>> "/usr/lib64/python2.7/logging/__init__.py", line 1529, in basicConfig
>>> Jul 29 01:19:21  daemonAdapter[39124]: hdlr =
>>> FileHandler(filename, mode)
>>> Jul 29 01:19:21  daemonAdapter[39124]: File
>>> "/usr/lib64/python2.7/logging/__init__.py", line 902, in __init__
>>> Jul 29 01:19:21  daemonAdapter[39124]:
>>> StreamHandler.__init__(self, self._open())
>>> Jul 29 01:19:21  daemonAdapter[39124]: File
>>> "/usr/lib64/python2.7/logging/__init__.py", line 925, in _open
>>> Jul 29 01:19:21  daemonAdapter[39124]: stream =
>>> open(self.baseFilename, self.mode)
>>> Jul 29 01:19:21  daemonAdapter[39124]: IOError: [Errno 6] No
>>> such device or address: '/dev/stdout'
>>> Jul 29 01:19:21  systemd[1]: supervdsmd.service: main process
>>> exited, code=exited, status=1/FAILURE
>>>
>>>
>>>
>>> On Sun, Jul 30, 2017 at 3:47 PM, Yaniv Kaul <yk...@redhat.com> wrote:
>>>
>>>>
>>>>
>>>> On Fri, Jul 28, 2017 at 8:37 PM, Richard Chan <
>>>> rich...@treeboxsolutions.com> wrote:
>>>>
>>>>> After an upgrade to 4.0 I have a single host that cannot start
>>>>> supervdsmd because of IOError on /dev/stdout. All other hosts upgraded
>>>>> correctly.
>>>>>
>>>>
>>>> Upgrade from which version? 3.6? Did you stay on 4.0 or continued to
>>>> 4.1?
>>>>
>>>>
>>>>>
>>>>> In the systemd unit I have to hack StandardOutput=null.
>>>>>
>>>>> Any thing I have overlooked? The hosts are all identical and it is
>>>>> just this one
>>>>> that has this weird behaviour.
>>>>>
>>>>
>>>> Any logs that you can share?
>>>>  Y.
>>>>
>>>>
>>>>>
>>>>> --
>>>>> Richard Chan
>>>>>
>>>>>
>>>>> ___
>>>>> Users mailing list
>>>>> Users@ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Richard Chan
>>> Chief Architect
>>>
>>> TreeBox Solutions Pte Ltd
>>> 1 Commonwealth Lane #03-01
>>> Singapore 149544
>>> Tel: 6570 3725
>>> http://www.treeboxsolutions.com
>>>
>>> Co.Reg.No. 201100585R
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>> --
>> Yaniv Bronhaim.
>>
>
>
>
> --
> Richard Chan
> Chief Architect
>
> TreeBox Solutions Pte Ltd
> 1 Commonwealth Lane #03-01
> Singapore 149544
> Tel: 6570 3725
> http://www.treeboxsolutions.com
>
> Co.Reg.No. 201100585R
>
-- 
Yaniv Bronhaim.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-01 Thread Yaniv Bronheim
Hi,

Seems like I already bumped in such issue awhile ago -
https://bugzilla.redhat.com/show_bug.cgi?id=1216880
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
logging.basicConfig(filename='/dev/stdout', filemode='w+',
level=logging.DEBUG)

and this fails while running as systemd daemon

sorry about that. check why it can't load  /etc/vdsm/svdsm.logger.conf and
update us
after fixing the access issue check if you can run
logging.config.fileConfig("/etc/vdsm/svdsm.logger.conf" ,
disable_existing_loggers=False)
Then supervdsmd should start properly

I'll reopen the bugzilla and fix the wrong fallback to syslog print

Thanks!


On Sun, Jul 30, 2017 at 3:23 PM Richard Chan 
wrote:

> Hi Yaniv,
>
> On this one node, it happened from 3.6 -> 4.0. It persisted after 4.0->4.1.
> Current: vdsm-4.19.24-1.el7.centos.x86_64
>
>
> In systemd override I now have to have:
> StandardOutput=null
>
>
>
>
> Jul 29 01:19:21  systemd[1]: Starting Auxiliary vdsm service for
> running helper functions as root...
> Jul 29 01:19:21  python2[39124]: detected unhandled Python
> exception in '/usr/share/vdsm/supervdsmServer'
> Jul 29 01:19:21  daemonAdapter[39124]: Traceback (most recent call
> last):
> Jul 29 01:19:21  daemonAdapter[39124]: File
> "/usr/share/vdsm/supervdsmServer", line 45, in 
> Jul 29 01:19:21  daemonAdapter[39124]: level=logging.DEBUG)
> Jul 29 01:19:21  daemonAdapter[39124]: File
> "/usr/lib64/python2.7/logging/__init__.py", line 1529, in basicConfig
> Jul 29 01:19:21  daemonAdapter[39124]: hdlr =
> FileHandler(filename, mode)
> Jul 29 01:19:21  daemonAdapter[39124]: File
> "/usr/lib64/python2.7/logging/__init__.py", line 902, in __init__
> Jul 29 01:19:21  daemonAdapter[39124]:
> StreamHandler.__init__(self, self._open())
> Jul 29 01:19:21  daemonAdapter[39124]: File
> "/usr/lib64/python2.7/logging/__init__.py", line 925, in _open
> Jul 29 01:19:21  daemonAdapter[39124]: stream =
> open(self.baseFilename, self.mode)
> Jul 29 01:19:21  daemonAdapter[39124]: IOError: [Errno 6] No such
> device or address: '/dev/stdout'
> Jul 29 01:19:21  systemd[1]: supervdsmd.service: main process
> exited, code=exited, status=1/FAILURE
>
>
>
> On Sun, Jul 30, 2017 at 3:47 PM, Yaniv Kaul  wrote:
>
>>
>>
>> On Fri, Jul 28, 2017 at 8:37 PM, Richard Chan <
>> rich...@treeboxsolutions.com> wrote:
>>
>>> After an upgrade to 4.0 I have a single host that cannot start
>>> supervdsmd because of IOError on /dev/stdout. All other hosts upgraded
>>> correctly.
>>>
>>
>> Upgrade from which version? 3.6? Did you stay on 4.0 or continued to 4.1?
>>
>>
>>>
>>> In the systemd unit I have to hack StandardOutput=null.
>>>
>>> Any thing I have overlooked? The hosts are all identical and it is just
>>> this one
>>> that has this weird behaviour.
>>>
>>
>> Any logs that you can share?
>>  Y.
>>
>>
>>>
>>> --
>>> Richard Chan
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
>
> --
> Richard Chan
> Chief Architect
>
> TreeBox Solutions Pte Ltd
> 1 Commonwealth Lane #03-01
> Singapore 149544
> Tel: 6570 3725
> http://www.treeboxsolutions.com
>
> Co.Reg.No. 201100585R
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
-- 
Yaniv Bronhaim.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] [ANN] oVirt 4.1.0 Second Beta Release is now available for testing

2016-12-28 Thread Yaniv Bronheim
On Wed, Dec 28, 2016 at 3:43 PM, Nathanaël Blanchet 
wrote:

> Hello,
>
> 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'">
>

Hi Nathanael, Thank you for the report

please send also the following logs for deeper investigation
/var/log/vdsm.log
/var/log/supervdsm.log
/var/log/messages or joursnalctl -xn output

Also, please specify a bit the platform you are running on and when this
issue occurs

Greetings,
Yaniv Bronhaim.



>
> Le 21/12/2016 à 16:12, Sandro Bonazzola a écrit :
>
> The oVirt Project is pleased to announce the availability of the Second
> Beta Release of oVirt 4.1.0 for testing, as of December 21st, 2016
>
> This is pre-release software. Please take a look at our community page[1]
> to know how to ask questions and interact with developers and users.
> All issues or bugs should be reported via oVirt Bugzilla[2].
> This pre-release should not to be used in production.
>
> This release is available now for:
> * Fedora 24 (tech preview)
> * Red Hat Enterprise Linux 7.3 or later
> * CentOS Linux (or similar) 7.3 or later
>
> This release supports Hypervisor Hosts running:
> * Red Hat Enterprise Linux 7.3 or later
> * CentOS Linux (or similar) 7.3 or later
> * Fedora 24 (tech preview)
>
> See the release notes draft [3] for installation / upgrade instructions and
> a list of new features and bugs fixed.
>
> Notes:
> - oVirt Live iso is already available
> - oVirt Node NG iso will be available soon
> - Hosted Engine appliance will be available soon
> - above delay is due to jenkins issues building node and appliance, should
> be fixed by tomorrow.
>
> An initial release management page including planned schedule is also
> available[4]
>
>
> Additional Resources:
> * Read more about the oVirt 4.1.0 beta release highlights:
> http://www.ovirt.org/release/4.1.0/
> * Get more oVirt Project updates on Twitter: 
> https://twitter.com/ovirt
> * Check out the latest project news on the oVirt blog:
> http://www.ovirt.org/blog/
>
> [1] https://www.ovirt.org/community/
> [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
> [3] http://www.ovirt.org/release/4.1.0/
> [4] http://www.ovirt.org/develop/release-management/releases/4.
> 1/release-management/
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


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


[ovirt-users] oVirt metrics

2016-07-13 Thread Yaniv Bronheim
Hi,

In oVirt-4.0 we introduced integration with metrics collectors, In [1] 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 should publish.
This area is still work in progress and we plan to support more
technologies and different architectures for metrics collections as
describes in the post. This will follow by additional links in the post
([1]) that describe how to do so.. stay tuned.

[1] https://bronhaim.wordpress.com/2016/06/26/ovirt-metrics

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


Re: [ovirt-users] Foreman: Add external provider (Failed with error PROVIDER_FAILURE and code 5050)

2015-09-25 Thread Yaniv Bronheim
Hi Nathanael,

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
this report.
Can you please share the production.log file from your foreman host?
Better to try to add the server as provider, get the error and then check
the production.log file - it will show us if engine request got to foreman
server, the internal fields and why foreman returned 5050.

Greeting,
Yaniv Bronhaim.

On Wed, Sep 23, 2015 at 5:31 PM, Nathanaël Blanchet 
wrote:

> Hello,
>
> I have a working foreman 1.9.1 installed with katello 2.3.
> ruby193-rubygem-ovirt_provision_plugin-1.0.1-1.el7 is also installed on
> the same host.
> But the issue is the same as below when testing  in "add external
> provider" from ovirt 3.5.4.
> What can I do now?
>
> Le 06/11/2014 12:31, Oved Ourfali a écrit :
>
>>
>> - Original Message -
>>
>>> From: "Daniel Helgenberger" 
>>> To: "Oved Ourfali" 
>>> Cc: users@ovirt.org
>>> Sent: Thursday, November 6, 2014 1:29:38 PM
>>> Subject: Re: [ovirt-users] Foreman: Add external provider (Failed with
>>> error PROVIDER_FAILURE and code 5050)
>>>
>>>
>>>
>>> On 06.11.2014 05:47, Oved Ourfali wrote:
>>>
 These steps are also in the feature page

>>> Thanks Oved for pointing to the doc; my bad. I was using the foreman
>>> integration document [1]. Maybe the pages should be merged?
>>>
>>> Yaniv - you planned to merge them, right? That would be a good time...
>>
>>
>> , but it would be nice if you review them to see nothing is missing.

 http://www.ovirt.org/Features/AdvancedForemanIntegration

>>> With foreman 1.6 (at least) there is no need to enable the nightly
>>> builds any more as rb-ovirt is resolved by yum.
>>>
>>> Lastly, I think you need to enable foreman_discovery with the foreman
>>> installer to work and download images:
>>>
>>> # foreman-installer --enable-foreman-plugin-discovery
>>> --foreman-plugin-discovery-install-images=true
>>>
>>> You have that already listed in the testing env setup; but this needs to
>>> be put in context with installing foreman-ovirt on the foreman host.
>>>
>> Yaniv - please add a note there too.
>>
>> Daniel - thanks for the review and the comments!
>>
>> Regards,
>> Oved
>>
>> Thanks
 Oved

 [1] http://www.ovirt.org/Features/ForemanIntegration
>>>
>>> On Nov 6, 2014 12:40 AM, Daniel Helgenberger <
 daniel.helgenber...@m-box.de>
 wrote:

> Answering my own question; and maybe a very obvious cause for the
> failing provider: the missiAnswering my own question; and maybe a very
> obvious cause for the
>
 failing provider: the missing provider plugin in forman!
 So one needs to do:

 yum install ruby193-rubygem-ovirt_provision_plugin

 on the foreman host.

 After that, the connection test in the engine comes up positive. Sadly,
 this is not documented anywhere; only on the GitHub repo readme [1].
 This is also a little bit outdated, as the rbovirt dependency is
 resolved now automatically.

 Also, but I am not sure, the porvider lugin needs the foreman_discovery
 plugin to work:

 yum install ruby193-rubygem-foreman_discovery

 [1]

 https://github.com/theforeman/ovirt_provision_plugin/blob/master/README.md

 On 29.10.2014 00:36, Daniel Helgenberger wrote:

> Hello,
>
> did anyone actually get this working in oVirt 3.5 / EL6 - Engine? I am
> trying this for two days now.
>
> Setup:
> Engine; EL6.5
> Foreman; EL6.5
>
> Foreman seems to do it's as I can use it to deploy hosts and also smart
> proxies are running fine.
>
> I have opened a BZ [1]; because this really can not work out of the box
> with EL6 plain vanilla packages. I wonder if this was ever tested... ?
> Java 7 used i n EL6 [4] does only support DH keys up to 1024byte. This
> is known issue in Foreman [2] as longer DH keys are now used by default
> in Foreman / PuppetCA.
> A dirty fix confirmed working is adding default DH parameters to the
> foreman cert; effectively disabling it [3].
>
> So I got SSL working and I get beyond the authentication (entering
> wrong
> data gets me auth errors)- however, I am still not able to add the
> external provider. Pressing 'test' results in
> (Failed with error PROVIDER_FAILURE and code 5050)
>
> Sample engine.log
> 2014-10-28 23:49:40,860 ERROR
> [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand]
> (ajp--127.0.0.1-8702-1) [6a3da4e7] Command
> org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand
> throw
> Vdc Bll exception. With error message VdcBLLException: PROVIDER_FAILURE
> (Failed with error PROVIDER_FAILURE and code 5050)
>
> I can't find any more hints in oVirt; access logs in 

[Users] oVirt 3.4.0 beta 2/Test Day

2014-02-13 Thread Yaniv Bronheim
Hey all,
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 somehow fails to be d/led.

currently opened 2 bugs   
https://bugzilla.redhat.com/show_bug.cgi?id=1063680
https://bugzilla.redhat.com/show_bug.cgi?id=1063829

and still playing with the ovirt-engine installation that doesn't work smoothly 
(at least from my prospective and tries)

Regards,
Yaniv Bronhaim.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] ovirt-3.3.3 release postponed due to blockers

2014-01-30 Thread Yaniv Bronheim
Hey, 

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 
instead.
in python-cpopen we have the same code base and it provides all 
vdsm-ptyhon-cpopen provides, so shouldn't be any issues with dropping it from 
the repository

is it possible to ship 3.3.3 release that way ? we don't need to change the 
requirement in the code, if python-cpopen 1.3-1 is part of the release, it will 
be taken by vdsm spec (tried with vdsm 4.13.3-2 with the available cpopen 1.3-1)

Sven, for your question, install python-cpopen 1.3-1 for both 3.3 and 3.4 
releases that you use, and the upgrade\downgrade should not raise any 
dependencies issues afaic

Yaniv Bronhaim.



- Original Message -
 From: Dan Kenigsberg dan...@redhat.com
 To: Sandro Bonazzola sbona...@redhat.com, ybron...@redhat.com
 Cc: Sven Kieske s.kie...@mittwald.de, Trey Dockendorf 
 treyd...@gmail.com, users users@ovirt.org, VDSM
 Project Development vdsm-de...@lists.fedorahosted.org
 Sent: Thursday, January 30, 2014 4:02:13 PM
 Subject: Re: [Users] ovirt-3.3.3 release postponed due to blockers
 
 On Thu, Jan 30, 2014 at 10:27:34AM +0100, Sandro Bonazzola wrote:
  Il 30/01/2014 10:20, Dan Kenigsberg ha scritto:
   On Thu, Jan 30, 2014 at 08:52:36AM +, Sven Kieske wrote:
   Hi,
  
   any news regarding my questions?
  
   Am 29.01.2014 09:23, schrieb Sandro Bonazzola:
   Il 29/01/2014 09:21, Sven Kieske ha scritto:
   Hi,
  
   I wanted to try it the other way around, installing vdsm-python-cpopen
   and check if it runs without python-cpopen .
  
   But that leads me to a question:
  
   Is there any difference between these packages beside their different
   name?
  
   If yes, what is the difference and which package should be installed?
   I no, why is there a packet vdsm-python-cpopen ?
  
   CCing VDSM
   
   python-cpopen includes some improvements and bug fixes, that are going
   to be needed in ovirt-3.4. vdsm-python-cpopen is shipped by ovirt-3.3.
   
   python-cpopen wast intended to deprecate and replace vdsm-python-cpopen,
   but we have had way too many issues trying to do that properly in
   rpm/yum. Most of the bugs are ours, at least one is yum's.
   
   At the moment, the existence of python-cpopen in Fedora confuses `yum
   install vdsm`.
   
   To avoid this unfortunate delay, we can either include python-cpopen in
   ovirt-stable or exclude vdsm-python-cpopen from there. Both options are
   unfavorable, but so is continuing to wait.
  
  If it's enough just to add python-cpopen to ovirt-stable, I'm fine with
  that.
  I just need the link to the build to be included there.
 
 Yaniv, have you tried if shipping python-cpopen hides this issue?
 
 http://kojipkgs.fedoraproject.org//packages/python-cpopen/1.3/1.fc20/x86_64/python-cpopen-1.3-1.fc20.x86_64.rpm
 http://kojipkgs.fedoraproject.org//packages/python-cpopen/1.3/1.fc19/x86_64/python-cpopen-1.3-1.fc19.x86_64.rpm
 http://kojipkgs.fedoraproject.org//packages/python-cpopen/1.3/1.el6/ppc64/python-cpopen-1.3-1.el6.ppc64.rpm
 
 Dropping vdsm-python-cpopen from a stable version seems impolite, but
 should work, too.
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Trouble Upgrading (Fedora)

2013-11-24 Thread Yaniv Bronheim
Hey,

- Original Message -
 From: Nicholas Kesick cybertimber2...@hotmail.com
 To: oVirt Mailing List users@ovirt.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.
 
 Two observations:
 1) I can't find ovirt-engine-3.3.1, even after a yum clear all; yum update.
 
 
 2) There is a dependency update circle involving
 python-cpopen-1.2.3-4.fc19.x86_64 and dsm-python-cpopen.x86_64
 0:4.13.0-11.fc19

This issue is fine. Not so smoothly but we had to do that. 
cpopen package is published as part of vdsm code in ovirt-3.3 and before,
On master branch we require python-cpopen formal package that is shipped with 
fedora\rhel currently .

Each time you'll switch between newer version of current master (3.4) to 
ovirt-3.3 or older you will notice this report

 
 Searching for ovirt-engine (after yum clear all)
 yum list ovirt-engine
 Loaded plugins: langpacks, refresh-packagekit, versionlock
 Installed Packages
 ovirt-engine.noarch 3.3.0-4.fc19 @ovirt-stable
 
 Next a the yum update
 sudo yum history info 8
 Loaded plugins: langpacks, refresh-packagekit, versionlock
 Transaction ID : 8
 Begin time : Thu Nov 21 18:28:24 2013
 Begin rpmdb : 1184:c12933940909ba00699a2269f2a08082654d7bdc
 End time : 18:30:41 2013 (137 seconds)
 End rpmdb : 1186:39b969c3d77367584456e993c37378e6e578a638
 User : root root
 Return-Code : Success
 Command Line : update
 Transaction performed with:
 Installed rpm-4.11.1-3.fc19.x86_64 @updates
 Installed yum-3.4.3-111.fc19.noarch @updates
 Installed yum-plugin-versionlock-1.1.31-18.fc19.noarch @updates
 Packages Altered:
 Updated acl-2.2.51-9.fc19.x86_64 @fedora
 Update 2.2.51-10.fc19.x86_64 @updates
 Updated dbus-1:1.6.12-1.fc19.x86_64 @updates
 Update 1:1.6.12-2.fc19.x86_64 @updates
 Updated dbus-libs-1:1.6.12-1.fc19.x86_64 @updates
 Update 1:1.6.12-2.fc19.x86_64 @updates
 Updated gnutls-3.1.15-1.fc19.x86_64 @updates
 Update 3.1.16-1.fc19.x86_64 @updates
 Updated gnutls-dane-3.1.15-1.fc19.x86_64 @updates
 Update 3.1.16-1.fc19.x86_64 @updates
 Updated gnutls-utils-3.1.15-1.fc19.x86_64 @updates
 Update 3.1.16-1.fc19.x86_64 @updates
 Updated gtk2-2.24.22-1.fc19.x86_64 @updates
 Update 2.24.22-2.fc19.x86_64 @updates
 Updated iw-3.8-2.fc19.x86_64 @fedora
 Update 3.11-1.fc19.x86_64 @updates
 Install kernel-3.11.8-200.fc19.x86_64 @updates
 Install kernel-modules-extra-3.11.8-200.fc19.x86_64 @updates
 Updated libacl-2.2.51-9.fc19.x86_64 @fedora
 Update 2.2.51-10.fc19.x86_64 @updates
 Updated libvirt-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-client-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-config-network-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-config-nwfilter-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-interface-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-libxl-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-lxc-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-network-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-nodedev-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-nwfilter-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-qemu-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-secret-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-storage-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-uml-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-driver-xen-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-kvm-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-daemon-qemu-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-lock-sanlock-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libvirt-python-1.0.5.6-3.fc19.x86_64 @updates
 Update 1.0.5.7-2.fc19.x86_64 @updates
 Updated libwbclient-2:4.0.9-3.fc19.x86_64 @updates
 Update 2:4.0.11-1.fc19.x86_64 @updates
 Updated mesa-libEGL-9.2-1.20130919.fc19.x86_64 @updates
 Update 9.2.3-1.20131114.fc19.x86_64 @updates
 Updated mesa-libGL-9.2-1.20130919.fc19.x86_64 @updates
 Update 9.2.3-1.20131114.fc19.x86_64 @updates
 Updated mesa-libgbm-9.2-1.20130919.fc19.x86_64 @updates
 Update 9.2.3-1.20131114.fc19.x86_64 

Re: [Users] Snapshot delele/merge broken. Was: Live storage migration snapshot removal (fails)

2013-11-14 Thread Yaniv Bronheim
checking the process, thanks for noticing 

Yaniv Bronhaim.

- Original Message -
 From: Itamar Heim ih...@redhat.com
 To: Sander Grendelman san...@grendelman.com, users@ovirt.org, Yaniv 
 Bronheim ybron...@redhat.com
 Cc: Federico Simoncelli fsimo...@redhat.com, Dan Kenigsberg 
 dan...@redhat.com
 Sent: Thursday, November 14, 2013 12:24:29 PM
 Subject: Re: [Users] Snapshot delele/merge broken. Was: Live storage 
 migration snapshot removal (fails)
 
 On 11/13/2013 07:52 AM, Sander Grendelman wrote:
  Snapshot deletion on preallocated FC domain disks is broken in
  ovirt-stable/3.3
 
  Both online and offline snapshot deletion leads to an error and the
  snapshot state is changed to BROKEN.
 
  When I apply the patch at http://gerrit.ovirt.org/#/c/19983/ from
  https://bugzilla.redhat.com/show_bug.cgi?id=1015071 snapshot deletion
  works again.
 
  Can/will this patch be backported to ovirt-stable?
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 
 yaniv - can you (or someone else maintaing stable 3.3) update 3.3.1
 release notes with the vdsm bugs fixed in it (not sure if the one above
 is or isn't)
 http://www.ovirt.org/OVirt_3.3.1_release_notes
 
 Thanks,
 Itamar
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] [vdsm] Low quality of el6 vdsm rpms

2013-11-12 Thread Yaniv Bronheim
Hey Patrick,

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 the 
repositories you need to set (which should solve and selinux-policy package you 
miss) and should be the same for ovirt-3.3.
About the hostname issue, can you detail more about the issue .. I'm not 
familiar with such error 

There are some differences between ovirt-3.3 branch and master in the 
requirements scope, each with specific reason.
you should checkout ovirt-3.3 branch and not ovirt-3.3.0 for those tests

We are working on the quality and constantly trying to increase and improve the 
software.
About the builds process you can talk with eedri for more details 

Regards,
Yaniv Bronhaim.
 

- Original Message -
 From: Sandro Bonazzola sbona...@redhat.com
 To: patrick hurrelmann patrick.hurrelm...@lobster.de, oVirt Mailing 
 List users@ovirt.org, vdsm-devel
 vdsm-de...@fedorahosted.org
 Sent: Tuesday, November 12, 2013 12:31:04 PM
 Subject: Re: [vdsm] [Users] Low quality of el6 vdsm rpms
 
 Il 12/11/2013 10:34, Patrick Hurrelmann ha scritto:
  Hi all,
  
  sorry for this rant, but...
  
  I now tried several times to test the beta 3.3.1 rpms, but they can't
  even be installed in the most times.
 
 I'm glad to read you're testing 3.3.1. May I ask you to add yourself to
 http://www.ovirt.org/Testing/Ovirt_3.3.1_testing ?
 
  One time it required a future
  selinux-policy, although the needed selinux fix was delivered in a much
  lower version. Now the rpms have broken requirements. It requires
  hostname instead of /bin/hostname. This broken requirement is not
  included in the vdsm 3.3 branch, so I wonder where it comes from?
  Anyway. So I proceeded and tried to build vdsm myself once again.
  Currently the build fails with (but worked fine some days ago):
  
  /usr/bin/pep8 --exclude=config.py,constants.py --filename '*.py,*.py.in'
  \
  client lib/cpopen/*.py lib/vdsm/*.py lib/vdsm/*.py.in tests
  vds_bootstrap vdsm-tool vdsm/*.py vdsm/*.py.in vdsm/netconf
  vdsm/sos/vdsm.py.in vdsm/storage vdsm/vdsm vdsm_api vdsm_hooks vdsm_reg
  vdsm/storage/imageRepository/formatConverter.py:280:29: E128
  continuation line under-indented for visual indent
  
  
  - How can the quality of the vdsm builds be increased? It is frustrating
  to spend time on testing and then the hosts cannot even be installed to
  broken vdsm rpms.
  - How are the builds prepared? Is there a Jenkins job that prepares
  stable rpms in addition to the nightly job? Or is this totally
  handcrafted?
  - How can it be that the rpm spec differs between the 3.3 branch and
  released rpms? What is the source/branch for el6 vdsm rpms? Maybe I'm
  just tracking on the wrong source tree...
 
 Since this is VDSM related, adding vdsm-devel list to the discussion.
 
 
  
  Thx and Regards
  Patrick
  
  
 
 
 --
 Sandro Bonazzola
 Better technology. Faster innovation. Powered by community collaboration.
 See how it works at redhat.com
 ___
 vdsm-devel mailing list
 vdsm-de...@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Compliance problem with ovirt 3.3 on Fedora 19

2013-08-27 Thread Yaniv Bronheim
The Hosts emulated machines are UNKNOWN, is probably an error during parsing 
emulatedMachines that returned from vdsm.
doesn't have anything with network IIUC..
so its probably new bug in parsing the list. please run vdsClient -s 0 
getVdsCaps | grep emulatedMachines on host and send it here.

For the second service issue, its quite obvious - ksmtuned couldn't start with 
systemd nor initctl, 
try to start it manually, maybe you just missing 'qemu-kvm' package somehow.

Let me know the outputs and I'll try to figure it more deeply.

Thanks,

Yaniv Bronhaim.

- Original Message -
 From: Alon Bar-Lev alo...@redhat.com
 To: Thomas Suckow thomas.suc...@pnnl.gov, Yaniv Bronheim 
 ybron...@redhat.com, Yair Zaslavsky
 yzasl...@redhat.com
 Cc: users@ovirt.org
 Sent: Tuesday, August 27, 2013 8:55:06 AM
 Subject: Re: [Users] Compliance problem with ovirt 3.3 on Fedora 19
 
 
 
 - Original Message -
  From: Thomas Suckow thomas.suc...@pnnl.gov
  To: users@ovirt.org
  Sent: Tuesday, August 27, 2013 1:48:33 AM
  Subject: Re: [Users] Compliance problem with ovirt 3.3 on Fedora 19
  
  Snippets of what seems possibly relevant:
  https://gist.github.com/thomassuckow/995f422cd5c46c6de98c
  
  messages seems mostly happy with the exception of a crash in
  /usr/bin/vdsm-tool related to ksmtuned, not sure if relevant
  
  The engine.log shows the error I mentioned before:
  
  ... Message: Host myhost does not comply with the cluster Default emulated
  machines. The Hosts emulated machines are UNKNOWN and the cluster is
  [rhel6.4.0, pc-1.0]}
  ...
  ... Message: State was set to NonOperational for host myhost
  
 
 For the service issue, I am adding Yaniv.
 The Hosts emulated machines are UNKNOWN, I am adding Yair.
 
 As far as I can see the host-deploy is finished OK, just to confirm can you
 send output of:
 # ip link
 # ip addr
 
 Thanks!
 Alon
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt 3.0 - known issue with live migration

2013-05-11 Thread Yaniv Bronheim
Hey,

Restarting libvirt service won't crash your VMs.. Might be that during the 
migration libvirt got crashed, did you try to restart only vdsm?
Can you attach your vdsm.log? Maybe I'll be able to point this issue to a 
specific bug and find the reason for this failure..

Thanks

- Original Message -
 From: Sven Knohsalla s.knohsa...@netbiscuits.com
 To: Yaniv Bronheim ybron...@redhat.com
 Cc: users@ovirt.org
 Sent: Thursday, May 9, 2013 9:30:09 AM
 Subject: AW: [Users] oVirt 3.0 - known issue with live migration
 
 Hi Yaniv,
 
 the config on all servers were fine (with SSL).
 
 I had to reboot the old hypervisors to make migration from new hypervisor
 possible (restart of libvirt would crash my VMs ;) ),
 was a bit hard as I hadn't any other VM slots were I could migrate to..
 
 Just have this behavior with oVirt 3.0 environment, oVirt3.2 with minimal F18
 nodes works fine here.. strange.
 
 Want to give you feedback here as you answered very quickly.
 Thanks again!
 
 Cheers,
 Sven.
 
 -Ursprüngliche Nachricht-
 Von: Yaniv Bronheim [mailto:ybron...@redhat.com]
 Gesendet: Donnerstag, 2. Mai 2013 10:26
 An: Sven Knohsalla
 Cc: users@ovirt.org
 Betreff: Re: [Users] oVirt 3.0 - known issue with live migration
 
 Hi,
 check your conf files, if you use secure connection to host you should check
 the parameters:
 
 in /etc/conf/vdsm/vdsm.conf - check that ssl=True under [var]
 in /etc/conf/libvirt/qemu.conf - check for spice_tls =1
 and in /etc/conf/libvirt/libvirtd.conf - auth_tcp and listen_tcp are not
 declared (under a comment).
 
 to verify, restart vdsm service and run - vdsClient -s 0 getVdsCaps  [-s for
 secure]. if it returns, the configurations are good.
 
 for unsecure connection:
 in libvirtd.conf you should have auth_tcp=none listen_tcp=1 in
 /etc/conf/vdsm/vdsm.conf - check that ssl=False in
 /etc/conf/libvirt/qemu.conf - check for spice_tls=0
 
 and again, to verify - vdsClient 0 getVdsCaps , if returns we're fine.
 
 Please attach the results.
 If it's not the issue, please attach your vdsm.log to check it more
 specifically.
 
 Regards,
 Yaniv Bronhaim.
 
 
 
 - Original Message -
  From: Sven Knohsalla s.knohsa...@netbiscuits.com
  To: users@ovirt.org
  Sent: Wednesday, May 1, 2013 5:02:07 PM
  Subject: [Users] oVirt 3.0 - known issue with live migration
  
  
  
  Hi there,
  
  
  
  
  
  adding a new node to an oVirt 3.0 cluster worked, but migration doesn’t..
  (same hardware, some node version 2.3.0)
  
  “Migration failed due to Error: Could not connect to peer host”
  (WebGui)
  
  
  
  Thread-2474::ERROR::2013-05-01
  13:58:08,007::SecureXMLRPCServer::73::root::(handle_error) client
  ('172.16.101.102', 60836) (vdsm log on target host)
  
  
  
  I remember there was a bug in this scenario where I had to uncomment
  the line in /etc/libvirt/libvirtd.conf:
  listen_tls = 0 -- #listen_tls = 0
  
  Rebooted the new HV in maintenance mode, the config setup persisted,
  
  but the problem also persists…
  
  
  
  Unfortunately I had the same issue in the past, but I just documented
  the setting in/etc/libvirt/libvirtd.conf
  
  as workaround, so it seems something is still missing…?
  
  
  
  DNS  FQDN are setup properly…
  
  
  
  Does anybody reminds of this bug and may help me out?
  
  (didn’t find this issue in the mail archive)
  
  
  Thanks in advance!
  
  
  
  Best,
  
  Sven.
  
  
  
  Sven Knohsalla | System Administration
  
  
  
  Office +49 631 68036 433 | Fax +49 631 68036 111 |E-Mail
  s.knohsa...@netbiscuits.com | Skype: netbiscuits.admin
  
  Netbiscuits GmbH | Europaallee 10 | 67657 | GERMANY
  
  
  
  
  
  
  
  
  
  
  
  Register Court: Local Court Kaiserslautern | Commercial Register ID:
  HR B
  3604
  Management Board : Guido Moggert, Michael Neidhöfer, Christian Reitz,
  Martin Süß
  
  
  
  This message and any files transmitted with it are confidential and
  intended solely for the use of the individual or entity to whom they are
  addressed.
  It may also be privileged or otherwise protected by work product
  immunity or other legal rules. Please notify the sender immediately by
  e-mail if you have received this e-mail by mistake and delete this
  e-mail from your system. If you are not the intended recipient you are
  notified that disclosing, copying, distributing or taking any action
  in reliance on the contents of this information is strictly prohibited.
  
  Warning: Although Netbiscuits has taken reasonable precautions to
  ensure no viruses are present in this email, the company cannot accept
  responsibility for any loss or damage arising from the use of this email or
  attachments.
  
  
  
  Please consider the environment before printing
  
  
  
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 
___
Users mailing list

Re: [Users] oVirt 3.0 - known issue with live migration

2013-05-02 Thread Yaniv Bronheim
Hi,
check your conf files, if you use secure connection to host you should check 
the parameters:

in /etc/conf/vdsm/vdsm.conf - check that ssl=True under [var]
in /etc/conf/libvirt/qemu.conf - check for spice_tls =1 
   
and in /etc/conf/libvirt/libvirtd.conf - auth_tcp and listen_tcp are not 
declared (under a comment).

to verify, restart vdsm service and run - vdsClient -s 0 getVdsCaps  [-s for 
secure]. if it returns, the configurations are good.

for unsecure connection:
in libvirtd.conf you should have auth_tcp=none listen_tcp=1
in /etc/conf/vdsm/vdsm.conf - check that ssl=False
in /etc/conf/libvirt/qemu.conf - check for spice_tls=0

and again, to verify - vdsClient 0 getVdsCaps , if returns we're fine.

Please attach the results.
If it's not the issue, please attach your vdsm.log to check it more 
specifically.

Regards,
Yaniv Bronhaim.



- Original Message -
 From: Sven Knohsalla s.knohsa...@netbiscuits.com
 To: users@ovirt.org
 Sent: Wednesday, May 1, 2013 5:02:07 PM
 Subject: [Users] oVirt 3.0 - known issue with live migration
 
 
 
 Hi there,
 
 
 
 
 
 adding a new node to an oVirt 3.0 cluster worked, but migration doesn’t..
 (same hardware, some node version 2.3.0)
 
 “Migration failed due to Error: Could not connect to peer host” (WebGui)
 
 
 
 Thread-2474::ERROR::2013-05-01
 13:58:08,007::SecureXMLRPCServer::73::root::(handle_error) client
 ('172.16.101.102', 60836) (vdsm log on target host)
 
 
 
 I remember there was a bug in this scenario where I had to uncomment the line
 in /etc/libvirt/libvirtd.conf:
 listen_tls = 0 -- #listen_tls = 0
 
 Rebooted the new HV in maintenance mode, the config setup persisted,
 
 but the problem also persists…
 
 
 
 Unfortunately I had the same issue in the past, but I just documented the
 setting in/etc/libvirt/libvirtd.conf
 
 as workaround, so it seems something is still missing…?
 
 
 
 DNS  FQDN are setup properly…
 
 
 
 Does anybody reminds of this bug and may help me out?
 
 (didn’t find this issue in the mail archive)
 
 
 Thanks in advance!
 
 
 
 Best,
 
 Sven.
 
 
 
 Sven Knohsalla | System Administration
 
 
 
 Office +49 631 68036 433 | Fax +49 631 68036 111 |E-Mail
 s.knohsa...@netbiscuits.com | Skype: netbiscuits.admin
 
 Netbiscuits GmbH | Europaallee 10 | 67657 | GERMANY
 
 
 
 
 
 
 
 
 
 
 
 Register Court: Local Court Kaiserslautern | Commercial Register ID: HR B
 3604
 Management Board : Guido Moggert, Michael Neidhöfer, Christian Reitz, Martin
 Süß
 
 
 
 This message and any files transmitted with it are confidential and intended
 solely for the use of the individual or entity to whom they are addressed.
 It may also be privileged or otherwise protected by work product immunity or
 other legal rules. Please notify the sender immediately by e-mail if you
 have received this e-mail by mistake and delete this e-mail from your
 system. If you are not the intended recipient you are notified that
 disclosing, copying, distributing or taking any action in reliance on the
 contents of this information is strictly prohibited.
 
 Warning: Although Netbiscuits has taken reasonable precautions to ensure no
 viruses are present in this email, the company cannot accept responsibility
 for any loss or damage arising from the use of this email or attachments.
 
 
 
 Please consider the environment before printing
 
 
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] questions about vdsm supervdsmserver

2013-04-28 Thread Yaniv Bronheim
Hey bigclouds,
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 have supervdsm as external deamon, as it runs as different user 
(root, vdsm runs as user vdsm). Supervdsm deamon doesn't related to libvirt or 
uses libvirt at all, most of supervdsm functionality is used by vdsm in 
different flows. you can check supervdsm API in supervdsmServer.py and see 
where we call it.

We need to have only one instance of supervdsm with a socket file under 
/var/run/vdsm/ , supervdsm creates this file and vdsm communicate with it. 

Due to your netstat output, most of the time you should have 2 or 3 entries 
unix  2  [ ACC ] STREAM LISTENING 18895145 
/var/run/vdsm/svdsm.sock
unix  2  [ ] STREAM CONNECTED 18895172 
/var/run/vdsm/svdsm.sock
unix  3  [ ] STREAM CONNECTED 18895158 
/var/run/vdsm/svdsm.sock
(multiprocessing package implementation, you can check there)
might be that other subprocesses or subthreads also hold a request to 
svdsm.sock at the time you checked, 
I don't understand the reason for /var/run/mcvda folder at all.. maybe you 
changed something in the configuration? is it always appear? what else do you 
have under this folder?
Normal run shouldn't have more entries as far as I checked.

In addition, I'm working on making supervdsm external service, you can take a 
look and maybe help me with review :)
[http://gerrit.ovirt.org/#/c/11051/]

Regards,
Yaniv Bronhaim.

- Original Message -
 From: bigclouds bigclo...@163.com
 To: users@ovirt.org
 Sent: Friday, April 26, 2013 9:59:47 AM
 Subject: [Users] questions about vdsm supervdsmserver
 
 hi,all.
 i have 2 questions about supervdsmserver,
 1.why it is created separately as a daemon?
 its many function have never been used, and its function can be done by
 calling libvirt directly, why supervdsmserver is need?
 2.it seems that only one supervdsmserver should be exist, by killing old ones
 to assure that . but look at this, and please explain to me.
 unix 2 [ ACC ] STREAM LISTENING 1339963 4968/python /var/run/vdsm/svdsm.sock
 unix 2 [ ACC ] STREAM LISTENING 384165 39716/python nb sp;
 /var/run/vdsm/svdsm.sock
 unix 2 [ ACC ] STREAM LISTENING 1100509 49487/python /var/run/vdsm/svdsm.sock
 unix 2 [ ACC ] STREAM LISTENING 1326232 3813/python /var/run/mcvda/svdsm.sock
 unix 3 [ ] STREAM CONNECTED 1448193 4968/python /var/run/mcvda/svdsm.sock
 unix 3 [ ] STREAM CONNECTED 1447937 4968/python /var /run/mcvda/svdsm.sock
 unix 3 [ ] STREAM CONNECTED 1424959 4968/python /var/run/mcvda/svdsm.sock
 unix 3 [ ] STREAM CONNECTED 1414835 4968/python /var/run/mcvda/svdsm.sock
 unix 3 [ ] STREAM CONNECTED 1327873 3813/python /var/run/mcvda/svdsm.sock
 unix 2 [ ] STREAM CONNECTED 1309612 49487/python  nbsp;
 /var/run/mcvda/svdsm.sock
 unix 3 [ ] STREAM CONNECTED 384221 39716/python /var/run/mcvda/svdsm.sock
 thanks
 
 
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] 102 VDSM processes ?

2013-04-24 Thread Yaniv Bronheim
Hey ,

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 can be wasted by creating those external processes, 
for each domain we start a process pool of 10 processes.

This means that if we configure 10 storage domains on specific host, it starts 
100 process + 1 process for vdsm and 1 for supervdsm.
Each operation on the domain will use one of the processes in the domain's pool.

Vdsm process is the main process that responses to API requests and manage all 
operations. supervdsm is another external process to vdsm that allows vdsm to 
run root commands. 

That's explain the 102 processes that you saw.
We try to make each process allocation small as possible, without loading 
unnecessary packages.

I'll be glad to answer more specific questions about that implementation if 
requested.

Regards,
Yaniv Bronhaim. 

- Original Message -
 From: Alex Leonhardt alex.t...@gmail.com
 To: users@ovirt.org
 Sent: Tuesday, April 16, 2013 1:20:17 AM
 Subject: [Users] 102 VDSM processes ?
 
 Hi,
 
 I'm wondering why my Hyper-Visor is running 102 vdsm processes, each using
 ~20mb = 2GB used ?? Is this expected and normal ??
 
 Thanks,
 Alex
 
 --
 www.vcore.co | www.vsearchcloud.com | Follow @www_vcore_co
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] vdsm unresponsive with python exception

2013-04-14 Thread Yaniv Bronheim
If only you would accept http://gerrit.ovirt.org/#/c/10313, Tony could manage 
to check the syslog for reports and fix it much faster.. :) 
Both patches should be backported IMHO

Thanks,
Yaniv.


- Original Message -
 From: Dan Kenigsberg dan...@redhat.com
 To: Tony Feldmann trfeldm...@gmail.com, Yaniv Bronheim 
 ybron...@redhat.com
 Cc: Joop jvdw...@xs4all.nl, users@ovirt.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:
  That was the issue.  Found out yesterday that vdsm.log was somehow changed
  to root:root.  Just now got a chance to put it back on the mailing list.
  How does the ownership of that file get cahnged.  When the issue occurred I
  am certain there was no one on the system.
 
 http://gerrit.ovirt.org/#/c/12940/ (Separating supervdsm log to
 supervdsm.log file) solves the issue. unfortunately, only on the master
 branch of vdsm.
 
 I think that this is a nasty issue that has to be backported to the
 ovirt-3.2 branch as well, and merits to be part of ovirt-3.2.2.
 
 Regards,
 Dan.
 
  
  
  On Thu, Apr 11, 2013 at 2:15 PM, Joop jvdw...@xs4all.nl wrote:
  
   Dan Kenigsberg wrote:
  
   On Wed, Apr 10, 2013 at 08:59:01AM -0500, Tony Feldmann wrote:
  
  
   I am having a strange issue in my ovirt cluster.  I have 2 hosts, 1
   running
   engine and added as a host and one other system added as a host.  Both
   systems are running gluster across local disks for shared storage.
   Everything was working fine until last night, where my system that is
   also
   running the engine when unresponsive in the admin page.  All vms were
   still
   running that were on the host.  I shut down the vms that were on the
   host
   from within the guest os as I was not able to do anything to the vm
   with
   the host in unresponsive state.  After getting the vms off and
   rebooting
   the host, the vdsmd service says that it is running, but it continually
   restarts the vdsm process and dumps out these messages: detected
   unhandled
   Python exception in '/usr/share/vdsm/vdsm'.  All services say they are
   up
   and running but the host stays in unresponsive state and the vdsm
   process
   keeps respawning.  There is also no data in the vdsm.log.  Can anyone
   shed
   any light on this for me?
  
  
  
   vdsm-de...@fedorahosted.org may be a better place to ask vdsm-specific
   questions.
  
   Could you log into the non-operational host as root, and stop the vdsm
   service.
  
   Then become the vdsm user with
  
   su -s /bin/bash - vdsm
  
   and run /usr/share/vdsm/vdsm manually. Do you see anything in
   particular?
  
  
  
   Please have a look at the permissions/owner of /var/log/vdsm/vdsm.log.
   Should be vdsm:kvm and not root:root
  
   Joop
  
  
 
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] UI lack of ui-plugins

2013-03-05 Thread Yaniv Bronheim
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]
ENGINE_ETC=/etc/ovirt-engine
3. restart Jboss service

If you did the three steps and engine still doesn't start, please attach your 
full engine.log

Yaniv.

- Original Message -
From: bigclouds bigclo...@163.com
To: Oved Ourfalli ov...@redhat.com
Cc: users@ovirt.org
Sent: Tuesday, March 5, 2013 3:02:31 AM
Subject: Re: [Users] UI lack of ui-plugins




hi ovedo 
the explorer is waiting all the time. when go to portal 
http://192.168.5.109:8700/UserPortal/org.ovirt.engine.ui.userportal.UserPortal/UserPortal.html
 




webadmin url see nothing at all 
http://192.168.5.109:8700/webadmin/webadmin/WebAdmin.html 


if http://www.ovirt.org/Building_oVirt_engine is not up to date? 
thanks. 







At 2013-03-04 18:20:20,Oved Ourfalli ov...@redhat.com wrote:


- Original Message -
 From: bigclouds bigclo...@163.com
 To: users@ovirt.org
 Sent: Monday, March 4, 2013 12:07:53 PM
 Subject: [Users] UI lack of ui-plugins
 
 
 
 at last i build engine code success, then i start jboss-as.
 go to http://host:8700, when i click user,admin portal, error occur.
 
 
 1. it reports ui-plugins is miss.
 2. $OVIRT_HOME/backend/manager/conf/engine.conf.defaults
 ENGINE_USR=username
 ENGINE_ETC=/etc/ovirt-engine i do not know what ENGINE_USR really is?
 thanks.
 

ENGINE_USR should be something like /usr/share/ovirt-engine
The warning about the ui-plugins directory is probably because it doesn't 
exist (see bug https://bugzilla.redhat.com/show_bug.cgi?id=895933), but that 
shouldn't effect anything besides loading UI plugins you wrote/downloaded, so 
the admin portal should work properly.

As far as I know, the ENGINE_USR is currently used only in order to detect the 
ui-plugins directory.

What happens when you just browse to
http://host:8700/webadmin
?

Does it work?

 
 error -msg:
 
 
 
 2013-03-04 17:39:10,182 INFO
 [org.ovirt.engine.core.bll.DbUserCacheManager]
 (DefaultQuartzScheduler_Worker-1) Start refreshing all users data
 2013-03-04 17:39:10,338 INFO
 [org.ovirt.engine.core.vdsbroker.ResourceManager] (MSC service
 thread 1-1) Finished initializing ResourceManager
 2013-03-04 17:39:10,365 INFO
 [org.ovirt.engine.core.bll.AsyncTaskManager] (MSC service thread
 1-1) Initialization of AsyncTaskManager completed successfully.
 2013-03-04 17:39:10,384 INFO
 [org.ovirt.engine.core.bll.OvfDataUpdater] (MSC service thread 1-1)
 Initialization of OvfDataUpdater completed successfully.
 2013-03-04 17:39:10,388 INFO [org.ovirt.engine.co
 re.bll.VdsLoadBalancer] (MSC service thread 1-1) Start scheduling to
 enable vds load balancer
 2013-03-04 17:39:10,394 INFO
 [org.ovirt.engine.core.bll.VdsLoadBalancer] (MSC service thread 1-1)
 Finished scheduling to enable vds load balancer
 2013-03-04 17:39:10,410 INFO
 [org.ovirt.engine.core.bll.network.MacPoolManager]
 (pool-10-thread-1) Start initializing MacPoolManager
 2013-03-04 17:39:10,450 INFO
 [org.ovirt.engine.core.bll.InitBackendServicesOnStartupBean] (MSC
 service thread 1-1) Init VM custom properties utilities
 2013-03-04 17:39:10,461 INFO
 [org.ovirt.engine.core.bll.network.MacPoolManager]
 (pool-10-thread-1) Finished initializing MacPoolManager
 2013-03-04 17:39:10,470 INFO [org.jboss.as] (MSC service thread 1-2)
 JBAS015951: Admin console listening on http://127.0.0.1:9990
 2013-03-04 17:39:10,471 INFO [org.jboss.as] (MSC service thread 1-2)
 JBAS015874: JBoss AS 7.1.1.Final  Brontes started in 11961ms -
 Started 507 of 594 services (86 services are passive or on-demand)
 2013-03-04 17:39:10,560 INFO [org.jboss.as.server]
 (DeploymentScanner-threads - 2) JBAS018559: Deployed engine.ear
 2013-03-04 17:42:22,716 ERROR [org.jboss.remoting.remote.connection]
 (Remoting ovirtdev read-1) JBREM000200: Remote connection failed:
 java.io.IOException: Received an invalid message length of
 1195725856
 2013-03-04 17:42:56,702 ERROR [org.jboss.remoting.remote.connection]
 (Remoting ovirtdev read-1) JBREM000200: Remote connection failed:
 java.io.IOException: Received an invalid message length of
 1195725856
 2013-03-04 17:45:14,258 INFO [org.hibernate.validator.util.Version]
 (http--0.0.0.0-8700-1) Hibernate Validator 4.2.0.Final
 2013-03-04 17:45:14,385 INFO
 [org.ovirt.engine.core.utils.LocalConfig] (http--0.0.0.0-8700-1)
 Loaded file
 /mnt/ovirt-engine/backend/manager/conf/engine.conf.defaults.
 2013-03-04 17:45:14,386 INFO
 [org.ovirt.engine.core.utils.LocalConfig] (http--0.0.0.0-8700-1)
 Loaded file /etc/sysconfig/ovirt-engine.
 2013-03-04 17:45:14,392 INFO
 [org.ovirt.engine.core.utils.LocalConfig] (http--0.0.0.0-8700-1)
 Value of property ENGINE_DEBUG_ADDRESS is 0.0.0.0:8787.
 2013-03-04 17:45:14,393 INFO
 [org.ovirt.engine.core.utils.LocalConfig] (http--0.0.0.0-8700-1)
 Value of property 

[Users] Fwd: build vdsm error at TestSuperVdsm

2013-03-04 Thread Yaniv Bronheim
Hey bigclouds,
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 error  at TestSuperVdsm

OK. so first, you can work with NOSE_EXCLUDE=.* until we figure the error. try 
to get into vdsm/tests folder and run
./run_tests_local.sh -s superVdsmTests.py
and tell me what you've got. it runs only supervdsm tests.

if it doesn't work, check if vdsm is running, stop it and try again.
i just did the same, fetch the last code and ran with the tests and it works 
(with some exceptions, but works)

TestSuperVdsm
testIsSuperUp   Exception 
AttributeError: AttributeError('_DummyThread' object has no attribute 
'_Thread__block',) in module 'threading' from 
'/usr/lib64/python2.7/threading.pyc' ignored
OK
testKillSuper   Exception 
AttributeError: AttributeError('_DummyThread' object has no attribute 
'_Thread__block',) in module 'threading' from 
'/usr/lib64/python2.7/threading.pyc' ignored
OK
testNoPidFile   Exception 
AttributeError: AttributeError('_DummyThread' object has no attribute 
'_Thread__block',) in module 'threading' from 
'/usr/lib64/python2.7/threading.pyc' ignored
OK

seems like its something with your environment, and we will figure what is it 
if you want

- Original Message -
From: bigclouds bigclo...@163.com
To: Yaniv Bronheim ybron...@redhat.com
Cc: users@ovirt.org
Sent: Friday, March 1, 2013 3:26:18 AM
Subject: Re:Re: [Users] build vdsm error  at TestSuperVdsm





i get it ' git clone http://gerrit.ovirt.org/p/vdsm.git' this morning. and make 
it again. error remains. 

i fellow http://www.ovirt.org/Vdsm_Developers step by step until( make rpm 
).but if add ' NOSE_EXCLUDE=.* ' ,make can success 
thanks. 

error message: 

testConnectWithoutCertificateFails OK testSessionIsCached OK 
SPM_MailMonitorTests 
testThreadLeak OK 
TestSuperVdsm 
testIsSuperUp WARNING:SuperVdsmProxy:Connect to svdsm failed [Errno 111] 
Connection refused 
WARNING:SuperVdsmProxy:Connect to svdsm failed [Errno 111] Connection refused 
WARNING:SuperVdsmProxy:Connect to svdsm failed [Errno 111] Connection refused 
ERROR:Storage.Misc:Panic: Couldn't connect to supervdsm 
Traceback (most recent! call last): 
File /root/rpmbuild/BUILD/vdsm-! 4.10.3/vdsm/supervdsm.py, line 202, in 
launch 
utils.retry(self._connect, Exception, timeout=60, tries=3) 
File /root/rpmbuild/BUILD/vdsm-4.10.3/vdsm/utils.py, line 1001, in retry 
return func() 
File /root/rpmbuild/BUILD/vdsm-4.10.3/vdsm/supervdsm.py, line 188, in 
_connect 
self._manager.connect() 
File /usr/lib64/python2.6/multiprocessing/managers.py, line 474, in connect 
conn = Client(self._address, authkey=self._authkey) 
File /usr/lib64/python2.6/multiprocessing/connection.py, line 143, in Client 
c = SocketClient(address) 
File /usr/lib64/python2.6/multiprocessing/connection.py, line 263, in 
SocketClient 
s.connect(address) 
File string, line 1, in connect 
error: [Errno 111] Connection refused 
Kil! led 
[root@ovirtdev vdsm]# ./autogen.sh --system  ./configure --enable-hooks  
make rpm 



At 2013-02-28 23:33:10,Yaniv Bronheim  ybron...@redhat.com  wrote:
i dont think they're related at all

run it without the tests:
./autogen.sh --system  ./configure --enable-hooks  make rpm NOSE_EXCLUDE=.*

tell me what you've got..
what vdsm branch do you compile? master or ovirt-3.2?

- Original Message -
From: bigclouds  bigclo...@163.com 
To: Yaniv Bronheim  ybron...@redhat.com 
Sent: Thursday, February 28, 2013 5:18:20 PM
Subject: Re:Re: [Users] build vdsm error  at TestSuperVdsm



hi, i think the error occurs when do unit test during compiling engine code. 
my env is centos6.3,engine code is latest from git-repo. 








At 2013-02-28 22:00:08,Yaniv Bronheim  ybron...@redhat.com  wrote:
Hey,
Maybe you've got vdsm that already runs on your machine ? but it doesn't 
supposed to throw this exception anyway
/msg NickServ identify 
What version of vdsm do you compile?? maybe the tests couldn't create the 
socket for the communication between supervdsm and vdsm.. 
its wrong that all the compilation fails that way.. ill check it. but did you 
try more than once to run it?


- Original Message -
From: bigclouds  bigclo...@163.com 
To: users@ovirt.org Sent: Thursday, February 28, 2013 7:47:37 AM
Subject: [Users] build vdsm error  at TestSuperVdsm




testThreadLeak OK 
TestSuperVdsm 
testIsSuperUp WARNING:SuperVdsmProxy:Connect to svdsm failed [Errno 111] 
Connection refused 
WARNING:SuperVdsmProxy:Connect to svdsm failed [Errno 111] Connection refused 
WARNING:SuperVdsmProxy:Connect to svdsm failed [Errno 111] Connection refused 
ERROR:Storage.Misc:Panic: Couldn't connect to supervdsm 
Traceback (most

Re: [Users] how to debug vdsm and node codes

2013-02-28 Thread Yaniv Bronheim
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 great with 
VDSM. you just need to add comment where you want to see the values or check if 
the program went there. All you need to do is to edit the specific installed 
files (located at /usr/share/vdsm) restart the service and wait for your print 
in the log.. 

Good luck 


- Original Message -
From: bigclouds bigclo...@163.com
To: users@ovirt.org
Sent: Thursday, February 28, 2013 5:26:14 PM
Subject: [Users] how to debug vdsm and node codes



a debug environment in which to debug vdsm and node code line by line 


thanks. 


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users