Oh thanks, that worked. I guess I was confused with the semantics of 'clean' and 'deactivate' and thought 'deactivate' would... deactivate the node not just 'clean' out its virtual resources :)
It would be nice if there was a curl interface for puppetdb to delete specific virtual resources! So far as I can tell it doesn't work with -X DELETE at all. On Wednesday, August 5, 2015 at 11:28:49 AM UTC-7, Matthew Burgess wrote: > > On 5 Aug 2015 19:10, "Steve Wray" <st...@wtfast.com <javascript:>> wrote: > > > > I have a problem where a virtual resource has, in an early run, got the > wrong value. I've fixed the manifest so that the virtual resource gets the > correct values and I've rerun Puppet on the node that populates the virtual > resource. However when it is instantiated it still gets the old value. > > > > I've used 'puppet node clean' for both the node where the virtual > resource is created/populated and on the node where the virtual resource is > instantiated and its still coming in with the wrong value. > > > > If I drop the puppetdb database (its postgres) and rerun Puppet on both > sides the virtual resource gets the correct new values. > > > > This seems like a very extreme measure for an environment with many > nodes and many virtual resources, just to clean out one incorrect value. > > > > What is the correct way to fix this situation? > > Run > > puppet node deactivate agent-hostname > > on your master. That nullifies all exported resources for that host, which > then get repopulated on the next agent run. > > Matt. > -- 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/c9195c3b-6d1a-4c95-bbaf-ae47606e30af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
