[Engine-devel] Failed to configure management network on the host

Tue Jun 4 09:03:54 UTC 2013

Hi Moti,

Had to reproduce this again to get the logs. Attached both engine and 
vdsm logs.

engine:
[org.ovirt.engine.core.vdsbroker.vdsbroker.CollectVdsNetworkDataVDSCommand] 
(pool-4-thread-4) [59b99e5d] Command CollectVdsNetworkDataVDS execution 
failed. Exception: VDSNetworkException: java.net.ConnectException: 
Connection refused

vdsm (based on flow id 59b99e5d) - no entries found.

However there's a line (without any flowId) -
Thread-13::DEBUG::2013-06-04 
14:21:05,227::BindingXMLRPC::913::vds::(wrapper) client 
[10.70.42.245]::call getCapabilities with () {}

thanks
sahina

On 06/04/2013 01:45 PM, Moti Asayag wrote:
> On 06/04/2013 09:52 AM, Sahina Bose wrote:
>> Hi Moti,
>>
>> Not sure I understand your comment about host activation flow.
>> commit bdd8966d97e1e02e775ee6f755d0a3637a668911  (engine: Remove mgmt
>> network setup from host activation) is present in our code base, but we
>> were not using the host activation flow.
> Hi,
>
> My fault, i had a different old thread in my mind.
>
> The relevant part from the engine.log indicates that the host deployment
> ended successfully, host was able to ping VDSM, but the first attempt to
> run getVdsCaps on vdsm failed.
>
> Could you add the relevant vdsm.log which contains the flow-ID 740c5292
> which matches the same correlation-id from the engine.log ?
>
>
> 2013-06-03 20:06:49,638 INFO
> [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation
> 10.70.43.140: Stage: Termination
> 2013-06-03 20:06:49,881 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand]
> (pool-4-thread-48) [740c5292] java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2013-06-03 20:06:49,882 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand]
> (pool-4-thread-48) [740c5292] Command PollVDS execution failed.
> Exception: RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 2013-06-03 20:06:50,382 INFO
> [org.ovirt.engine.core.bll.network.NetworkConfigurator]
> (pool-4-thread-48) [740c5292] Engine managed to communicate with VDSM
> agent on host s2
> 2013-06-03 20:06:50,393 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.CollectVdsNetworkDataVDSCommand]
> (pool-4-thread-48) [740c5292] Command CollectVdsNetworkDataVDS execution
> failed. Exception: VDSNetworkException: java.net.ConnectException:
> Connection refused
>
> Thanks,
> Moti
>
>> Here's what we tried to do.
>> Add a host (with vdsm 4.10.2 installed) to engine (built from Jun 2
>> upstream codebase).
>>
>> The installation failed with "Failed to configure manamgent network on
>> the host"
>>
>> and the logs had this
>>
>> 2013-06-03 19:49:03,390 INFO
>> [org.ovirt.engine.core.bll.network.NetworkConfigurator]
>> (pool-4-thread-50) [7bf46c88] Engine managed to communicate with VDSM
>> agent on host s1
>> 2013-06-03 19:49:03,412 ERROR
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.CollectVdsNetworkDataVDSCommand]
>> (pool-4-thread-50) [7bf46c88] Command CollectVdsNetworkDataVDS execution
>> failed. Exception: VDSNetworkException: java.net.ConnectException:
>> Connection refused
>>
>> As Kanagaraj mentioned, reverting the Change Iaf82e104: engine:
>> Allow engine to configure management network , fixed this issue.
>>
>>  From the flowchart on
>> http://www.ovirt.org/Features/Normalized_ovirtmgmt_Initialization, it
>> seems to fail on the "Configure Management Network (by setup networks)"
>> action.
>>
>> Any help on solving this would be appreciated.
>>
>> thanks
>> sahina
>>
>>
>>
>> On 06/04/2013 11:53 AM, Moti Asayag wrote:
>>> Hi,
>>>
>>> Same host activation flow should work on the master as well as the
>>> management network will not be created as part of the host activation.
>>> So reverted changes were already merged by commit
>>> bdd8966d97e1e02e775ee6f755d0a3637a668911
>>>
>>> For more details about host installation see:
>>> http://www.ovirt.org/Features/Normalized_ovirtmgmt_Initialization
>>>
>>> Thanks,
>>> Moti
>>>
>>> See
>>> On 06/04/2013 08:51 AM, Kanagaraj wrote:
>>>> Host installation went through successfully after reverting the change
>>>> eca95e192ebf3e1fe0e9440bb8fac694214ca8fd (Change Iaf82e104: engine:
>>>> Allow engine to configure management network ).
>>>>
>>>> Thanks,
>>>> Kanagaraj
>>>>
>>>> On 06/04/2013 12:23 AM, Dead Horse wrote:
>>>>> Seeing this as well but during host activation with latest master
>>>>> vdsm/engine.
>>>>> --> http://lists.ovirt.org/pipermail/engine-devel/2013-June/004752.html
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Jun 3, 2013 at 9:45 AM, Kanagaraj <kmayilsa at redhat.com
>>>>> <mailto:kmayilsa at redhat.com>> wrote:
>>>>>
>>>>>       Hi,
>>>>>
>>>>>        After adding a host to a 3.2 cluster, bootstrap went through fine
>>>>>       and in the end it failed with the following error.
>>>>>
>>>>>       "Host s2 installation failed. Failed to configure manamgent
>>>>>       network on the host."
>>>>>
>>>>>       Attached engine.log and vdsm.log
>>>>>
>>>>>       Vdsm rpms:
>>>>>       vdsm-4.10.2-22.2.el6rhs.x86_64
>>>>>       vdsm-python-4.10.2-22.2.el6rhs.x86_64
>>>>>       vdsm-cli-4.10.2-22.2.el6rhs.noarch
>>>>>       vdsm-gluster-4.10.2-22.2.el6rhs.noarch
>>>>>       vdsm-xmlrpc-4.10.2-22.2.el6rhs.noarch
>>>>>
>>>>>       Engine rpms: recent code from master
>>>>>
>>>>>       Can someone please help in resolving this issue,
>>>>>
>>>>>       Thanks,
>>>>>       Kanagaraj
>>>>>
>>>>>       _______________________________________________
>>>>>       Engine-devel mailing list
>>>>>       Engine-devel at ovirt.org <mailto:Engine-devel at ovirt.org>
>>>>>       http://lists.ovirt.org/mailman/listinfo/engine-devel
>>>>>
>>>>>
>>> _______________________________________________
>>> Engine-devel mailing list
>>> Engine-devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/engine-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: engine.log
Type: text/x-log
Size: 53624 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20130604/c2233249/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vdsm.log
Type: text/x-log
Size: 28178 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20130604/c2233249/attachment-0003.bin>