Issue #2321 has been updated by Luke Kanies.
You could try explicitly setting Puppet::SSL::Host.ca_location = :none. At some point we'll have an external routes file (mostly likely for 0.26), but for now, you have to explicitly configure this kind of stuff, and that's how you disable the usage of (and expectation for) the CA. If you look in the puppetmasterd.rb file, you'll see this code with some control structures around it based on the value of --no-ca. It's worth asking why --no-ca isn't sufficient with config.ru, but it's probably an ordering thing. ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
