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

Issue with puppet creating production folder when multiple environment paths are set

    XMLWordPrintable

Details

    • Night's Watch
    • 3
    • NW - 2021-01-20
    • Needs Assessment
    • 42471
    • 1
    • Bug Fix
    • Hide
      The `production` environment folder used to be automatically created, at every Puppet run, in the first search path (given in the 'environmentpath' setting) if it did not already exist there. This fix makes sure to search through all the given paths before creating any new `production` environment folder.
      Show
      The `production` environment folder used to be automatically created, at every Puppet run, in the first search path (given in the 'environmentpath' setting) if it did not already exist there. This fix makes sure to search through all the given paths before creating any new `production` environment folder.
    • Needs Assessment

    Description

      Tested on the below but likely occurs in every version since PUP-2519 was added

      Puppet Version: 5.5.22**
      Puppet Server Version: 2018.1.18
      OS Name/Version: centos7

      Add environmentpath setting to puppet.conf with multiple paths set.

      E.g:

      environmentpath = /home/puppet/projects:/etc/puppetlabs/code/environments

      Puppet will create an empty folder production under /home/puppet/projects resulting in /etc/puppetlabs/code/environments/production getting ignored and no classes getting picked up for production

      Desired Behavior:

      Puppet should check all environment paths for a production folder before creating one.

      Actual Behavior:

       Puppet creates a production folder the first environment path and ignores the 2nd

      Attachments

        Issue Links

          Activity

            People

              luchian.nemes Luchian Nemes
              elaine.mccloskey Elaine McCloskey
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support