Re: [Users] ovirt-report Forbidden access error
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
To: "Yedidyah Bar David" <didi(a)redhat.com>
Cc: "Alessandro Bianchi" <a.bianchi(a)skynet.it>, "users"
<users(a)ovirt.org>
Sent: Tuesday, February 4, 2014 3:25:37 PM
Subject: Re: [Users] ovirt-report Forbidden access error
On Tue, Feb 4, 2014 at 2:06 PM, Yedidyah Bar David wrote:
> ----- Original Message -----
>> From: "Alessandro Bianchi" <a.bianchi(a)skynet.it>
>> To: "Yedidyah Bar David" <didi(a)redhat.com>
>> Cc: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>,
"users"
>> <users(a)ovirt.org>
>> Sent: Tuesday, February 4, 2014 2:49:47 PM
>> Subject: Re: [Users] ovirt-report Forbidden access error
> [snip]
>
> (for now I'll ignore the confs (which seem ok) and the logs (which will
> require more time to understand)
>
>> postgres-# select * from vdc_options where
>> option_name='RedirectServletReportsPage'
>> postgres-#
>> (no results)
>
> This is probably the source of the problem.
>
> Can you post all the setup log files (engine, dwh, reports)?
>
> The line is normally inserted by engine-setup and updated by reports-setup.
> --
> Didi
In fact in my case where it is working I have:
engine=# select * from vdc_options where
option_name='RedirectServletReportsPage';
option_id | option_name |
option_value | version
-----------+----------------------------+-----------------------------------------------------------+---------
281 | RedirectServletReportsPage |
https://my-engine:443/ovirt-engine-reports | general
(1 row)
Indeed, that's updated to be so by reports setup. But Alessandro
reported he does not have this row at all, which is probably some bug
or problem in engine-setup.
We can quite easily patch reports setup to add this row if it does not
exist, but it might imply some deeper problems in the setup which should
probably be fixed anyway.
--
Didi