Bug 1996018

Summary:	redhat.satellite.host requires FQDN and is incompatible with append_domain_name_for_hosts false
Product:	Red Hat Satellite	Reporter:	Ahmed Eladawy <aeladawy>
Component:	Ansible Collection	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	egolov, jpathan, momran, satellite6-bugs, tris.hoar
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused	Flags:	momran: needinfo? (satellite6-bugs)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1992583	Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1992583
Bug Blocks:

Description Ahmed Eladawy 2021-08-20 10:25:25 UTC

+++ This bug was initially created as a clone of Bug #1992583 +++

Description of problem:
The module enforces having '.'s in the name of the hosts (lines 460-461 in plugins/modules/host.py) This is incompatible if you set your satellite to use append_domain_name_for_hosts false

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


How reproducible:
Always

Steps to Reproduce:
1. Set append_domain_name_for_hosts false in Administrator -> Settings -> General on satellite
2. Register host
3. Try to update host using module

Actual results:
Module will not be able to match name of the host


Expected results:
Module to update host

Additional info:
Worked arround by commenting lines 460-461

Comment 4 Evgeni Golov 2022-05-12 08:51:00 UTC

*** Bug 1992583 has been marked as a duplicate of this bug. ***

Comment 9 Brad Buckingham 2023-03-06 11:38:36 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 10 Marek Hulan 2023-03-06 12:50:51 UTC

We are not closing this one as we're progressing on changing the behavior. The setting will only affect the way we display the information, but internally we'll always store FQDN. That way, it will be compatible with other inventories (AAP, Insights etc). I have prevented the automation to close this BZ.