Hi there,
thanks for coming back to me.
Yesterday when I was trying to find out what’s going on I have found some info about separate step to upgrade puppet post install/upgrade of Foreman… So I decided to give it a go…
foreman-installer --upgrade-puppet
…
Resolving Dependencies
→ Running transaction check
—> Package puppetserver.noarch 0:2.8.0-1.el7 will be updated
—> Package puppetserver.noarch 0:5.1.4-1.el7 will be an update
→ Processing Dependency: puppet-agent >= 4.99.0 for package: puppetserver-5.1.4-1.el7.noarch
→ Running transaction check
—> Package puppet-agent.x86_64 0:1.10.9-1.el7 will be updated
—> Package puppet-agent.x86_64 0:5.3.3-1.el7 will be an update
→ Finished Dependency Resolution
…
Puppet 4 to 5 upgrade param reset, continuing with installation
Installing Done [100%] […]
Success!
after
cat /etc/foreman-proxy/settings.d/puppet.yml --- # Puppet management :enabled: https # valid providers: # puppet_proxy_puppetrun (for puppetrun/kick, deprecated in Puppet 3) # puppet_proxy_mcollective (uses mco puppet) # puppet_proxy_ssh (run puppet over ssh) # puppet_proxy_salt (uses salt puppet.run) # puppet_proxy_customrun (calls a custom command with args) #:use_provider: puppet_proxy_puppetrun :puppet_version: 5.3.3
Although still same problem persisted…
Then I have created /etc/puppet/autosign.conf file with correct permissions and ownership info and - tada, it’s working now…
Another Question:
Now I am wondering - what’s the best way to register/handle new VMs. How do I ensure that newly deployed VMs will:
- have puppet installed and configured
- be registered as content hosts in foreman/katello
Should this be done on a template level and then they will re-register when deployed with new hostnames? Or should this be done somehow as a step/part of deployment?
Thank you in advance
Tomasz