Hi Folks,
OK, so I digested node classification documentation to ensure my nodes
attempts can be classified using the correct node definitions as below:
puppet.master # vi /etc/puppet/manifests/site.pp
# site.pp file.
-- sof --
node default {
}
node 'chat.client.com', 'puppet.master.com' { # applies to puppet-client
and puppet-master nodes
file {'/tmp/dns': # resource type file and filename
ensure => present, # make sure it exists
mode => 0644,
content => "Only DNS servers get this file.\n",
}
}
-- eof --
Then restarted the Puppet Master and run "puppet master --verbose
--no-daemonize". Even tried this "puppet master --compile
chat.client.com", still nothing triggers catalogs for my node
"chat.client.com".
puppet.master # puppet apply site.pp --noop
Notice: Compiled catalog for puppet.master.com in environment production in
0.16 seconds << no joy >>
Notice: /Stage[main]/Main/Node[puppet]/File[/tmp/dns]/ensure: current_value
absent, should be present (noop)
Notice: Node[puppet]: Would have triggered 'refresh' from 1 events
Notice: Class[Main]: Would have triggered 'refresh' from 1 events
Notice: Stage[main]: Would have triggered 'refresh' from 1 events
Notice: Finished catalog run in 0.09 seconds
puppet.master # puppet apply site.pp
Notice: Compiled catalog for puppet.master.com in environment production in
0.17 seconds
Notice: /Stage[main]/Main/Node[puppet]/File[/tmp/dns]/ensure: created
Notice: Finished catalog run in 0.13 seconds
puppet.master # cat /tmp/dns
Only DNS servers get this file.
puppet.master # vi /etc/puppet/manifests/site.pp
Why does this only trigger on the master if I have two nodes declared ? in
the site.pp file. Is there method to force a creation for nodes catalogs.
I tried this on the master but nothing of interest below:
# puppet master --compile chat.client.com
{
"document_type": "Catalog",
"data": {
"resources": [
{
"tags": ["stage"],
"type": "Stage",
"parameters": {
"name": "main"
},
"exported": false,
"title": "main"
},
{
"tags": ["class","settings"],
"type": "Class",
"exported": false,
"title": "Settings"
},
{
"tags": ["class"],
"type": "Class",
"parameters": {
"name": "main"
},
"exported": false,
"title": "main"
}
],
"tags": ["settings"],
"classes": [
"settings"
],
"version": 1440708265,
"edges": [
{
"target": "Class[Settings]",
"source": "Stage[main]"
},
{
"target": "Class[main]",
"source": "Stage[main]"
}
],
"environment": "production",
"name": "chat.client.com"
},
"metadata": {
"api_version": 1
}
}
TIA.
On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote:
>
> Hi I Setup a Open Source Puppet Master and a Puppet Agent client on Linux
> CentOS release 6.6, Puppet 3.8.1 on two separate servers.
>
> Have successfully setup communications between both servers (cert
> list/sign/fingerprint etc etc and telnet 8140, disabled SELinux and added
> iptables 8140 rule) and I have created and run "puppet apply site.pp"
> node.pp and a init.pp/class no errors.
>
> Thus run "puppet master --verbose --no-daemonize" on the PM and "puppet
> agent -t --debug" on the client and I do not receive any errors when I run
> # puppet apply site.pp or node.pp etc or see any issues when I run tail on
> the masterhttp.log file.
>
> Test files specified in site.pp and node.pp are created on the Puppet
> Master but do not replicate to the Node ?
>
> Puppet node does not pick any changes from master's catalogs when I
> forcibly restart puppet client or run puppet agent instead of waiting 30
> mins, even though the "Info: Applying configuration version '1440626773'"
> number changes accordingly. Further information below:
>
> # puppet master --verbose --no-daemonize
>
> Info: access[/file_metadata]: adding authentication any
> Info: Inserting default '/status' (auth true) ACL
> Info: Caching node for chat.client.com
> Info: Caching node for chat.client.com
> Notice: Compiled catalog for chat.client.com in environment production in
> 0.04 seconds
>
> # puppet agent -t --debug
>
> Debug: Creating default schedules
> Debug: Loaded state in 0.00 seconds
> Info: Applying configuration version '1440626773' < changes >
> Debug: Finishing transaction 69904202860300
> Debug: Storing state
> Debug: Stored state in 0.03 seconds
> Notice: Finished catalog run in 0.13 seconds
> Debug: Using cached connection for https://puppet.master.com:8140
> Debug: Caching connection for https://puppet.master.com:8140
> Debug: Closing connection for https://puppet.master.com:8140
>
> Any help or advice to troubleshoot on why Puppet node does not pull any
> changes from master's site.pp and node.pp manifest. I'm ignoring the Module
> classes I have created for now.
>
> Cheers,
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/17c06adb-b482-4628-a198-34f701552c9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
