I wanted to update this thread as it seems that on puppet 4 the overall, so known common manifests are now in /etc/puppetlabs/code/modules.
Seperate environments are only picked up in /etc/puppetlabs/code/environments/<environmentname>/modules I think it's how the API works and searches. Op dinsdag 18 oktober 2016 15:23:41 UTC+2 schreef Matt: > > 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 ? > > > Op dinsdag 18 oktober 2016 10:48:24 UTC+2 schreef Greg Sutcliffe: >> >> 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 <[email protected]> wrote: >> > ... I saw that my agents were not able to find the classes on a run ... >> >> To me that says Puppet can't find your classes either. Since Foreman >> queries Puppet for it's class listing in Puppet4 (via the puppetserver's >> API) then I would expect Foreman to think the classes had gone if Puppet >> can't find them either. >> >> It *feels* like a misconfig of some kind, but I can't quite spot it. >> Perhaps try moving the common modules to "/etc/puppetlabs/code/modules" >> (since thats also in the basemodulepath) as a test? >> >> Greg >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
