Bug 1656480

Summary: ansible rex fails if /etc/ssh/ssh_config has ProxyCommand /usr/bin/sss_ssh_knownhostsproxy -p %p %h
Product: Red Hat Satellite Reporter: Peter Ondrejka <pondrejk>
Component: Ansible - Configuration ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: aruzicka, inecas, mhulan
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-07 13:40:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Ondrejka 2018-12-05 15:36:50 UTC 
Description of problem:

Running ansible remote execution fails with

fatal: [ip]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh_exchange_identification: Connection closed by remote host\r\n", "unreachable": true}
  16:
	to retry, use: --limit @/tmp/foreman-playbook-51438471-3a3c-4b2a-85d1-5270d8d28cdb.retry


This happends when /etc/ssh/ssh_config contains the line 
ProxyCommand /usr/bin/sss_ssh_knownhostsproxy -p %p %h

The line gets generated when sat server is added to a kerberos realm (quoting aruzicka :)). This affects robottelo automation, the workaround is to comment the line.

Version-Release number of selected component (if applicable):
Sat 6.5 snap 6

How reproducible:
always
Comment 4 Adam Ruzicka 2018-12-05 15:54:12 UTC 
Moving to Ansible component as regular ssh-based REX is not affected by this
Comment 5 Marek Hulan 2018-12-07 13:40:13 UTC 
Seems as a duplicate of BZ 1650103, please reopen if I missed something, copying Adams notes there too.

*** This bug has been marked as a duplicate of bug 1650103 ***