Project

General

Profile

Actions
Copy link

Bug #337

closed

Import classes button not working

Added by SyRenity Now over 14 years ago. Updated over 13 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
SyRenity Now
Category:
Web Interface
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hi.

If I create a new module and click the "Import classes" button, nothing is imported.

Only if I manually run the command "rake puppet:import:puppet_classes RAILS_ENV=production", then it's working.

Regards.

Actions
Copy link
 #1

Updated by Ohad Levy over 14 years ago

  • Status changed from New to Need more information
  • Assignee changed from Ohad Levy to SyRenity Now
  • Priority changed from High to Normal
  • Target version deleted (0.1-5)

can you provide the log entries, and your setting file?

Actions
Copy link
 #2

Updated by Ohad Levy over 14 years ago

  • Status changed from Need more information to Rejected
Actions
Copy link
 #3

Updated by Mikael Fridh over 13 years ago

Seems like you need to set one of two things:

/etc/foreman/settings.yaml:

:modulepath: /etc/puppet/modules/

or

/etc/puppet/puppet.conf:

[main]
modulepath = /etc/puppet/modules

According to wiki:
modulepath

This it the modulepath that foreman uses when processing puppet modules. It is usually able to determine this itself at runtime but if it is not able to find a value then modulepath is used.
Default: /etc/puppet/modules

So, I wonder if there's something wonky about my environment which makes it not find this information out?

It should search the default: /etc/puppet/modules:/usr/share/puppet/modules ...

Actions
Copy link

Also available in: Atom PDF