Bug #12390

modulepath not read in [master] in puppet.conf

Added by James Turnbull 3 months ago. Updated 3 months ago.

Status:Rejected Start date:02/02/2012
Priority:Normal Due date:
Assignee:Daniel Pittman % Done:

0%
Category:plumbing
Target version:-
Affected Puppet version:2.7.9 Branch:
Keywords:
Votes: 0

Description

Platform: Ubuntu 10.04 Puppet: Tested 2.7.9, 2.7.10 and PE 2.0.1

To replicate run:

$ sudo puppet --configprint modulepath

Working puppet.conf:

[main]
    modulepath = /etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules:/tmp
[master]

$ sudo puppet --configprint modulepath
/etc/puppet/modules:/usr/share/puppet/modules

Should return – /etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules:/tmp

Fixed if I do:

[main]
[master]
    modulepath = /etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules:/tmp

$ sudo puppet --configprint modulepath
/etc/puppet/modules:/usr/share/puppet/modules:/tmp

History

#1
Updated by James Turnbull 3 months ago

  • Category set to plumbing
  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Jason McKerr
  • Affected Puppet version set to 2.7.9

#2
Updated by Daniel Pittman 3 months ago

  • Status changed from Needs Decision to Needs More Information
  • Assignee changed from Jason McKerr to James Turnbull

James Turnbull wrote:

Platform: Ubuntu 10.04 Puppet: Tested 2.7.9, 2.7.10 and PE 2.0.1

To replicate run:

sudo puppet --configprint modulepath

Can you replicate this with sudo puppet master --configprint modulepath please?

I suspect the default mode for puppet without a subcommand has changed, but that doesn’t matter – what matters is if the master sees the modulepath, which is what the variant command checks.

#3
Updated by James Turnbull 3 months ago

  • Status changed from Needs More Information to Accepted
  • Assignee changed from James Turnbull to Daniel Pittman

I can’t replicate it with: sudo puppet master —configprint modulepath. That works perfectly.

#4
Updated by Daniel Pittman 3 months ago

  • Status changed from Accepted to Rejected

In that case I don’t think there is a substantial problem here. The runmode when you don’t specify a subcommand is happily in the world of “undefined behaviour”, and we do the right thing when you do say what you want to act as.

(Actually, probably undefinable, because you can reasonable argue that all of master, agent, and apply are sensible defaults there.)

If someone can name a concrete problem this introduces, we can tackle this, but otherwise we should just discourage users from this risky area.

Also available in: Atom PDF