Did exactly that. Got:
r...@server19:~# puppetd --test --tags=bootstrap
info: Loading fact dmidecode
...
info: mount[modules]: Mounted
info: mount[plugins]: Mounted
err: Could not create apt-da...@puppet: user apt-dater doesn't exist
warning: Not using cache on failed catalog
warning: Configuratio
ISTR trying that and having the same problems.
User depends on class ldap-users. (So in theory, anything that needs a
user will require that.) Puppetd bails after grabbing the config with
"cannot find user joe" because ldap isn't set up. (Same using tags.)
Users may be a special bug though..
On
In general, it seems like the best way to handle "must go first"
bootstrap items like that is with environments. (We haven't gotten
there yet, but we're moving in that direction.)
New node comes up in environment bootstrap, where there is a generic
definition and 1 class that just grabs the bare
On 10/24/2009 11:25 AM, Douglas Garstang wrote:
>
> Oh boy. Puppet is frustrating the heck out of me.
> I have this below
>
> node tst_basenode {
>
> include yum
>
> Package {
> require => [
> Yumrepo["CentOS-Base"],
> Yumrepo["EPEL-Core"],
>
> node tst_basenode {
>
> include yum
>
> Package {
> require => [
> Yumrepo["CentOS-Base"],
> Yumrepo["EPEL-Core"],
> ...
> ]
> }
> }
>
> node tst_childnode inherits tst_basenode {
> include ldap_client
> }
>
[snip]
> Quite simply, how do
