Do modules need to be installed on agents?

[zerozer...@gmail.com]

Hi,

I'm getting confused about module paths...

In a master - agent configuration, if the classes applied to the agent need some additional Forge modules to be installed, is it enough if I install them on the master, or do I need to install them on all clients too?

I didn't need to install them on clients... until now, when I started using the domcleal-augeasproviders module which appeared to work differently.

And then, trying to get around this and rearranging modules and environments, I started having problems with other modules I already used before.

For example, on the master I have a custom class which contains a call to the class defined in spiette-selinux, like this:

class mymodule::myclass {

  class { 'selinux':

    mode   => 'disabled',

  }

}

If I run a puppet agent --test on a client where myclass is applied, I get a "Could not find declared class selinux" error.

This also happens if I install the spiette-selinux module on the client itself.

But if the spiette-selinux module is installed, then a simple "puppet apply manifest.pp" works fine (where manifest.pp only contains the "class { 'selinux': ...}" section as above).

What am I missing?

The spiette-selinux module is correctly installed on the master, it is listed in /etc/puppet/modules when I do a "puppet module list".

The agent is in the "development" environment, and $confdir/modules is in the modulepath for the development environment on the master.

Thank you very much.

Marco

[Rich Burroughs]

You should not need to install modules on the agents. If they use plugins you will want to have pluginsync enabled, see:

http://docs.puppetlabs.com/guides/plugins_in_modules.html

That may be what you ran into with the Augeas module. You shouldn't need to install the module on the client though.

I'm not positive what your issue is but installing the modules on the agent is not the solution. My best guess is that the module itself is not actually still in your modulepath on the Puppet master.

Rich

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3885136a-13dd-4c04-be7f-6673ef6b020a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Garrett Honeycutt]

Hi Marco,

I agree with Rich. The issue you are likely facing with the selinux
module is that the directory is 'spiette-selinux' instead of 'selinux'
or that the module is in the wrong path. Reading up on the auto loader
should clear things up for you.

http://docs.puppetlabs.com/puppet/latest/reference/lang_namespaces.html#autoloader-behavior

Best regards,
-g


--
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658

[zerozer...@gmail.com]

Il giorno martedì 1 luglio 2014 04:25:23 UTC+2, Garrett Honeycutt ha scritto:

 

I agree with Rich. The issue you are likely facing with the selinux
module is that the directory is 'spiette-selinux' instead of 'selinux'

The path was right, but thank you very much (to both of you) for the answers and the interesting pointers.

In the meantime I did a global software upgrade (puppet master, puppet agent, foreman...) and things started working as expected, but I'll give a read to those interesting docs anyway.

Marco.