Puppet

given the following manifest:

class php {
    fail("php")
}

class apache::foobar::php {
    notice("yeah2")
    include php
}

class apache::foobar::webhosting_php {
    include apache::foobar::php
}

class somehost {
    include apache::foobar::webhosting_php
}

include somehost
notice("yeah")

and running it with puppet will not give the expected result:

# puppet foobar.pp
notice: Scope(Class[apache::foobar::php]): yeah2
notice: Scope(Class[main]): yeah

imho puppet should fail as the php class has clearly a fail statement.

I discovered this while debugging a certain host because it didn’t install php on it. the includes are similar to this lab setup, however spreaded over modules and different files. But I get the same result putting notices in the different parts as in the lab setup.

Currently I have no idea how to debug this further nor where exactly the problem may lie. As the classes are named somehow similar to address the needed functionality I had the idea that this might “confuse” puppet. So I tested the following manifest:

class test {
    fail("php")
}

class foobar {
    notice("yeah2")
    include test
}

class blah {
    include foobar
}

class somehost {
    include blah
}

include somehost
notice("yeah")

which fails as expected:

# puppet foobar.pp
notice: Scope(Class[foobar]): yeah2
php at /tmp/foobar.pp:2 on node foobar

So I definately think that this is a problem of the evaluation as putting a syntax error in the php class will fail puppet to parse the manifest.

either debug nor trace statements give more information.

Behaviour have been reproduced on:

• 0.24.5
• 0.24.6
• HEAD