Project

General

Profile

Bug #1255

Error: "Unable to find directory /etc/puppet/modules in environment production"

Added by Brian Gupta about 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

On our puppetmaster we have three environments setup using modulepaths that aren't /etc/puppet/modules.

In the GUI, if I do:
1) Settings -> Puppet Classes
2) Import New Puppet Classes and Environments

I get a popup error:
"Unable to find directory /etc/puppet/modules in environment production"

Gonna search bug tracker for this issue and am planning an upgrade to trunk to see if maybe it is resolved.


Related issues

Related to Foreman - Bug #1068: Module path not guessed correctly with puppet 2.7Closed2011-07-26
Related to Foreman - Bug #1159: Class import behaviour not consistent "rake puppet:import:puppet_classes" x "UI"Closed2011-09-07

History

#1 Updated by Brian Gupta about 11 years ago

Upgraded tonight and still see the issue.

#2 Updated by Ohad Levy almost 11 years ago

  • Status changed from New to Ready For Testing

I think this is solved already - could you try the suggestion in the following comment:
http://theforeman.org/issues/1159#note-8

#3 Updated by Brian Gupta almost 11 years ago

Yes, that resolved it. However, I thought that was a "workaround" not a solution, which is why I kept the ticket open. (My apologies for not updating the ticket sooner.)

#4 Updated by Benjamin Papillon over 10 years ago

  • Status changed from Ready For Testing to Closed

Hello,

My thoughts are it is considered the good solution for the 0.4 version.
For the new 1.0 version, this solution is not valid anymore as you have to use smart proxy to import environments and classes

Also available in: Atom PDF