Issue #2321 has been updated by Christian Hofstaedtler.
Luke Kanies wrote: > Er, I somehow missed that adding --no-ca made it work; I read that as you > saying it didn't work. > > So yeah, it seems like rack support isn't reading the config file in > correctly. The expected way this should work is setting ca = false in the config file, yes? I don't see a reason why this shouldn't work with the rack stuff, but will take a look :-/ ---------------------------------------- Bug #2321: Rack does not correctly read in settings from puppet.conf 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 -~----------~----~----~----~------~----~------~--~---
