Bug #6945
closed
smart-proxy doesn't find the autosign.conf if not at "#{puppetdir}/autosign.conf"
Description
modules/puppetca/puppetca.rb hardocodes the autosign.conf file to
def autosign_file
"#{puppetdir}/autosign.conf"
endso even if we've set a different location in puppet.conf:
autosign = /etc/autosign.conf { mode = 664 }we still see this error in the foreman-proxy logs:
No such file /etc/puppet/autosign.conf
Updated by Brian Witt almost 10 years ago
Our puppetdir in this case is set to /etc/puppet. Is there anything else that uses puppetdir?
Updated by Dominic Cleal almost 10 years ago
- Category set to Puppet
Brian Witt wrote:
Our puppetdir in this case is set to /etc/puppet. Is there anything else that uses puppetdir?
Yes, it's also used to find puppet.conf, they're expected to be in the same directory.
Updated by Brian Witt almost 10 years ago
I thought the puppet.conf location was set via :puppet_conf:
Updated by Dominic Cleal almost 10 years ago
Brian Witt wrote:
I thought the puppet.conf location was set via :puppet_conf:
Yeah, puppet_conf will override the use of puppetdir/puppet.conf, so you can change puppetdir safely if you have puppet_conf set.
Updated by Brian Witt almost 7 years ago
Michael Moll wrote:
I'm leaning towards closing this.
Why?
Updated by Anonymous almost 7 years ago
I'd say it "works as designed". Maybe the docs would need updating...
Updated by Anonymous almost 7 years ago
I think I need to revise my opinion on that in the light of the whole Puppet 4 situation now. It seems the puppetdir setting is not used elsewhere in the pupetca module.
Updated by The Foreman Bot almost 7 years ago
- Status changed from New to Ready For Testing
- Assignee set to Anonymous
- Pull request https://github.com/theforeman/smart-proxy/pull/530 added
Updated by Anonymous almost 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset e7968a9dc616e1c4c28961c1b3cd182eb02c1831.