Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1097784

Summary: Can't add host to the DC/Cluster in 3.0
Product: Red Hat Enterprise Virtualization Manager Reporter: GenadiC <gcheresh>
Component: vdsmAssignee: lpeer <lpeer>
Status: CLOSED NOTABUG QA Contact: GenadiC <gcheresh>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: alonbl, bazulay, gcheresh, gklein, iheim, lpeer, myakove, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-15 06:13:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vdsm, host deploy and engine logs none

Description GenadiC 2014-05-14 14:09:56 UTC
Created attachment 895505 [details]
vdsm, host deploy and engine logs

Description of problem:
ovirt-host-deploy attempts to connect to 127.0.0.1:80 and fails as engine is installed not on local machine

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Add host to DC/Cluster 3.0
2.
3.

Actual results:
Host installation fails

Expected results:
Host installation should succeed

Additional info:
Performing the same action for DC/Cluster 3.4 is working as expected.

Traceback (most recent call last):
  File "/tmp/ovirt-c3oAOVstQK/otopi-plugins/ovirt-host-deploy/vdsm/bridge.py", line 666, in _validation
    retries=2,
  File "/tmp/ovirt-c3oAOVstQK/otopi-plugins/ovirt-host-deploy/vdsm/bridge.py", line 264, in _waitForRoute
    port=host[1],
RuntimeError: Cannot establish connection to 127.0.0.1:80
2014-05-14 15:41:54 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge bridge._waitForRoute:211 host=('::1', 80), timeout=10, retries=2
2014-05-14 15:41:54 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge bridge._validation:671 connection exception
Traceback (most recent call last):
  File "/tmp/ovirt-c3oAOVstQK/otopi-plugins/ovirt-host-deploy/vdsm/bridge.py", line 666, in _validation
    retries=2,
  File "/tmp/ovirt-c3oAOVstQK/otopi-plugins/ovirt-host-deploy/vdsm/bridge.py", line 223, in _waitForRoute
    errno = s.connect_ex(host)
  File "<string>", line 1, in connect_ex
gaierror: [Errno -9] Address family for hostname not supported
2014-05-14 15:41:54 DEBUG otopi.context context._executeMethod:152 method exception
Traceback (most recent call last):
  File "/tmp/ovirt-c3oAOVstQK/pythonlib/otopi/context.py", line 142, in _executeMethod
    method['method']()
  File "/tmp/ovirt-c3oAOVstQK/otopi-plugins/ovirt-host-deploy/vdsm/bridge.py", line 680, in _validation
    addresses=addresses,
RuntimeError: Cannot connect engine host 'localhost' at any of the addresses set(['127.0.0.1', '::1'])'
2014-05-14 15:41:54 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Setup validation': Cannot connect engine host 'localhost' at any of the addresses set(['127.0.0.1', '::1'])'
2014-05-14 15:41:54 DEBUG otopi.context context.dumpEnvironment:468 ENVIRONMENT DUMP - BEGIN
2014-05-14 15:41:54 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/error=bool:'True'
2014-05-14 15:41:54 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError("Cannot connect engine host 'localhost' at any of the addresses set(['127.0.0.1', '::1'])'",), <traceback object at 0x2506e18>)]'
2014-05-14 15:41:54 DEBUG otopi.context context.dumpEnvironment:482 ENVIRONMENT DUMP - END

Comment 1 Alon Bar-Lev 2014-05-14 20:37:43 UTC
Your ENGINE_FQDN at engine side is probably localhost, which does not allow the host to check network connectivity after management bridge is created.

Please checkout the:
/etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf

Modify the ENGINE_FQDN to resolvable name of engine.

Restart ovirt-engine service.

Comment 2 GenadiC 2014-05-15 05:29:45 UTC
Alon, you were absolutely right,After updating in 10-setup-protocols.conf ENGINE_FQDN field, the problem was solved.
The question that I have why it worked for DC/Cluster in 3.4?
I guess the 10-setup-protocols.conf is not checked in 3.4 version, why?

Comment 3 Alon Bar-Lev 2014-05-15 06:13:47 UTC
(In reply to GenadiC from comment #2)
> Alon, you were absolutely right,After updating in 10-setup-protocols.conf
> ENGINE_FQDN field, the problem was solved.
> The question that I have why it worked for DC/Cluster in 3.4?
> I guess the 10-setup-protocols.conf is not checked in 3.4 version, why?

Because in >=3.3 the engine is responsible to create the management bridge post host-deploy phase which is much simpler and safer.