Issue #14722 has been updated by Charlie Sharpsteen.
Redmine Issue [#14722](http://projects.puppetlabs.com/issues/14722) has been migrated to JIRA: <https://tickets.puppetlabs.com/browse/PDB-134> ---------------------------------------- Bug #14722: Purging resources that were exported resources sometimes fails https://projects.puppetlabs.com/issues/14722#change-101417 * Author: Jason Hancock * Status: Accepted * Priority: Normal * Assignee: Ken Barber * Category: * Target version: * Keywords: * Branch: * Affected PuppetDB version: 1.1.1 ---------------------------------------- I'm seeing an issue where sometimes I have an exported resource that is failing to be removed from the node that is collecting them after the node has been cleaned up by running a "puppet node clean <hostname>" on the puppetmaster. For example, I'm exporting both nagios_host and nagios_service resources from my nodes and collecting them on my nagios server. On the nagios server, I've set up resources of these types to be purged: <pre> resources { ['nagios_service', 'nagios_host']: purge => true, notify => Service['nagios'], } </pre> If I purge a node on the puppetmaster: <pre> puppet node clean node.example.com </pre> On the next puppet run on the nagios server, I might get the following error message: <pre> warning: /Nagios_service[node.example.com SSH]: Whit[Completed_stage[post]],Whit[Admissible_stage[post]],Whit[Admissible_stage[puppetcomplete]],Whit[Completed_stage[puppetcomplete]], Whit[Completed_stage[main]],Whit[Completed_class[Nagios]],Service[nagios] still depend on me -- not purging </pre> This doesn't happen all of the time, nor does it happen for all of the nagios_service resources for this node (other nagios_service resources get cleaned up just fine). I've seen this with both the nagios_host and the nagios_service type of resources. It will continue to occur for the same resource on any subsequent run of puppet on the nagios server. To remedy this, I have to manually remove the resource it is complaining about from the nagios configuration and restart the service (something I would like to avoid). Not sure if it matters or not, but I'm using PuppetDB as the stored configurations backend. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
