----- Original Message ----- > From: "Felix Frank" <felix.fr...@alumni.tu-berlin.de> > To: puppet-users@googlegroups.com > Sent: Wednesday, June 20, 2012 9:03:48 AM > Subject: Re: [Puppet Users] facter plugin requires cause catalog failure, > prevent setting up new clients > > On 06/20/2012 01:34 AM, Jo Rhett wrote: > > > >> by bootstrap i mean kickstart or whatever, ie. before you run > >> puppet. > > > > I should have some other system that configures my system before I > > run > > the software to configure my system? ;-) > > Humm, I believe it's fair to assume that "most people" have some way > of puppet provisioning that will be able to take care of this > configuration detail. > > That being said, I concur that it would be sane design to allow a > module to compile in the absence of the custom facts etc. it may deploy to > agents during the first run.
I agree but its also quite hard, the proposed fix is using the masters vardir location as default for where servers must put their snippets, this is ridiculous and not a usable fix. There is no default really for where nodes put their vardir, we can assume /var/lib/puppet or something but that just doesn't hold true always and will in those cases just fail again during a run. Pluginsync is well understood and so widely used that I think more or less everyone has figured out how to enable it either first run or use a first run environment that bootstraps puppet - though how you would do that without the ability to edit the config file is a good question. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
