Bug #17634

Puppet4 vardir and Upgrading from Puppet3

Added by Martin Schurz 8 months ago. Updated 8 months ago.

Status:Closed
Priority:Normal
Assigned To:Martin Schurz
Category:Foreman modules
Target version:-
Difficulty: Bugzilla link:
Found in release:1.13.2 Pull request:https://github.com/theforeman/puppet-puppet/pull/468
Story points-
Velocity based estimate-
Release1.14.1Release relationshipAuto

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.

History

#1 Updated by Dominic Cleal 8 months ago

1. Please feel free to edit the wiki.

2. This is entirely separate from the documentation, it should be filed as an issue in the installer project, not a support ticket. Do you want me to change this ticket, or do you intend to file a specific bug report?

#2 Updated by Martin Schurz 8 months ago

Dominic Cleal wrote:

1. Please feel free to edit the wiki.

2. This is entirely separate from the documentation, it should be filed as an issue in the installer project, not a support ticket. Do you want me to change this ticket, or do you intend to file a specific bug report?

Ok I will update the wiki. Can you change the ticket? I will try to provide a patch. From what I've seen this sould be trivial.

#3 Updated by Michael Moll 8 months ago

  • Tracker changed from Support to Bug
  • Project changed from Foreman to Installer
  • Category changed from Settings to Foreman modules

#4 Updated by Martin Schurz 8 months ago

  • Pull request https://github.com/theforeman/puppet-puppet/pull/468 added

#5 Updated by Martin Schurz 8 months ago

Hi Michael,

just one short question.
The PR for the puppet Module was merged a few days ago. Will the fix be in the next version of foreman-installer or is there something that needs to be done to update the dependency?

#6 Updated by Michael Moll 8 months ago

It'll be part of Foreman 1.15 per default and I'll leave the decision to Dominic if it's going to be part of the branched releases.

Personally I'm not 100% sure, but think the whole "puppet master" thing is marked deprecated in Puppet 4.x and will be gone in 5.x (or maybe even sooner), so it's probably a good idea to move away from using that. But ask Puppetlabs about the things you're specifically using, if you need 100% confidence.

#7 Updated by Dominic Cleal 8 months ago

  • Status changed from New to Resolved

We can see about including it in a patch release, e.g. 1.14.1.

#8 Updated by Dominic Cleal 8 months ago

  • Status changed from Resolved to Closed
  • Assigned To set to Martin Schurz
  • Release set to 1.14.1

Also available in: Atom PDF