Re: [foreman-users] Cannot import Modules/Classes on 1.12 with Puppet 4

Hi, common didn't had an environment.conf in it, I placed it in, didn't fix it. When I did a mv * ../../modules foreman found all my classes, this is strange to me. So, your last line is indeed a fix, but it doens't solve the problem for environments/common Do you want me more to chec/test ?

Re: [foreman-users] Cannot import Modules/Classes on 1.12 with Puppet 4

So that looks ok, I think, but I do wonder about how "common" is inside the environmentpath. Does "common" have an environment.conf as well (so that puppet would regard it as a valid environment)? Also this is interesting: On 17 October 2016 at 09:40, Matt wrote: > ... I

Re: [foreman-users] Cannot import Modules/Classes on 1.12 with Puppet 4

Hi Greg, I wasn't sure about them, here they are: # tree /etc/puppetlabs/code/environments -d -L 3 /etc/puppetlabs/code/environments ├── common │ ├── accounts │ │ ├── files │ │ ├── lib │ │ ├── manifests │ │ ├── spec │ │ └── templates │ ├── apache │ │ ├── files │ │

Re: [foreman-users] Cannot import Modules/Classes on 1.12 with Puppet 4

It's hard to say what might be happening without seeing the structure. Can you share your puppet.conf on the master, and the output of "tree /etc/puppetlabs/code/environments -d -L 3"? -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To