Red Hat Bugzilla – Bug 970196
Properly support colon-separated modulepath
Last modified: 2014-06-18 04:14:22 EDT
Description of problem:
In my master section of my puppet.conf I have the following modulepath:
modulepath = $confdir/environments/$environment/puppet_modules:/home/$environment/puppet_modules
For my personal testing environment (kcormier) I keep all of my modules under /home/kcormier/puppet_modules. /etc/puppet/environments/kcormier/puppet_modules does not exist. Neither does the parent directory /etc/puppet/environments/kcormier. Puppet works fine however foreman fails to import my classes and thinks the environment does not exist. If I create /etc/puppet/environments/kcormier, foreman will load my classes correctly. Just to note, /etc/puppet/environments/kcormier/puppet_modules still DOES NOT exist, however it's parent directory does.
This was found with foreman-proxy 1.1rc1 from the foreman-1.1.rc4 rpms running on centos 6.3 fully patched.
Fixed upstream in d603c3c9438b03cfab968d5654c83557d227a217.
Moved to ON_QA as part of puddle 4.5.
please provide verifications steps
"Either add a dummy directory to the puppet's module path, or delete a directory specified in the path from the disk."
Still may not be clear. Perhaps ping dev directly if there are further questions.
clearing needinfo flag.
Upstream fix, shipped in MDP1.