The actual operation of creating host is taking time. I believe
we've handled its timeout before, but it is possible that our waiting period is still
too short.
I will look into this.
Veli, could you open a bug please? Thank you.
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Eli Mesika" <emesika(a)redhat.com>
Cc: "Veli-Matti Leppänen" <vellu(a)velhot.net>, users(a)ovirt.org, "Alex
Lourie" <alourie(a)redhat.com>
Sent: Sunday, August 19, 2012 7:33:27 PM
Subject: Re: [Users] Problems with F17 and ovirt 3.1
On 08/19/2012 12:14 PM, Eli Mesika wrote:
>
>
> ----- Original Message -----
>> From: "Veli-Matti Leppänen" <vellu(a)velhot.net>
>> To: users(a)ovirt.org
>> Sent: Sunday, August 19, 2012 11:47:46 AM
>> Subject: Re: [Users] Problems with F17 and ovirt 3.1
>>
>>
>> On 2012-08-19 10:48, Eli Mesika wrote:
>>> ----- Original Message -----
>>>> From: "Veli-Matti Leppänen" <vellu(a)velhot.net>
>>>> To: users(a)ovirt.org
>>>> Sent: Saturday, August 18, 2012 1:13:23 PM
>>>> Subject: Re: [Users] Problems with F17 and ovirt 3.1
>>>>
>>>> Hi.
>>>>
>>>> I tried to install ovirt 3.1 on clean F17 hosts. I tried
>>>> all-in-one
>>>> and plain manager + node installation, but every time host is just
>>>> non-responsive.
>>>>
>>>> vdsmd service does not start
>>>> [root@maila ~]# service vdsmd start
>>>> Redirecting to /bin/systemctl start vdsmd.service
>>>> Job canceled.
>>>> and there is no vdsm log.
>>>>
>>>> selinux or iptables is not the issue, cause setting selinux to
>>>> permissive mode or flushing the firewall does not help.
>>>>
>>>> any ideas where to start?
>>>
>>> There was an excellent step-by-step video showing how to install
>>> all-in-one on top of f17
>>> please follow and check again
>>>
>>>
http://blog.jebpages.com/archives/up-and-running-with-ovirt-3-1-edition/
>>>
>>
>> I followed that video. Installation times out during adding local
>> host.
>> Web admin console shows it installing and after that it goes to
>> non-responsing state.
> Hi again
> please refer to the following (taken from the same site)
>
> I’ve found that the all-in-one installer sometimes times out during the install
process. If the script times out during the final “AIO: Adding Local host (This may take
several minutes)” step, you can proceed to the web admin console to complete the process.
If it times out at an earlier point, like waiting for the jboss-as server to start, you
should run “engine-cleanup” and then re-run “engine-setup”.
>
>>
>>>>
>>>> /Vellu
>>>>
>>>>
>>>> ---
>>>> ______________________
>>>> Veli-Matti Leppänen
>>>> vellu(a)velhot.net
>>>> Velzi @ IRC
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users(a)ovirt.org
>>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
Eli/Alex - what are we timing out on?
1. all-in-one rpm is supposed to require vdsm rpms so the add host
wouldn't really need to install them
2. all-in-one is skipping the reboot