Jira (PUP-2963) modulepath not being respected in multi-path setups

[Daniel Henninger (JIRA)]

Title: Message Title

Daniel Henninger created an issue   Puppet / PUP-2963 modulepath not being respected in multi-path setups Issue Type: Bug Affects Versions: 3.6.2 Assignee: Andy Parker Components: Server Created: 23/Jul/14 2:40 PM Environment: Red Hat Enterprise Linux 6, and admittedly complex environment (not in the puppet context) Priority: Normal Reporter: Daniel Henninger Hi there! We have a Puppet set up where we have three paths, in the following order, in one's module path: 1. Your environment 2. Root environment (The core environment) 3. Global modules (stuff that's downloaded from puppet forge) In this setup, the Root environment makes up everything that is the "base" of our Linux installs. So for example it sets up SSH, Kerberos, OpenAFS, LDAP, etc all based off standards across our university. Individual colleges or groups have their own environments. (we tend to refer to them as "puppet repos") We suggest that they call their own modules something with a common prefix so as not to conflict with modules in root or global modules. However what we want is for folk to be able to override modules if they so choose. For example, we use the puppetlabs firewall module and it is currently in the root repo (don't ask) and then there is an ncsufirewall module that calls firewall. It makes up the base firewall setup for campus. If I extract a newer version of the puppetlabs firewall module into my own repo (#1 from above) and I also needed to make a copy of ncsufirewall because it was relying on some old parameters that aren't there anymore, I end up with this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate declaration: Resources[firewall] is already declared in file /srv/puppet/root/modules/ncsufirewall/manifests/base.pp:12; cannot redeclare at /srv/puppet/chass_danieltest/modules/ncsufirewall/manifests/base.pp:12 on node MYHOSTNAME-d9048e7f-80ab-4c71-83a2-cfd85ff58f7e In this case chass_danieltest is the name of my environment. From puppet.conf on master: manifest = /srv/puppet/$environment/site.pp modulepath = /srv/puppet/$environment/modules:/srv/puppet/root/modules:/srv/puppet/global-modules I brought this up on #puppet and what hesco here is saying makes a lot of sense for what might be occurring: [04:54 PM] <hesco> Jadestorm: your question raises something I have been wanting for a while, the abaility to inherit and overload modules from other environments. [04:55 PM] <hesco> The issues you report are the ones I have feared. Had not occured to me to list multiple paths in modulepath. Glad to know that is possible. [04:55 PM] <hesco> But the use case you allude to would make a wonderful contribution to puppet. Hope someone is already working on it. I do hesitate to call this a bug as it may be intended or expected behavior. So please feel free to move this as you see fit. =) And if I'm simply doing something ridiculous, which is not outside of the realm of possibility, let me know! Thanks much! Add Comment   This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.