Puppet users - Mar 2011 - Wrong module path when using external nodes vs. CLI args

I''ve started using the environment capabilities with puppet and set up
a [development] environment which points the modulepath to
/etc/puppet/development/modules. The [main] section puts it in
/etc/puppet/modules.

When I run puppet with --environment=development everything works great. When I
use my external none classifier which sets the environment, for some reason,
puppet uses the wrong module path for file references even though my
puppetmasterd log shows that it compiled the catalog for development (just like
it does when I set the environment on the CLI).

I can tell things aren''t working because, while it gets the right
catalog, the files it downloads are from the production modules.

Any hints?

-bjc

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Brian Cully wrote:
> When I run puppet with --environment=development everything works
> great. When I use my external none classifier which sets the
> environment, for some reason, puppet uses the wrong module path
> for file references even though my puppetmasterd log shows that
> it compiled the catalog for development (just like it does when
> I set the environment on the CLI).
> 
> I can tell things aren''t working because, while it gets the right
> catalog, the files it downloads are from the production modules.
Known bug: the node classifier is only run when the client
requests the catalog, not when it is downloading files.  Thus
when the client wants to fetch a file, the master blindly
trusts the client and gives it the file from the environment
the client says it wants (and if you haven''t explicitly set
the environment with --environment or in puppet.conf on the
client, it will default to "production").

https://projects.puppetlabs.com/issues/3910

The only workaround is to set the environment on the client.
But if you do that correctly, there is no need to have the
external node classifier set the environment as well...


	/Bellman

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Mar 22, 2011, at 19:21, Thomas Bellman <bellman@nsc.liu.se> wrote:
> https://projects.puppetlabs.com/issues/3910
Thanks. I can try to work around it for now and watch the ticket for a
resolution.

-bjc

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.