The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Bug #14152

Hooks for dependent settings not called

Added by Jeff Weiss about 4 years ago. Updated over 3 years ago.

Status:DuplicateStart date:04/24/2012
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Affected Puppet version: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


While working on #13948, I found that if you have a setting, like $libdir that is defined as $vardir/lib, when $vardir is changed, the hook for $libdir is not called with the new interpolated value. This is primarily a problem related to $libdir, but it may also affect $factpath.

Here’s a sample of the code that can reproduce the problem

    puts "vardir #{Puppet[:vardir]}"
    puts "libdir #{Puppet[:libdir]}"
    puts "$LOAD_PATH includes $libdir: #{$LOAD_PATH.include? Puppet[:libdir]}"
    Puppet[:vardir] = "/tmp/var"
    puts "vardir #{Puppet[:vardir]}"
    puts "libdir #{Puppet[:libdir]}"
    puts "$LOAD_PATH includes $libdir: #{$LOAD_PATH.include? Puppet[:libdir]}"

And here’s the output:

$ bin/puppet master --configprint pidfile --trace
vardir /var/lib/puppet
libdir /var/lib/puppet/lib
$LOAD_PATH includes $libdir: true
vardir /tmp/var
libdir /tmp/var/lib
$LOAD_PATH includes $libdir: false


Related issues

Related to Puppet - Bug #13948: libdir does not always get added to LOAD_PATH Closed 04/13/2012
Related to Puppet - Bug #7316: puppet face applications (subcommands) delivered via modu... Closed 05/02/2011
Duplicates Puppet - Bug #9827: Hooks for dependent settings not called Accepted 09/29/2011 10/05/2011


#1 Updated by Josh Cooper over 3 years ago

  • Status changed from Accepted to Duplicate

Dup of #9827

Also available in: Atom PDF