Issue #2321 has been updated by Nigel Kersten.
Nope. No useful logs if I do that.
I should have mentioned that in the 0.24.x config.ru I was actually doing this:
<pre>
# The list of handlers running inside this puppetmaster
handlers = {
:Status => {},
:FileServer => {},
:Master => {},
# :CA => {},
:FileBucket => {},
:Report => {}
}
</pre>
to explicitly disable the CA functionality, as with Rack in 0.24.x at least, it
seemed to ignore the ca = {false, true} setting from puppet.conf
To try to mimic this behavior, I just tested this with 0.25.0 rack.
<pre>
ARGV << "--no-ca"
</pre>
and everything works happily.
So really it seems like the problem is the rack config not actually using
puppet.conf settings consistently?
----------------------------------------
Bug #2321: Unable to run a non-CA server without having the CA private key/pass
etc.
http://projects.reductivelabs.com/issues/2321
Author: Nigel Kersten
Status: Accepted
Priority: Normal
Assigned to:
Category: SSL
Target version: 0.25.0
Complexity: Unknown
Affected version: 0.25.0
Keywords:
Our standard Puppet servers don't operate as a CA.
When upgrading a development server to 0.25.x, I found that the rack
application simply refused to start unless I copied over the CA private
key/passphrase etc.
Note that a webrick server does actually work, so the fault may lie more in the
rack application config than puppetmasterd itself.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
