Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-647

master-{code, run, log}-dir settings should be optional

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: SERVER 2.0.0
    • Fix Version/s: SERVER 2.1.0
    • Component/s: Puppet Server
    • Labels:
      None
    • Template:
    • Sub-team:
    • Story Points:
      2
    • Sprint:
      Server Emerald 2015-05-27

      Description

      The example config says that the master-code-dir, master-run-dir, and master-log-dir settings are optional and will be pulled in from puppet's defaults if not specified (https://github.com/puppetlabs/puppet-server/blob/master/dev/puppet-server.conf.sample#L51-L64), but this does not seem to be the case. Running Puppet Server off of master (specifically I was running in the repl), if you don't specify these options, you get a schema error:

      2015-05-15 12:25:57,673 ERROR [p.t.internal] Error during service init!!!
      clojure.lang.ExceptionInfo: Output of initialize-config does not match schema: {:master-code-dir missing-required-key, :master-log-dir missing-required-key, :master-run-dir missing-required-key}
              at puppetlabs.services.jruby.jruby_puppet_core$eval34199$initialize_config__34200.invoke(jruby_puppet_core.clj:84) ~[na:na]
      

      These settings need to be added to the initialize-config function (https://github.com/puppetlabs/puppet-server/blob/master/src/clj/puppetlabs/services/jruby/jruby_puppet_core.clj#L99) so that we pull them in from puppet if they are not specified in puppet server's config.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jeremy.barlow Jeremy Barlow
              Reporter:
              ruth Ruth Linehan
              QA Contact:
              Erik Dasher
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support