Bug #2770
closed
Import of Environments and Classes Fail
Description
On installing foreman 1.2 using the foreman installer (vagrant project here [1]) the import environment and classes functionality does not work. This issue has also been discussed on the foreman-user mailing list [2]. In summary:
- 2 environments defined - production & development
- puppet.conf: https://gist.github.com/dizz/5950107
- Example structure: /etc/puppet/environments/production example structure (showing paths to init.pp): https://gist.github.com/dizz/5950994
Andy
[1] https://github.com/dizz/vagrant-foreman
[2] https://groups.google.com/d/topic/foreman-users/H2WIGMfXIAI/discussion
Updated by Przemyslaw Bak over 11 years ago
The Foreman 1.2 + Puppet 3.2.2 with simple config - the same behaviour: cannot import puppet environments.
The Foreman just after installation is at the moment unusable.
Updated by Dominic Cleal over 11 years ago
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
I think I see what's happening, the correct environment directory structure isn't being created by the installer (we were trying to standardise the paths it uses in different configs).
[production]
modulepath = /etc/puppet/environments/production/modules:/etc/puppet/environments/common:/usr/share/puppet/modulesNote the path is /etc/puppet/environments/production/modules but the modules are installed under /etc/puppet/environments/production (missing the last modules/). The installer is only creating up to /etc/puppet/environments/production without the modules/ subdir, which is likely to throw you (it just did me too).
Updated by Dominic Cleal over 11 years ago
- Status changed from Assigned to Ready For Testing
Updated by Andy Edmonds over 11 years ago
I've just tested this and it works! Thanks very much Dominic!
Dominic Cleal wrote:
Updated by Sam Kottler over 11 years ago
- Status changed from Ready For Testing to Closed
The pull request got merged.