Project

General

Profile

Actions

Bug #2706

closed

Failed to import puppet environments using foreman-proxy

Added by Myungjee Zhao almost 11 years ago. Updated almost 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Puppet integration
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I want to integrate puppet and foreman, so I install foreman, foreman-proxy and puppet-server.
Below is the version number I installed in my puppet master machine.

foreman-1.1stable-3.el6.noarch
foreman-proxy-1.1stable-1.el6.noarch
puppet-server-2.6.18-3.el6.noarch

I have configured the below lines in my foreman-proxy configuration file.
:puppet: true
:puppet_conf: /etc/puppet/puppet.conf

And I added two environments in my puppet.conf file as below.

[DEVELOPMENT]
modulepath = /var/opt/ActiveEnvironments/DEVELOPMENT/puppet/modules
manifest = /var/puppet/site.pp

[TESTING]
modulepath = /var/opt/ActiveEnvironments/TESTING/puppet/modules
manifest = /var/puppet/site.pp

But when i issue the command 'rake puppet:import:puppet_classes RAILS_ENV=production', it always prompts the below info.

Evaluating possible changes to your installation
No changes detected

I can get the environments from 'curl -k -H "Content-Type:application/json" -H "Accept:application/json" http://puppet:8443/puppet/environments'
==> ["DEVELOPMENT","TESTING"], but no entry exists in the real database.
All environments I configured should be existing in my database that is configured in /etc/foreman/database.yml file after i issue rake command. right?

I have investigated this issue for a bit time and have no idea what the problem is.
Could anyone give me some suggests?

Any response will be much appreciated.

Actions #1

Updated by Dominic Cleal almost 11 years ago

  • Status changed from New to Feedback

a) Do both of the environments contain modules and classes? Otherwise Foreman may not import them.
b) It's not clear that you've checked the Foreman web UI under More->Configuration->Environments and Puppet Classes to see if the classes you're expecting are present.
(I'd generally recommend using the import button on the Puppet Classes instead of the rake task)
c) Failing all of that, please check /var/log/foreman-proxy/proxy.log for errors.

Actions #2

Updated by Myungjee Zhao almost 11 years ago

Thanks for your quick response. There is no classes in my modules, so the import failed.

Actions #3

Updated by Dominic Cleal almost 11 years ago

  • Status changed from Feedback to Rejected

Thanks for confirming.

Actions

Also available in: Atom PDF