Issue #19260 has been reported by Steve Shipway.

----------------------------------------
Bug #19260: When you have a module+class called 'foo', node manifests included 
from a separate subdirectory 'foo' do not load
https://projects.puppetlabs.com/issues/19260

Author: Steve Shipway
Status: Unreviewed
Priority: High
Assignee: 
Category: compiler
Target version: 
Affected Puppet version: 2.7.18
Keywords: 
Branch: 


This strange behaviour has caused a rather large amount of damage on our 
systems today.

We have a number of node manifests in files in a subdirectory 'oracle', which 
are included with 'include oracle/*.pp'.  This used to work.

We then added a new module, 'oracle' which defines CLASSES oracle and 
oracle::fmw.  No node definitions are using these classes as yet.

After doing this, none of the manifests in oracle/*.pp appear to load, and the 
nodes start using the default node definition instead.  Deleting the 'oracle' 
module makes all work again, putting it back breaks it again.  Although we're 
still testing, it seems that this can also affect individual files called 
oracle.pp.

We have seen this before (node manifests apparently becoming invisible) but 
this is the first time we've managed to link it to a corresponding module/class 
name and repeat the behaviour at will.

This is bad on so many levels, particularly since our default node definition 
closes all firewall ports for security and reverting to it shut down access to 
all our major databases.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to