Replying to myself - and removing html links as it looks like my message got classd as spam in my own mailbox.
My mistake was : I added the foreman user to the git group, instead of the foreman-proxy user. Changing this seems to allow the foreman proxy to see the classes.
I think it could be a good idea to warn when a directory is not readable in the logs. ?
Regards
···
De : foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] De la part de SCHAER Frederic Envoyé : mercredi 6 mars 2013 19:14 À : foreman-users@googlegroups.com Objet : [PROVENANCE INTERNET] [foreman-users] need help with thesmart proxy class/env importersHi,
I’m attempting to setup a new smart proxy before upgrading my production servers to latest foreman (1.1)/puppet (3.1).
My version :
rpm -q foreman-proxy
foreman-proxy-1.1stable-1.el6.noarch
The issue I face is the following : on the foreman web page, I click on the import button for the environments. and it tells me there is no change.
When I run the rake task, I get :
rake puppet:import:puppet_classes RAILS_ENV=production --trace
** Invoke puppet:import:puppet_classes (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute puppet:import:puppet_classes
Evaluating possible changes to your installation
No changes detected
Still, on localhost, I can access a few things :
curl -k -H “Content-Type:application/json” -H “Accept:application/json” https: //127.0.0.1:8443/puppet/environments
[“dev”,“production”]
curl -k -H “Content-Type:application/json” -H “Accept:application/json” https: //127.0.0.1:8443/puppet/environments/dev
{“paths”:["/etc/puppet/envs/dev","/etc/puppet/envs/common","/usr/share/puppet/modules"],“name”:“dev”}
The smart proxy runs on the same VM as the puppetmaster or foreman - and I’m using passenger.
The smart proxy is not configured with the “trusted_hosts” option of the foreman installer.
I set the log_level option to “DEBUG” in the smart proxy settings, but the only thing I constantly see is the following (no debug line) :
I, [2013-03-06T19:00:23.025567 #26971] INFO – : Initializing from Puppet config file: /etc/puppet/puppet.conf
I, [2013-03-06T19:00:23.242263 #26971] INFO – : Initializing from Puppet config file: /etc/puppet/puppet.conf
I made sure the foreman user is allowed to read the modules files, so I’m a bit lost at where to look in order to fix this ??
Any idea of how to fix the import of classes/envs ?
Thanks
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.