Project

General

Profile

Actions

Bug #11870

open

Multiple hosts created when saltstack minion_id differs from FQDN.

Added by Jim Dubinsky about 9 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Foreman Integration
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

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)
foreman-1.9.1-1.el7.noarch
ruby193-rubygem-foreman_salt-3.0.2-1.fm1_9.el7.noarch

(On salt master, which is different from foreman host)
salt-2015.5.3-4.el7.noarch
salt-minion-2015.5.3-4.el7.noarch
salt-master-2015.5.3-4.el7.noarch
salt-api-2015.5.3-4.el7.noarch
foreman-proxy-1.9.1-1.el7.noarch


Related issues 1 (0 open1 closed)

Has duplicate Salt - Bug #16156: Foreman Salt - duplication issueDuplicate08/17/2016Actions
Actions

Also available in: Atom PDF