Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-3256

multiple fileserver configs don't work

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:

      Description

      I have a multiple environment puppet server set up with the following structure: there are five environments. each one has a separate fileserverconfig variable pointing to a different fileserver.conf file. Each fileserver.conf file has a different path setting for [files].

      However, it only seems to read the first one. No matter which environment I use, it points to the "development" environment. This isn't the behavior I was expecting.

      puppet.conf:
      <pre>
      [main]

      1. Where Puppet stores dynamic and growing data.
      2. The default value is '/var/puppet'.
        vardir = /var/lib/puppet
      1. The Puppet log directory.
      2. The default value is '$vardir/log'.
        logdir = /var/log/puppet
      1. Where Puppet PID files are kept.
      2. The default value is '$vardir/run'.
        rundir = /var/run/puppet
      1. Where SSL certificates are kept.
      2. The default value is '$confdir/ssl'.
        ssldir = $vardir/ssl

      pluginsync = true
      factpath = $vardir/lib/facter

      modulepath = /etc/puppet/modules

      [puppetd]

      1. The file in which puppetd stores a list of the classes
      2. associated with the retrieved configuratiion. Can be loaded in
      3. the separate ``puppet`` executable using the ``--loadclasses``
      4. option.
      5. The default value is '$confdir/classes.txt'.
        classfile = $vardir/classes.txt
      1. Where puppetd caches the local configuration. An
      2. extension indicating the cache format is added automatically.
      3. The default value is '$confdir/localconfig'.
        localconfig = $vardir/localconfig
        server = pupp002.ir.dc
      4. splay = true
        runinterval = 600

      report = true

      [puppetmasterd]
      reportdir = /var/lib/puppet/reports
      reports = puppet_dashboard

      [development]
      manifest = /home/svn/puppet/repo/manifests/site.pp
      modulepath = /home/svn/puppet/repo/modules
      fileserverconfig = /etc/puppet/fileserver.conf.development

      [qa]
      manifest = /home/svn/puppet/releases/qa/puppet/manifests/site.pp
      modulepath = /home/svn/puppet/releases/qa/puppet/modules
      fileserverconfig = /etc/puppet/fileserver.conf.qa

      [staging]
      manifest = /home/svn/puppet/releases/staging/puppet/manifests/site.pp
      modulepath = /home/svn/puppet/releases/staging/puppet/modules
      fileserverconfig = /etc/puppet/fileserver.conf.staging

      [prodtest]
      manifest = /home/svn/puppet/releases/prodtest/puppet/manifests/site.pp
      modulepath = /home/svn/puppet/releases/prodtest/puppet/modules
      fileserverconfig = /etc/puppet/fileserver.conf.prodtest

      [production]
      manifest = /home/svn/puppet/releases/prod/puppet/manifests/site.pp
      modulepath = /home/svn/puppet/releases/prod/puppet/modules
      fileserverconfig = /etc/puppet/fileserver.conf.prod
      </pre>

      and one of the fileserver.confs:

      <pre>

      1. This file consists of arbitrarily named sections/modules
      2. defining where files are served from and to whom
      1. Define a section 'files'
      2. Adapt the allow/deny settings to your needs. Order
      3. for allow/deny does not matter, allow always takes precedence
      4. over deny
      5. [files]
      6. path /var/lib/puppet/files
      7. allow *.example.com
      8. deny *.evil.example.com
      9. allow 192.168.0.0/24
        [files]
        path /home/svn/puppet/repo/manifests/files
        allow 192.168.0.0/16
        allow 10.0.0.0/8

      [plugins]
      allow 192.168.0.0/16
      allow 10.0.0.0/8
      </pre>

      Thanks.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              redmine.exporter redmine.exporter
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support