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.
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 <kmayi...@redhat.com
<mailto:kmayi...@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@ovirt.org <mailto:Engine-devel@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
