Description of problem:
When installing a new host or reinstalling existing one, the installation completes but the host becomes "non-responsive".

Version-Release number of selected component (if applicable):
oVirt: 4.1.0-0.0.master.20161107231322.git50adf28.el7.centos
Vdsm: vdsm-4.18.999-798.git7a306d6.el7.centos.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Add / Reinstall new host
2. Verify sure all host components are install with the recent oVirt snapshot
3. Host becomes non-responsive and communication errors appear in the log

Actual results:
Host becomes non-responsive

Expected results:
Host should be added to the engine and become responsive

Additional info:

2016-11-08 18:05:03,319 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler1) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM h
ost_mixed_2 command failed: Message timeout which can be caused by communication issues
2016-11-08 18:05:03,319 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler1) [] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand'
 return value 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSInfoReturnForXmlRpc@6d559e70'
2016-11-08 18:05:03,320 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler1) [] HostName = host_mixed_2
2016-11-08 18:05:03,320 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler1) [] Command 'GetCapabilitiesVDSCommand(HostName = host_mixed_2, VdsIdAndVdsVDSCom
mandParametersBase:{runAsync='true', hostId='e8b8cc5c-d510-4f84-b6a1-ec2653d43b81', vds='Host[host_mixed_2,e8b8cc5c-d510-4f84-b6a1-ec2653d43b81]'})' execution failed: VDSGenericException: VDSNetworkExceptio
n: Message timeout which can be caused by communication issues
2016-11-08 18:05:03,320 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (DefaultQuartzScheduler1) [] Failure to refresh host 'host_mixed_2' runtime info: VDSGenericException: VDSNetworkExc
eption: Message timeout which can be caused by communication issues
2016-11-08 18:05:06,326 INFO  [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to /10.35.128.28
2016-11-08 18:05:07,412 WARN  [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) [] Exception thrown during message processing
2016-11-08 18:05:09,075 WARN  [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) [] Exception thrown during message processing
2016-11-08 18:05:18,320 WARN  [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) [] Exception thrown during message processing
2016-11-08 18:05:20,322 WARN  [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) [] Exception thrown during message processing
2016-11-08 18:05:41,350 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (DefaultQuartzScheduler8) [] Command 'GetAllVmStatsVDSCommand(HostName = host_mixed_1, VdsIdVDSCommandParame
tersBase:{runAsync='true', hostId='f3dadec8-5b39-429d-8050-1e03bf37f7d2'})' execution failed: VDSGenericException: VDSNetworkException: Vds timeout occured