Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #32457 - Register host & apply inherited attributes #8539

Merged
merged 1 commit into from Jun 1, 2021

Conversation

stejskalleos
Copy link
Contributor

No description provided.

@theforeman-bot
Copy link
Member

Issues: #32457

Copy link
Member

@ares ares left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @stejskalleos, works great, merging!

@ares ares merged commit e60069e into theforeman:develop Jun 1, 2021
@ares ares added the Needs cherrypick This should be cherrypicked to the stable branches or branches label Jun 1, 2021
@ares
Copy link
Member

ares commented Jun 1, 2021

This deserves 2.5 cherrypick I believe

tbrisker pushed a commit that referenced this pull request Jun 3, 2021
@tbrisker
Copy link
Member

tbrisker commented Jun 3, 2021

2.5 - 2303337

@ezr-ondrej ezr-ondrej removed the Needs cherrypick This should be cherrypicked to the stable branches or branches label Jun 15, 2021
@LiohMoeller
Copy link

This issue is still present on Foreman 3.5.1.

Steps to reproduce:

  • Create a Host Group
  • Select 'Puppet Proxy', 'Puppet CA' and 'Environment' from the relevant Pull-Down-Menus on the Host Group
  • Create a Global Registration Template associated with the newly created Host Group
  • Register a client using the Global Registration template

The client is registered, but Puppet Parameters from the Host Group are not adopted, leading to empty ‘Environment’ ‘Puppet Proxy’ and ‘Puppet CA Proxy’ on the host object and a puppet.conf on the client which looks like this:


[main]

[agent]
pluginsync      = true
report          = true
certname        = my.host.tld

The issue does not occur if the host object already exists and Puppet settings are defined on the host object.

A partial workaround, still leading to a non-functional result, is to define puppet_ca_server and puppet_server as Parameters on the hostgroup. In this case server and ca are written correctly, but environment not. Trying to set the host_puppet_environment parameter manually on the host group, still leads to the same result (variable empty)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants