Issue #3392 has been updated by Dominic Maraglia.
I have broken this bug into five points: 1) Behaviour with --parseonly and bad manifest. Currently puppet master --parseonly fails to detect faulty manifests - see issue 6928 for more info. 2) Starting puppet master and the creation of the ssl dir. 3) Create a PID file upon start up 4) Create/re-recreate ssl/ upon start-up 5) Serve status info over REST ---------------------------------------- Feature #3392: Preliminary puppetmasterd test coverage needed https://projects.puppetlabs.com/issues/3392 Author: Markus Roberts Status: Accepted Priority: Normal Assignee: Dominic Maraglia Category: Puppet Core Test Suite Target version: Patch: None Affected Puppet version: development Keywords: Branch: The following tests are being removed from the in-application rspec test suite as they were inappropriate for the tool, and will need to be tested instead in the test matrix. puppetmasterd - should create a PID file - should be serving status information over REST - should be serving status information over xmlrpc - should exit with return code 0 after parsing if --parseonly is set and there are no errors - should exit with return code 1 after parsing if --parseonly is set and there are errors puppetmasterd when run for the first time with noop - should create its ssl directory puppetmasterd when run for the first time without noop - should create its ssl directory -- 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://projects.puppetlabs.com/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.
