Feature #34388
closed
Allow puppet setup to be skipped even if you set a puppet master
Added by Daniel Henninger almost 3 years ago.
Updated over 2 years ago.
Description
Hi folk! In our environment, we use Foreman with Puppet but, we also make use of Ansible and AWX to set up Puppet in the first place. As such, I used modified Preseed and Kickstart provisioning/finish templates that allowed me to skip the puppet setup, even if I have the server and ca set in my host config. This issue will coincide with a PR to add that support upstream so I can ideally return to using the stock provisioning templates. Thanks! If you'd like some more details on WHY I've chosen to do it this way, I'm happy to tell the story so to speak, but I figured I'd keep this pretty short.
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/9086 added
- Pull request deleted (
https://github.com/theforeman/foreman/pull/9086)
Rejecting my own issue as a solution was provided in the PR that I am happy with. (basically it's ok to not set the Puppet Proxy for a host, doesn't hurt as much as I thought it did)
Ok.. apparently I can't reject it so.. whenever someone sees this, please cancel it.
- Pull request https://github.com/theforeman/foreman/pull/9086 added
Well turns out I may need this after all. I have opened the pull request and discussion is happening there.
Note I've found another albeit crappy workaround. I'd rather be able to explicitly skip puppet being configured and have it stay that way, but if y'all would prefer not to have that, it's not the end of the world. =)
- Fixed in Releases 3.3.0 added
- Status changed from Ready For Testing to Closed
- Assignee set to Ondřej Ezr
- Pull request https://github.com/theforeman/foreman/pull/9143 added
- Fixed in Releases 3.2.0 added
Also available in: Atom
PDF