Bug #21
closed
:modulepath: in config/settings.yaml seems to be ignored
Added by eric sorenson over 15 years ago.
Updated about 3 years ago.
Description
rake puppet:import:puppet_classes wasn't finding my classes, so I added a couple of puts to app/models/environment.rb to show what environment and modulepath it's looking. Now, even though my settings.rb says
---
:modulepath: /Users/eric/Sandbox/svn/puppet/etc/modules/
:tftppath: tftp/
This is what comes out:
rake puppet:import:puppet_classes RAILS_ENV=production
(in /Users/eric/Sandbox/foreman)
using environment production
scanning modulepath /Users/eric/.puppet/modules
scanning modulepath /usr/share/puppet/modules
Environment old:1 current:1
PuppetClasses old:0 current:0
I was able to trick it with a symlink but this would be good to have working.
- Category set to Importers
- Status changed from New to Assigned
- Assignee set to Ohad Levy
- Target version set to 0.1-1
Hi Eric,
The modulepath variable is not being used for importing classes, since the idea is that you should be able to read it from puppet.conf (if puppet can find it, we should be able to find it too ;))
It shouldnt be a big problem to make it work, but I was just wondering why it didnt pick up the right settings from your puppet.conf.
Can you post your puppet.conf?
- Status changed from Assigned to Ready For Testing
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
- Pull request https://github.com/theforeman/hammer-cli-foreman-puppet/pull/27 added
- Pull request deleted (
https://github.com/theforeman/hammer-cli-foreman-puppet/pull/27)
Also available in: Atom
PDF