Bug 1581384

Summary:	With remote_execution_connect_by_ip on, the reports are assigned to host named as ip, instead of the correct host name
Product:	Red Hat Satellite	Reporter:	Ivan Necas <inecas>
Component:	Ansible - Configuration Management	Assignee:	Daniel Lobato Garcia <dlobatog>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	dlobatog, mhulan, pcreech
Target Milestone:	6.4.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman_ansible-2.2.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 19:05:44 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 Ivan Necas 2018-05-22 15:33:03 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. set remote_execution_connect_by_ip to true
2. run ansible job
3. search for reports at the host

Actual results:
no reports found for the host, new host created with the name of the ip, with the reports assigned

Expected results:
The original host gets the reports assigned


Additional info:

Comment 4 Daniel Lobato Garcia 2018-05-30 13:42:03 UTC

Created redmine issue http://projects.theforeman.org/issues/23741 from this bug

Comment 5 Satellite Program 2018-07-12 08:04:26 UTC

Upstream bug assigned to dlobatog

Comment 6 Satellite Program 2018-07-12 08:04:29 UTC

Upstream bug assigned to dlobatog

Comment 7 Martin Korbel 2018-07-26 09:08:50 UTC

VERIFIED on Sat6.4#13

reproducer via comment #0

Comment 9 Bryan Kearney 2018-10-16 19:05:44 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927