Config_group fact missing?

Support
1

Hi,

I can't seem to use/find the config_group fact (for puppet) in 1.12
anymore. Did I miss something? I saw the bug fix in 1.12.3 for sorting by
config_group and hostgroup, but that seemed unrelated to this.

I've looked at Foreman :: Manual
, the last part talks about looking at the "yaml" page for a host. I would
have expected to find a fact called "config_group" in there, just like the
"hostgroup" fact. A host that has a config group assigned to its hostgroup
looks like this (edited to remove identifying company data):

··· --- classes: (classes from the CG go here) parameters: puppetmaster: $puppetmaster_fqdn domainname: domain.com hostgroup: my/hostgroup location: USA organization: MyOrg root_pw: puppet_ca: $puppetmaster_fqdn foreman_env: $my_env owner_name: Admin User owner_email: root@domain.com foreman_subnets: [] foreman_interfaces: - ip: 192.168.100.115 mac: 00:50:56:74:17:70 name: $hostname.fqdn attrs: mtu: '1500' network: 192.168.100.0 netmask: 255.255.254.0 virtual: false link: true identifier: eth0 managed: true primary: true provision: true subnet: tag: attached_to: type: Interface environment: $my_env

Am I missing something? What else should I look at? The DB doesn’t seem to have this fact in it either.

Thanks for any suggestions.

-Chris

2

Hello

please see answers below in text

> Hi,
>
> I can't seem to use/find the config_group fact (for puppet) in 1.12
> anymore. Did I miss something? I saw the bug fix in 1.12.3 for sorting by
> config_group and hostgroup, but that seemed unrelated to this.

I don't remember we'd have config groups information available in puppet
before.

> I've looked at Foreman :: Manual
> , the last part talks about looking at the "yaml" page for a host. I would
> have expected to find a fact called "config_group" in there, just like the
> "hostgroup" fact. A host that has a config group assigned to its hostgroup
> looks like this (edited to remove identifying company data):

Others asked the same thing [1] and it was recently implemented. It's aligned
with 1.14 so you'll have to wait ~4 months for this version to be released, if
you want you can install Foreman nightly which already contains the patch.
Also one thing to notice, it won't be called config_groups but it's prefixed so
the name will be foreman_config_groups to avoid potential conflicts.

[1] Feature #12535: Expose config groups list in host yaml - Foreman

Hope this helps

··· On Wednesday 28 of September 2016 15:18:35 Chris Baldwin wrote:

–
Marek

classes:
(classes from the CG go here)
parameters:
puppetmaster: $puppetmaster_fqdn
domainname: domain.com
hostgroup: my/hostgroup
location: USA
organization: MyOrg
root_pw:
puppet_ca: $puppetmaster_fqdn
foreman_env: $my_env
owner_name: Admin User
owner_email: root@domain.com
foreman_subnets: []
foreman_interfaces:

  • ip: 192.168.100.115
    mac: 00:50:56:74:17:70
    name: $hostname.fqdn
    attrs:
    mtu: '1500’
    network: 192.168.100.0
    netmask: 255.255.254.0
    virtual: false
    link: true
    identifier: eth0
    managed: true
    primary: true
    provision: true
    subnet:
    tag:
    attached_to:
    type: Interface
    environment: $my_env

Am I missing something? What else should I look at? The DB doesn’t seem to
have this fact in it either.

Thanks for any suggestions.

-Chris

3

Thanks. Looks like I misunderstood what was available. I'm looking forward
to 1.14!

··· On Wednesday, September 28, 2016 at 6:18:35 PM UTC-4, Chris Baldwin wrote: > > Hi, > > I can't seem to use/find the config_group fact (for puppet) in 1.12 > anymore. Did I miss something? I saw the bug fix in 1.12.3 for sorting by > config_group and hostgroup, but that seemed unrelated to this. > > I've looked at https://theforeman.org/manuals/1.12/index.html#4.2.2Classes > , the last part talks about looking at the "yaml" page for a host. I would > have expected to find a fact called "config_group" in there, just like the > "hostgroup" fact. A host that has a config group assigned to its hostgroup > looks like this (edited to remove identifying company data): > > --- > classes: > (classes from the CG go here) > parameters: > puppetmaster: $puppetmaster_fqdn > domainname: domain.com > hostgroup: my/hostgroup > location: USA > organization: MyOrg > root_pw: > puppet_ca: $puppetmaster_fqdn > foreman_env: $my_env > owner_name: Admin User > owner_email: root@domain.com > foreman_subnets: [] > foreman_interfaces: > - ip: 192.168.100.115 > mac: 00:50:56:74:17:70 > name: $hostname.fqdn > attrs: > mtu: '1500' > network: 192.168.100.0 > netmask: 255.255.254.0 > virtual: false > link: true > identifier: eth0 > managed: true > primary: true > provision: true > subnet: > tag: > attached_to: > type: Interface > environment: $my_env > > > Am I missing something? What else should I look at? The DB doesn't seem to have this fact in it either. > > > Thanks for any suggestions. > > -Chris > >