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

rundir and logdir are no longer relative to vardir

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Story Points:
      0
    • Sprint:
      Client 2015-03-04

      Description

      There are several directories that are rooted under a parent directory, such as the $rundir and $logdir being under $vardir. If you do not rely on the default location of $vardir and specify it explicitly, the children directories do not move with it.

      For example:

      $ puppet master --configprint vardir
      /Users/nwolfe/.puppet/var
       
      $ puppet master --configprint rundir
      /Users/nwolfe/.puppet/var/run
       
      $ puppet master --configprint rundir --vardir=/tmp
      /Users/nwolfe/.puppet/var/run
      

      I would expect the output to be:

      $ puppet master --configprint rundir --vardir=/tmp
      /tmp/run
      

      Note that this behavior might be different between root and non-root. This ticket is concerned with the non-root case, which is what is used by Puppet Server when loading the Puppet ruby code into JRuby.


      I believe that in the early days of AIO this behavior was supported, but the implementation introduced some sort of cyclical dependency between various classes/modules (specifically the run_mode.rb and defaults.rb if I remember correctly), so this was undone.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  nwolfe Nate Wolfe
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support