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

Cant use 'master' or 'agent' as environment names

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Cannot Reproduce
    • Affects Version/s: PUP 3.8.7
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      linux, debian jessie

    • Template:

      Description

      When using an environment named master, agent or main, it does not work

      Here I show having 2 environments named production and master
      When I get modulepath for production expansion is correctly done and everything works fine, but when I try to get it for master environment, it just prints the default basemodulepath

      # Show environments config
      root@puppetmaster:~# grep environments /etc/puppet/puppet.conf
      environmentpath = $confdir/environments
      root@puppetmaster:~#
       
      # GOOD
      root@puppetmaster:~# cat /etc/puppet/environments/production/environment.conf 
      modulepath=./modules:./external_modules:$basemodulepath
      root@puppetmaster:~# puppet config print modulepath --environment production
      /etc/puppet/environments/production/modules:/etc/puppet/environments/production/external_modules:/etc/puppet/modules:/usr/share/puppet/modules
      root@puppetmaster:~#
       
      # WRONG
      root@puppetmaster:~# cat /etc/puppet/environments/master/environment.conf 
      modulepath=./modules:./external_modules:$basemodulepath
      root@puppetmaster:~# puppet config print modulepath --environment master
      /etc/puppet/modules:/usr/share/puppet/modules
      root@puppetmaster:~#
      

      It's quite trivial to reproduce it, just create a new environment named after those reserved words ...

        Attachments

          Activity

            People

            • Assignee:
              javipolo javipolo
              Reporter:
              javipolo javipolo
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support