On Thu, Nov 29, 2012 at 11:10 AM, Jeremy Custenborder < [email protected]> wrote:
> Hello all, > > I'm using version 3.0.1 with puppetdb and so far it's been great. Good job > on reducing catalog compile times. The only problem I'm running into > is decommissioning a node. Before I would just run this : > > puppet node clean <hostname> > > This would remove the node from store configs. I would then delete my > nagios config and let puppet regenerate it. Now that I'm using puppetdb how > should I go about removing a decommissioned node? Is this just an oversight > or is there a different mechanism going forward. > > You need to use the "node deactivate" command: http://docs.puppetlabs.com/puppetdb/1/maintain_and_tune.html#deactivate-decommissioned-nodes There is a ticket around getting "puppet node clean" to work with PuppetDB: http://projects.puppetlabs.com/issues/14721 It's currently blocked on upstream work in puppet proper, though we hope to get to that soon. deepak -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
