forked from glarizza/puppetlabs-puppet
-
Notifications
You must be signed in to change notification settings - Fork 60
Open
Description
I have just had a couple of hours debugging a strange problem in deploying a Puppetmaster (on RHEL7, with passenger compiled from gem).
As I finally found out, it does matter in which order I declare the puppet::master and puppet::agent classes, e.g. the following manifest doesn't get successfully applied
include puppet::agent
include puppetdb
class { 'puppet::master':
storeconfigs => true,
}whereas if I use the following variant, everything works as expected:
include puppetdb
class { 'puppet::master':
storeconfigs => true,
}
include puppet::agentThe reason is probably the use of the defined functions in manifests/agent.pp and manifests/master.pp, which is, as I understand now, parse-order dependent.
Metadata
Metadata
Assignees
Labels
No labels