Hi, I've had a similar issue since a couple of years. Every brand new foreman/katello install I make works fine with the defined common module path (/etc/puppet/modules/) but after I upgrade it stops working and I have to import the classes to every environment. I never filled a bug because I never actually investigated the reaseon, but maybe the solution may help us both. Regards
El lunes, 10 de octubre de 2016, 17:36:40 (UTC-3), Konstantin Orekhov escribió: > > Hello all! > > I have a "common" environment with some non-app-related modules (OS repos, > DNS, NTP, things of that nature), and several other environments, which are > application-specific - for example, "production". > Most of the common modules need to applied to all systems in "production" > environment as well, However, after importing the puppet classes into > Foreman from "common" environment, they get mapped to that environment and > I don't see a way to add any of them to any of the hostgroups from > "production" environment. > > So, how do I share the modules/puppet classes between multiple > environments in Foreman? > > On puppet level this should be just fine as Foreman installer puts a > proper base path for me: > > # grep base /etc/puppet/puppet.conf > basemodulepath = > /etc/puppet/environments/common:/etc/puppet/modules:/usr/share/puppet/modules > > From Foreman/ENC point of view that should be fine as well - common > modules would get the same (global) params regardless of the environment a > particular machine is in. > > How would I accomplish this? > Thanks! > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
