Foreman » Smart Proxy

The smart proxy log looks reasonably successful, it's listing manifests that are being parsed for classes. I'd suggest one these options is likely:

1. The manifests are failing to parse, the smart proxy may not list errors. Use puppet parser validate to check.
2. The manifests don't contain classes.
3. The classes are ignored by Foreman's ignored_environments.yml

Can you view the output of the smart proxy API call by using cURL? e.g. curl http://proxy.example.com:8000/puppet/environments/production/classes

Hi Dominic,

Back with answers:

Note: I have left only 2 modules, removed * of them for debugging purposes. And replaced "import module" with "include module" in site.pp
stdlib
logrotate

--------------------------
The smart proxy log looks reasonably successful, it's listing manifests that are being parsed for classes. I'd suggest one these options is likely:

The manifests are failing to parse, the smart proxy may not list errors. Use puppet parser validate to check. ---> Parsing fine now
The manifests don't contain classes. ---> contains classes
The classes are ignored by Foreman's ignored_environments.yml - in foreman I have only config/ignored_environments.yml.sample, it is not used

Can you view the output of the smart proxy API call by using cURL? e.g. curl http://proxy.example.com:8000/puppet/environments/production/classes
A: curl http://puppetmaster2.phgroup.com:8000/puppet/environments/production/classes --> []
it does not see them it seems.

Thanks, that does confine the problem to the smart proxy, but doesn't show any likely cause.

Re-reading the description, I'm unsure that Puppet and the smart proxy are correctly set up.

puppet master:*3.8.5 (os installed)
[..]
2. Our smart/foreman are deployed under a separate user deployer (deployer is a member of puppet group), using rvm and ruby 2.3.0.please see attached

The "Syck" errors in your deployeruser_gems.log file is because Puppet 3.x is being used under Ruby 2.3.0, which isn't compatible (see https://docs.puppet.com/guides/platforms.html#ruby-versions).

The smart proxy when using Puppet 3.x will need to load Puppet to parse manifests, so it must be run under a mutually compatible version. I'd suggest trying to run the smart proxy under 2.1.0 as well (or upgrade to Puppet 4, which doesn't have these issues).

Lastly, there are both Puppet 4 and 3 gems listed in the Bundler output, so ensure you run the smart proxy with bundle exec to use the one specified in your Gemfile/Gemfile.lock. If not then it might be trying to use Puppet 4.

It seems i missread doc, all ok and thank you.