Puppet

Hmm:

class one {
    notify { "one": }
}

class one {
    notify { "two": }
}   
include one

And I get:

luke@phage(0) $ test.pp
notice: one
notice: two
luke@phage(0) $

Strangely, I just ran your code and got the same behaviour you’re getting (that is, only the first notice). Even stranger, I added my ‘notify’ resources to these classes and got my new behaviour again with all three notices:

class mysql { 
    notice('This is a load of the [[MySQL]] class') 
    notify { one: }
}
class mysql {     notice('This is a load of the second [[MySQL]] class') 
    notify { two: }
}
class mysql {     notice('This is a load of the third [[MySQL]] class') 
    notify { three: }
}
include mysql

Returns

luke@phage(0) $ test.pp
notice: Scope(Class[mysql]): This is a load of the [commit:MySQL]] class
notice: Scope(Class[mysql): This is a load of the second [commit:MySQL]] class
notice: Scope(Class[mysql): This is a load of the third [[MySQL]] class
notice: two
notice: three
notice: one
luke@phage(0) $

So, I don’t know what the bug is here, but there’s definitely a bug.

jamtur01 wrote:

When multiple classes of the same name are defined:

class mysql { notice(‘This is a load of the MySQL class’) }

class mysql { notice(‘This is a load of the second MySQL class’) }

class mysql { notice(‘This is a load of the third MySQL class’) }

According to Luke the contents of each new class of the same name are just added to the initial class and processed.

Testing indicates that this isn’t the behaviour and in fact only the first class is processed, i.e. using the above example the only notice returned is:

“notice: mysql: This is a load of the MySQL class”

I recommend that either this configuration throws an error – making classes unique – or the combination behaviour is fixed to include all content of each class.

I just fixed it in the tickets/0.24.x/857 branch in my github repository: http://github.com/masterzen/puppet/tree/tickets%2F0.24.x%2F857

Can you please rebase to the current 0.24.x

Hi James,

Rebased against current 0.24.x. It seems to apply fine above #1402. It is still in the tickets/0.24.x/857 branch in my github repository: http://github.com/masterzen/puppet/tree/tickets%2F0.24.x%2F857

Hi James,

I rebased both #857 and #1402 on tickets/0.24.x/1402+857 in my github repository: http://github.com/masterzen/puppet/tree/tickets%2F0.24.x%2F1402+857

Pushed in commit:9f30306d2c768bad3327ecb7748669afb10cd4aa in branch 0.24.x