大网数据广告活动
服务器运维问答

Different manifest location on Puppet Server/Agent

· 52CE 我爱测

My Puppet Server Environment setting is as follows [master] vardir = /opt/puppetlabs/server/data/puppetserver logdir = /data/log/puppetlabs/puppetserver rundir = /var/run/puppetlabs/puppetserver pidfile = /var/run/puppetlabs/pupp…

问题原文

原帖链接 · Zama Ques · CC BY-SA 3.0

My Puppet Server Environment setting is as follows

[master]
vardir = /opt/puppetlabs/server/data/puppetserver
logdir = /data/log/puppetlabs/puppetserver
rundir = /var/run/puppetlabs/puppetserver
pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
codedir = /data/puppetlabs/code

#  puppet master --configprint manifest
/data/puppetlabs/code/environments/production/manifests

On Agents it is as follows

server = jw-host
environment = production

But --configprint is showing a different location on agent nodes

# puppet master --configprint manifest
/etc/puppetlabs/code/environments/production/manifests

It is not getting changed to /data because of which my manifests are not getting applied .

Versions are as follows

 # puppetserver  --version
  puppetserver version: 2.4.0
 # puppet  --version
  4.5.2

What is the issue here ?

已采纳解答

原帖链接 · faker · CC BY-SA 3.0

From what I understand the puppet master --configprint checks locally which settings a puppet server would use.
It does not connect to the configured master and get the value from it.

As you are not running a puppet server on the agent this setting is not relevant.
It is simply defaulting to /etc/puppetlabs/code/environments/production/manifests when it's not set at all.
But it's anyway not used by the agent.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-06-30)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。