[Users] VDSM errors on fedora17

[Dennis Jacobfeuerborn]

On 06/12/2012 11:51 AM, Dan Kenigsberg wrote:
> On Mon, Jun 11, 2012 at 05:38:24PM -0500, Adam Litke wrote:
>> On Sun, Jun 10, 2012 at 11:23:22AM +0300, Dan Kenigsberg wrote:
>>> On Thu, Jun 07, 2012 at 05:35:06PM +0300, Itamar Heim wrote:
>>>> On 06/07/2012 10:10 AM, Haim Ateya wrote:
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: ovirt at qip.ru
>>>>>> To: users at ovirt.org
>>>>>> Sent: Thursday, June 7, 2012 9:22:35 AM
>>>>>> Subject: [Users] VDSM errors on fedora17
>>>>>>
>>>>>>
>>>>>> VDSM from http:// www . ovirt .org/releases/beta/fedora/17/ www.
>>>>>> ovirt .org/releases/beta/fedora/17/ ovirt
>>>>>> -engine-dbscripts-3.1.0_0001-0. gitf 093e0.fc17.noarch.rpm">  gitf
>>>>>> 093e0
>>>>>>
>>>>>> VDSM started and working but
>>>>>>
>>>>>> 1. after start there was error in vdsm .log
>>>>>>
>>>>>> MainThread:: ERROR ::2012-06-07 10:05:23,883::clientIF::151::vds::(_
>>>>>> prepareBindings ) Unable to load the rest server module. Please make
>>>>>> sure it is installed.
>>>>>
>>>>> please install: vdsm-rest-4.9.6-2.gite952471.fc17.noarch.rpm
>>>>
>>>> should this be an error, or only an INFO that the REST bindings are
>>>> not installed?
>>>
>>> I think INFO should have been enough.
>>
>> That means that rest was set to enabled in vdsm.conf but it is not installed.
>> Maybe that's an error because we cannot comply with a specific configuration
>> request.  I can see it both ways.
> 
> I see what you mean, but note that vdsm-rest is enabled by default, but not
> installed as part of ovirt. This means that practically all users would
> see this frightening ERROR.

Speaking as an admin if REST support is enabled (either explicitly or as a
default) but cannot be properly setup then vdsm should bail out with an error.

When I provide a daemon with a configuration X then I expect it to run with
configuration X. If it cannot do so then I want it to fail and complain
about why it cannot run in this configuration so I can fix things.

Silently running with configuration Y instead (which is X - REST in this
case) and only outputting a INFO message in some log is not a good option.

Regards,
  Dennis