On Sunday, November 25, 2012 11:57:36 PM UTC-6, go8ose wrote:
>
> I've got an exported exec that looks like:
>
> 38 @@exec { "commvault_subclient_$hostname":
> 39 command => "/usr/local/sbin/commvault_auto_subclient
> --touchstamp /srv/mnt/.$hostname_commvault_backed_up $hostname",
> 40 creates => "/srv/mnt/.$hostname_commvault_backed_up",
> 41 tag => "commvault_nfs_subclient"
> 42 }
>
> Elsewhere I've got some manifest to collect these:
>
> 90 # Collect the exec's that automatically setup commvault backups
> 91 Exec <<| tag == 'commvault_nfs_subclient' |>>
> 92
>
>
> But on the host that has that collection, I'm not seeing the resulting
> script run (which creates the file mentioned as the --touchstamp
> argument). It's like the collection is silently failing.
>
> I'm not sure how to debug this. Other exported resources are working,
> I'm successfully doing:
> @@nagios_host { $hostname:
> address => $ipaddress,
> use => 'linux-host',
> alias => $hostname,
> }
> @@nagios_service { "$hostname-ping":
> use => 'alive-service',
> host_name => $hostname,
> }
>
> And collecting them with:
> Nagios_service <<| |>>
> Nagios_host <<| |>>
>
> I'm also seeing in my mysql database entries in the 'resources' table
> that have restype='Exec' and have a title like
> commvault_subclient_webapp01.
>
> I'm running puppet 2.6.2 on the master and the involved clients. Any
> suggestions?
>
>
This looks like http://projects.puppetlabs.com/issues/11049. You can vote
for that issue. To work around the it, I think you'll need to arrange for
the host that collects those resources to declare its own nagios_service
and nagios_host resources as ordinary instead of exported resources. Of
course, that's a bust if more than one node needs to collect those
resources.
There are probably other workarounds, but they depend on details of your
site. Many of them involve substituting something else for exported
resources; the rest involve collecting onto a node that does not export
(and therefore is not affected by the bug), and then sharing the result
somehow.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/MG_5-Jtrp4EJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
