A simple matter of…

Well just as I think I’m starting to get somewhere with puppet, I hit some problems. Fortunately I’m now starting to resolve them a little quicker (namely since they are simpler problems)

I still need the fairly gross workaround in order to structure things the way I’d like, but hey. One day I might actually write some of this stuff up – TBH a fair bit of it is, however although i’ve spent a large chunk of my own time (and holiday) doing this, a larger chunk is for work, on a customer project.

One issue which has bitten me twice now is that the new puppetmasterd doesn’t send bad configs to the client. However it doesn’t even tell the client this is the case so you can spend ages tweaking settings which aren’t actually reaching the client because of a typo elsewhere. This is documented, but still sucks.

The debconf patches are working fine for me BTW – I can now build from scratch a box using debian preseeding and puppet and bring up most infrastructure services fully automatically

The _next_ step is to activate the ldap client settings (which have been tested, just only _after_ an install). There is certainly a chicken/egg situation here and I suspect there may be some manual poking required for the actual LDAP and DNS master/slaves.