We are using Foreman 3.19.1 / Katello 4.21.0 and our hosts are registered using FQDN.
However, if we change the setting under Administer→Settings→General→Display FQDN for hosts to No, Remote Execution jobs fail to find the target hosts depending on how the job is initiated:
-
Via the “All Hosts” page (New UI):
Selecting a host and clicking Schedule a job works perfectly. The UI generates a search filter using the numeric host ID (e.g.,id ^ (276)) which does not depend on the FQDN/non-FQDN setting. -
Via the individual Host Details page:
Clicking into a specific server and then clicking Schedule a job fails. Instead of using the numeric ID, this page generates a search filter using the short hostname. Because the host is registered via FQDN, the search returns “Apply to 0 hosts”. -
Via the Old UI (All Hosts page):
Testing with the legacy UI enabled makes the things worse; now it cannot run the job even from the All Hosts page, yielding 0 target hosts.
This looks like a bug to me. Has anyone else encountered this, or is there a known tracking issue for it?