[Users] NoRouteToHostException when adding F18 host to engine built with latest source.

Mon Mar 11 08:19:33 UTC 2013

Hi Sharad,

I am not sure this is related, but in F18 if you change the name of the engine host at installation from the default 'localhost.localdomain' then it will not appear in the /etc/hosts file and the system will not be able to resolve the address of the host it is running on and this breaks some functionality in most java programs. Probably this is the reason of the exception you get, not that the engine is not able to connect to vdsm.

If this does not solve the problem, could you increase log level? A stack trace would be great :)

Thank you,
Laszlo

----- Original Message -----
> From: snmishra at linux.vnet.ibm.com
> To: users at ovirt.org
> Sent: Friday, March 8, 2013 9:46:44 PM
> Subject: [Users] NoRouteToHostException when adding F18 host to engine built with latest source.
> 
> 
> Hi,
> 
> 	I am trying to setup 2 F18 machines as ovirt engine and host. On the
> first machine I
> 
> 1. built engine from source,
> 2. copied vdsm bootstrap files as documented at
> http://www.ovirt.org/Building_oVirt_engine#Copying_vdsm_bootstrap_files
> and
> 3. completed the steps at
> http://www.ovirt.org/Building_oVirt_engine#Deploying_engine-config_.26_engine-manage-domains
> and deployed the
> engine.
> 
> 	Other F18 machine is just a minimal install of F18, iptables running
> as mentioned at
> http://www.ovirt.org/Quick_Start_Guide#Install_Fedora_Host
> 
> 	I start webadmin and go to add a new host (second F18), but it
> immediately goes to non-responsive state.
> 
> 
> 
> 
> 2013-03-08 15:37:26,833 INFO
> [org.ovirt.engine.core.bll.AddVdsCommand] (http--0.0.0.0-8700-6)
> [6c833e18] Running command: AddVdsCommand internal: false. Entities
> affected :  ID: 99408929-82cf-4dc7-a532-9d998063fa95 Type: VdsGroups
> 2013-03-08 15:37:26,868 INFO
> [org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (http--0.0.0.0-8700-6)
> [3ad6cd4e] Running command: AddVdsSpmIdCommand internal: true.
> Entities affected :  ID: ca519cc1-7579-4292-9d49-c68aba649991 Type:
> VDS
> 2013-03-08 15:37:26,881 INFO
> [org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (http--0.0.0.0-8700-6)
> [3ad6cd4e] Lock freed to object EngineLock [exclusiveLocks= key:
> 5849b030-626e-47cb-ad90-3ce782d831b3 value: REGISTER_VDS
> , sharedLocks= ]
> 2013-03-08 15:37:26,883 ERROR
> [org.ovirt.engine.core.vdsbroker.ResourceManager]
> (http--0.0.0.0-8700-6) [3ad6cd4e] Cannot get vdsManager for
> vdsid=ca519cc1-7579-4292-9d49-c68aba649991
> 2013-03-08 15:37:26,885 INFO
> [org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand]
> (http--0.0.0.0-8700-6) [3ad6cd4e] START, RemoveVdsVDSCommand(HostName
> = ovirt2, HostId = ca519cc1-7579-4292-9d49-c68aba649991), log id:
> 684f7786
> 2013-03-08 15:37:26,887 ERROR
> [org.ovirt.engine.core.vdsbroker.ResourceManager]
> (http--0.0.0.0-8700-6) [3ad6cd4e] Cannot get vdsManager for
> vdsid=ca519cc1-7579-4292-9d49-c68aba649991
> 2013-03-08 15:37:26,888 INFO
> [org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand]
> (http--0.0.0.0-8700-6) [3ad6cd4e] FINISH, RemoveVdsVDSCommand, log
> id:
> 684f7786
> 2013-03-08 15:37:26,889 ERROR
> [org.ovirt.engine.core.vdsbroker.ResourceManager]
> (http--0.0.0.0-8700-6) [3ad6cd4e] Cannot get vdsManager for
> vdsid=ca519cc1-7579-4292-9d49-c68aba649991
> 2013-03-08 15:37:26,891 INFO
> [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand]
> (http--0.0.0.0-8700-6) [3ad6cd4e] START, AddVdsVDSCommand(HostName =
> ovirt2, HostId = ca519cc1-7579-4292-9d49-c68aba649991), log id:
> 35d874d9
> 2013-03-08 15:37:26,892 INFO
> [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand]
> (http--0.0.0.0-8700-6) [3ad6cd4e] AddVds - entered , starting logic
> to
> add VDS ca519cc1-7579-4292-9d49-c68aba649991
> 2013-03-08 15:37:26,893 INFO
> [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand]
> (http--0.0.0.0-8700-6) [3ad6cd4e] AddVds - VDS
> ca519cc1-7579-4292-9d49-c68aba649991 was added, will try to add it to
> the resource manager
> 2013-03-08 15:37:26,894 INFO
> [org.ovirt.engine.core.vdsbroker.VdsManager] (http--0.0.0.0-8700-6)
> [3ad6cd4e] Entered VdsManager constructor
> 2013-03-08 15:37:26,896 INFO
> [org.ovirt.engine.core.vdsbroker.VdsManager] (http--0.0.0.0-8700-6)
> [3ad6cd4e] Initialize vdsBroker (9.27.28.20,54,321)
> 2013-03-08 15:37:26,897 INFO
> [org.ovirt.engine.core.vdsbroker.ResourceManager]
> (http--0.0.0.0-8700-6) [3ad6cd4e] VDS
> ca519cc1-7579-4292-9d49-c68aba649991 was added to the Resource
> Manager
> 2013-03-08 15:37:26,898 INFO
> [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand]
> (http--0.0.0.0-8700-6) [3ad6cd4e] FINISH, AddVdsVDSCommand, log id:
> 35d874d9
> 2013-03-08 15:37:29,946 WARN
> [org.ovirt.engine.core.vdsbroker.VdsManager]
> (DefaultQuartzScheduler_Worker-9) Failed to refresh VDS , vds =
> ca519cc1-7579-4292-9d49-c68aba649991 : ovirt2, VDS Network Error,
> continuing.
> java.net.NoRouteToHostException: No route to host
> 2013-03-08 15:37:32,953 WARN
> [org.ovirt.engine.core.vdsbroker.VdsManager]
> (DefaultQuartzScheduler_Worker-10) Failed to refresh VDS , vds =
> ca519cc1-7579-4292-9d49-c68aba649991 : ovirt2, VDS Network Error,
> continuing.
> java.net.NoRouteToHostException: No route to host
> 2013-03-08 15:37:35,987 ERROR
> [org.ovirt.engine.core.vdsbroker.VdsManager]
> (DefaultQuartzScheduler_Worker-2) Server failed to respond, vds_id =
> ca519cc1-7579-4292-9d49-c68aba649991, vds_name = ovirt2, error =
> java.net.NoRouteToHostException: No route to host
> 
> 
> I can ssh from engine to host machine using the authentication
> provided in new host dialog.
> 
> -Sharad
> 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 