Multiple hosts created when saltstack minion_id differs from FQDN.
We have minion_ids that are frequently just the uppercase version of the first part of the hostname. When a minion_id is the FQDN, it seems that all information comes through into the foreman host list. When using the partial hostname, or one that doesn't match the FQDN, we don't see the OS/OS release info or the Model info (such as VMWare). This does come through when we use the FQDN. The state.highstate report info seems to come through no matter whether the minion_id matches the FQDN or not. With the single part hostname, regardless of whether the minion_id is upper or lower case.
Can this be remedied to support full functionality even when the salt minion_id doesn't match the host's FQDN?
We use saltstack with foreman and the smart proxy.
Installed via rpm:
(on Foreman host)
(On salt master, which is different from foreman host)
#2 Updated by Stephen Benjamin about 5 years ago
- Subject changed from OS/release information not gathered when saltstack minion_id differs from FQDN. to Multiple hosts created when saltstack minion_id differs from FQDN.
Another user reported this as well, and there's lots of odd behavior when a minion id differs from the FQDN.
Not sure how easy it is to fix, because the SaltStack reports contain the minion ID in the report name:
There's no way to get the FQDN AFAIK from the saltstack report. Maybe we can add a minion id to the host
and match up reports/grains that way.
#8 Updated by Mihai Cindea over 1 year ago
For anyone who is still having this issue:
While trying to craft a patch for report_importer.rb I realized that actually this is solvable just by setting "Append domain names to the host" to "No" in Settings in Foreman UI
Feel free to poke me if you have any issues.