On Sun, Apr 23, 2017 at 2:32 PM, Arman Khalatyan <arm2arm(a)gmail.com> wrote:
Hi Yaniv,
I'm unfortunately there is nothing in the logs, it looks like a ovirt
doesnot listen to the right interface.
We have multiples interfaces internal and external access.
We sometimes ago we renamed the engine name to work with the external ip
address. Now it is listening only to the local address.
To fix it i just added:
/etc/ovirt-engine/engine.conf.d/99-setup-http-proxy.conf
And this file did not survive the upgrade?
Y.
One need to dig more to fix it
Am 20.04.2017 2:55 nachm. schrieb "Yaniv Kaul" <ykaul(a)redhat.com>:
>
>
> On Thu, Apr 20, 2017 at 1:06 PM, Arman Khalatyan <arm2arm(a)gmail.com>
> wrote:
>
>> After the recent upgrade from ovirt Version 4.1.1.6-1.el7.centos. to
>> Version 4.1.1.8-1.el7.centos
>>
>> The web portal gives following error:
>> Bad Request
>>
>> Your browser sent a request that this server could not understand.
>>
>> Additionally, a 400 Bad Request error was encountered while trying to
>> use an ErrorDocument to handle the request.
>>
>>
>> Are there any hints how to fix it?
>>
>
> It'd be great if you could share some logs. The httpd logs, server.log
> and engine.log, all might be useful.
> Y.
>
>
>> BTW the rest API works as expected, engine-setup went without errors.
>>
>> Thanks,
>>
>> Arman.
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>