Wyatt, We implemented the code to make these facts be nothing. We can see it working on nodes that are small, and it worked in our test environment. However, we still have the issue that it cannot replace facts as PuppetDB still chokes on emptying the facts for the nodes with large facts. I tried to deactivating a node, but it still exists in the DB obviously until GC happens (a week for me). This is too long. Is there a query I can run to wipe out all these facts in the PuppetDB? I don't care about them anyway. Thanks again in advance.
Mike On Tuesday, April 19, 2016 at 10:49:27 PM UTC-5, Wyatt Alt wrote: > > > > On 04/19/2016 10:39 AM, Mike Sharpton wrote: > > Again,* thank you* very much. If I could buy you a beer, I would. The > machines in question are a mix of RHEL5/6/7. > > Hah, you're very welcome. Thanks for confirming the OS; that means this > isn't just a Solaris issue like that facter ticket suggests. > > -- 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/d20f930b-96da-4fc4-80d7-c432b3552eb4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
