Hi Greg,
I wasn't sure about them, here they are:
# tree /etc/puppetlabs/code/environments -d -L 3
/etc/puppetlabs/code/environments
├── common
│ ├── accounts
│ │ ├── files
│ │ ├── lib
│ │ ├── manifests
│ │ ├── spec
│ │ └── templates
│ ├── apache
│ │ ├── files
│ │ ├── manifests
│ │ └── templates
│ ├── apt
│ │ ├── lib
│ │ ├── manifests
│ │ ├── spec
│ │ ├── templates
│ │ └── tests
│ ├── stdlib
│ │ ├── examples
│ │ ├── lib
│ │ ├── manifests
│ │ └── spec
│ ├── tests
│ │ ├── manifests
│ │ └── templates
│ ├── timezone
│ │ ├── manifests
│ │ ├── spec
│ │ └── tests
│ ├── vscrepo
│ │ ├── examples
│ │ ├── lib
│ │ └── spec
│ └── yum
│ ├── manifests
│ ├── spec
│ └── tests
├── development
│ ├── manifests
│ └── modules
└── production
puppet.conf:
# cat /etc/puppetlabs/puppet/puppet.conf
### File managed with puppet ###
## Module: 'puppet'
[main]
# Where Puppet's general dynamic and/or growing data is kept
vardir = /opt/puppetlabs/puppet/cache
# The Puppet log directory.
# The default value is '$vardir/log'.
logdir = /var/log/puppetlabs/puppet
# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
rundir = /var/run/puppetlabs
# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = /etc/puppetlabs/puppet/ssl
# Allow services in the 'puppet' group to access key (Foreman + proxy)
privatekeydir = $ssldir/private_keys { group = service }
hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
show_diff = false
log_level = debug
## Server config
reports = foreman,puppetdb
environmentpath = /etc/puppetlabs/code/environments
basemodulepath = /etc/puppetlabs/code/environments/common:/etc/
puppetlabs/code/modules:/usr/share/puppet/modules
hiera_config = $confdir/hiera.yaml
### Next part of the file is managed by a different template ###
## Module: 'puppet'
[agent]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuration. Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is '$statedir/classes.txt'.
classfile = $statedir/classes.txt
# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig
# Disable the default schedules as they cause continual skipped
# resources to be displayed in Foreman - only for Puppet >= 3.4
default_schedules = false
report = true
pluginsync = true
masterport = 8140
# environment = production
certname = foreman-01.my.domain
server = foreman.my.domain
listen = false
splay = false
splaylimit = 1800
runinterval = 1800
noop = false
usecacheonfailure = true
ca_server = puppetca.my.domain
### Next part of the file is managed by a different template ###
## Module: 'puppet'
[master]
# autosign = /etc/puppetlabs/puppet/autosign.conf { mode = 0664 }
external_nodes = /etc/puppetlabs/puppet/node.rb
node_terminus = exec
ca = false
ssldir = /etc/puppetlabs/puppet/ssl
certname = foreman-01.my.domain
parser = current
ca_server = puppetca.my.domain
strict_variables = false
# pluginsync = true
storeconfigs = true
storeconfigs_backend = puppetdb
log_level = debug
reports = foreman
# environmentpath=/etc/puppetlabs/code/environments
Op maandag 17 oktober 2016 10:04:11 UTC+2 schreef Greg Sutcliffe:
>
> It's hard to say what might be happening without seeing the structure. Can
> you share your puppet.conf on the master, and the output of "tree
> /etc/puppetlabs/code/environments -d -L 3"?
>
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
