Default Hostgroup not matching on any custom facts, always hits default

Support
#1

Problem:
Using the default hostgroup plugin to put nodes in hostgroups based on a custom fact. However, the fact value is never matched by the plugin and the default ‘catch all’ option is always used.
Expected outcome:
The plugin would match the custom fact and apply the corresponding hostgroup/environment to that node
Foreman and Proxy versions:
foreman-1.20.2-1.el7.noarch
foreman-proxy-1.20.2-1.el7.noarch
Foreman and Proxy plugin versions:
tfm-rubygem-foreman_default_hostgroup-5.0.0-3.fm1_20.el7.noarch

Other relevant data:
I’ve set the “force_hostgroup_match_only_new” to no and “force_hostgroup_match” to yes in the UI and restarted foreman and httpd.

[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)

2019-04-16T14:41:14 [I|app|3cfc7] Processing by Api::V2::HostsController#facts as JSON
2019-04-16T14:41:14 [I|app|3cfc7]   Parameters: {"facts"=>"[FILTERED]", "name"=>"ticemp1-ll1.jhuapl.edu", "certname"=>"ticemp1-ll1.jhuapl.edu", "apiv"=>"v2", "host"=>{"certname"=>"ticemp1-ll1.jhuapl.edu", "name"=>"ticemp1-ll1.jhuapl.edu"}}
2019-04-16T14:41:15 [I|app|3cfc7] Import facts for 'ticemp1-ll1.jhuapl.edu' completed. Added: 0, Updated: 21, Deleted 0 facts
2019-04-16T14:41:15 [I|app|3cfc7] Fact = apl_env
2019-04-16T14:41:15 [I|app|3cfc7] Regex = dare
2019-04-16T14:41:15 [I|app|3cfc7] Fact = apl_env
2019-04-16T14:41:15 [I|app|3cfc7] Regex = MyAPLCloud-dmz
2019-04-16T14:41:15 [I|app|3cfc7] Fact = apl_env
2019-04-16T14:41:15 [I|app|3cfc7] Regex = MyAPLCloud
2019-04-16T14:41:15 [I|app|3cfc7] Fact = apl_env
2019-04-16T14:41:15 [I|app|3cfc7] Regex = Opt-in
2019-04-16T14:41:15 [I|app|3cfc7] Fact = apl_env
2019-04-16T14:41:15 [I|app|3cfc7] Regex = dev
2019-04-16T14:41:15 [I|app|3cfc7] Fact = apl_env
2019-04-16T14:41:15 [I|app|3cfc7] Regex = test
2019-04-16T14:41:16 [I|app|3cfc7] Fact = hostname
2019-04-16T14:41:16 [I|app|3cfc7] Regex = .*
2019-04-16T14:41:16 [I|app|3cfc7] DefaultHostgroupMatch: ticemp1-ll1.jhuapl.edu added to default
2019-04-16T14:41:16 [I|app|3cfc7] Completed 201 Created in 1887ms (Views: 3.4ms | ActiveRecord: 546.7ms)

When I do a ‘facter apl_env’ on the node:
[root@ticemp1-ll1 ~]# facter apl_env
test

Yet this host (and other hosts I’ve tried always catch the ‘default’ option, here’s the config:

---
:default_hostgroup:
  :facts_map:
    "DARE":
      "apl_env": "dare"
    "default/MyAPLCloud-dmz":
      "apl_env": "MyAPLCloud-dmz"
    "default/MyAPLCloud":
      "apl_env": "MyAPLCloud"
    "default/Opt-in":
      "apl_env": "Opt-in"
    "default-dev":
      "apl_env": "dev"
    "default-test":
      "apl_env": "test"
    "default":
      "hostname": ".*"

If you need more information let me know. Thanks.

#2

For more information, I set this ‘apl_env’ fact by creating a yaml file in /opt/puppetlabs/facter/facts.d/
It seems that I can match correctly on other core facts such as hostname or ipaddress.

#3

Does this external fact show up in Forman for the host in question once it’s checked in?

#4

Also what’s the output of puppet facts apl_env

#5

This fact used to show up (I was using Foreman 1.19.1) but when I upgraded everything it stopped showing up in foreman.

The output of the command shows all the facts, but does contain apl_env:
[root@ticemp1-ll1 ~]# puppet facts apl_env
{
“name”: “apl_env”,
“values”: {
“aio_agent_version”: “5.5.13”,
“apl_env”: “test”,
“architecture”: “x86_64”,
“augeas”: {
“version”: “1.11.0”
},

#6

So foreman not knowing about your external facts will be the reason the match is not happening.

If puppet knows about the fact locally on the node then we need to work out if they are not being reported to the puppetmaster or node.rb is not uploading them to foreman. I don’t know of any mechanism by which external facts would be filtered out intentionally.

Is there anything of interest in the puppetmaster foreman proxy logs when the client checks in?

#7

Unfortunately there’s nothing useful in the foreman-proxy logs.

#8

Did you find the solution for it? I am using the same version and getting same issue. Default facts are working whereas custom facts are not working with this plugin.

Fact value is also getting imported into foreman but still default hostgroup is unable to update that.

Below is my default hostgroup rules.

:default_hostgroup:
:facts_map:
“Noida_AllHost”:
“foreman_location”: “Noida”
“Redhat”:
“osfamily”: “RedHat”
“lsbdistcodename”: “Santiago”
“Osx/Common”:
“osfamily”: “Darwin”
“Base”:
“hostname”: “.*”

Client host is getting the fact value as below:

[root@rhel6dev ~]# puppet facts foreman_location | grep foreman_location
“name”: “foreman_location”,
“foreman_location”: “Noida”,
[root@rhel6dev ~]#

Image of forman portal which showing the fact value for the host:

image
image1581×253 23.1 KB

But when i am running puppet agent on this client host then its assigning it to “Base” hostgroup not in “Noida_AllHost”

Both the hostgroup i have already created in Foreman.

Please help to fix it.

#9

Hi Support,

Could you please update here?