Bug #7625
closed
Error ERF12-4115 when importing puppet classes
Description
Configure -> Puppet Classes -> Import from... produces this output:
ProxyAPI::ProxyException
ERF12-4115 [ProxyAPI::ProxyException]: Unable to get classes from Puppet for production ([RestClient::NotAcceptable]: 406 Not Acceptable) for proxy https://foreman.intranet.psfc.coop:8443/puppet
lib/proxy_api/puppet.rb:27:in `rescue in classes'
lib/proxy_api/puppet.rb:21:in `classes'
app/services/puppet_class_importer.rb:155:in `actual_classes'
app/services/puppet_class_importer.rb:78:in `new_classes_for'
app/services/puppet_class_importer.rb:25:in `block in changes'
app/services/puppet_class_importer.rb:24:in `each'
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'
Previously, three modules were imported successfully from forge.puppet.com. Module files moved from /etc/puppet/modules/ to /etc/puppet/environments/production/modules/ prior to import. Foreman does not detect modules in directory /etc/puppet/modules.
Updated by Dominic Cleal about 10 years ago
- Status changed from New to Need more information
Please see the wiki for some troubleshooting information: ERF12-4115
But essentially, you need to begin with the smart proxy logs to find out what the cause of the error is.
Updated by John McNally about 10 years ago
Dominic,
Thanks for the direction. Seems it was a permissions issue: Some files in /etc/puppet/environments/production/modules had been locked down too tight. After restoring the original permissions, the import completes normally.
Thanks.
Updated by Dominic Cleal about 10 years ago
- Status changed from Need more information to Resolved
Glad it's fixed, thanks.