Project

General

Profile

Actions
Copy link

Bug #17634

closed

Puppet4 vardir and Upgrading from Puppet3

Added by Martin Schurz over 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Martin Schurz
Category:
Foreman modules
Target version:
1.14.1
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/puppet-puppet/pull/468
Fixed in Releases:
Found in Releases:
Foreman - 1.13.2
Red Hat JIRA:

Description

Last Week we did an update from Puppet3 to Puppet4 in one of our environments. We used you documentation: http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4

We had two possible issues after the update.

1.

We discovered, that in step 2 it would be good to add an additional option to the foreman-installer.

"--reset-puppet-server-puppetserver-vardir"

Can I update the documentation in your wiki?

2.

This is related to (1). We are using "puppet master --compile ..." to generate some reports on the puppet master. Since Puppet 4 the master and agent use a different vardir. In the default installation it is no longer possible to execute this command, because the puppet process is trying to geht cached facts etc. from the agent vardir. We had to add this to our puppet.conf:

[master]
...
    vardir = /opt/puppetlabs/server/data/puppetserver

This should be done by the foreman-installer itself when installing Puppet 4.

Actions
Copy link

Also available in: Atom PDF