Support #8917
closed
cannot import modules/classes
Description
Foreman 1.7.1/uppet 3.7.3. Very similar, but not identical to #5856.
Error was:
Warning!
ERF12-2749 [ProxyAPI::ProxyException]: Unable to get environments from Puppet ([RestClient::ResourceNotFound]: 404 Resource Not Found) for proxy https://foreman.my.org:8443/puppet
Full trace:
ProxyAPI::ProxyException ERF12-2749 [ProxyAPI::ProxyException]: Unable to get environments from Puppet ([RestClient::ResourceNotFound]: 404 Resource Not Found) for proxy https://foreman.my.org:8443/puppet lib/proxy_api/puppet.rb:11:in `rescue in environments' lib/proxy_api/puppet.rb:9:in `environments' app/services/puppet_class_importer.rb:133:in `actual_environments' app/services/puppet_class_importer.rb:24:in `changes' app/controllers/concerns/foreman/controller/environments.rb:11:in `import_environments' app/models/concerns/foreman/thread_session.rb:33:in `clear_thread' lib/middleware/catch_json_parse_errors.rb:9:in `call'
I initially thought it was b/c of the warnings about directory environments, but those still aren't supported, per #5856 & #6004. puppet.conf attached. My question is: are there puppet module smart class params I should be setting/overriding in the Foreman UI?
Files
Updated by Dominic Cleal over 9 years ago
- Tracker changed from Bug to Support
- Category set to Puppet
Can you provide /etc/foreman-proxy/settings.d/puppet.yml please?
Directory environments are supported nowadays, by the way (via #4699, in Foreman 1.5.2).
Updated by Travis Burrell over 9 years ago
- File puppet.yml puppet.yml added
Attached. I'd actually edited this file previously, enabling puppet run via the UI using a custom command, but it seems that the upgrade overwrote my changes.
Updated by Travis Burrell over 9 years ago
Restoring my puppet.yml from the puppet.yml.dpkg-old & restarting the foreman-proxy service did the trick. Thanks, & you can close this.
Updated by Dominic Cleal over 9 years ago
- Status changed from New to Resolved
(:enabled was false in the config file)