[ovirt-users] hosted engine install fails for bonded interface

Wed Jun 7 10:16:07 UTC 2017

The only thing that I can think it that the HE VM FQDN does not resolvable
via DNS, so when the HE deployment tries to reach it, he fails.
Can you check that you can connect to the HE VM via FQDN "happyhourovirt"
after the engine-setup?

Best Regards

On Wed, Jun 7, 2017 at 11:46 AM, Ramachandra Reddy Ankireddypalle <
rcreddy.ankireddypalle at gmail.com> wrote:

> Please find attached hosted engine setup log.
> hosted-engine deploy is stuck in the following loop.
>
>           |- HE_APPLIANCE_ENGINE_SETUP_SUCCESS
> [ INFO  ] Engine-setup successfully completed
> [ INFO  ] Engine is still unreachable
> [ INFO  ] Engine is still not reachable, waiting...
>
>
> On Wed, Jun 7, 2017 at 3:40 AM, Artyom Lukianov <alukiano at redhat.com>
> wrote:
>
>> Hi, can you please provide the ovirt-hosted-engine-setup log?
>>
>> On Wed, Jun 7, 2017 at 9:45 AM, Ramachandra Reddy Ankireddypalle <
>> rcreddy.ankireddypalle at gmail.com> wrote:
>>
>>> Hi,
>>>      I created a bonded interface consisting of two network interfaces.
>>> When I tried to install hosted engine over the bonded interface, it fails
>>> at the end with the following error message:
>>>
>>>      [ ERROR ] Cannot automatically add the host to cluster Default:
>>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400
>>> Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent
>>> a request that this server could not understand.<br /> </p> </body></html>
>>>
>>>      If I try to install over the eth interface instead of the bonded
>>> interface the install succeeds. Please suggest what needs to be done to use
>>> bonded interface.
>>>
>>> Thanks and Regards,
>>> Ram
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170607/24fb7e53/attachment-0001.html>