Hi, We've ran into the same problem. Our current solution, which we're not happy about, is to also have the custom types on the master/production environment. Doing that at least the custom types are always available. Unfortunately, it makes it impossible to deploy an update of a custom type to a branch/environment for testing.
-- Daniele Sluijters On Wednesday, 15 August 2012 19:06:03 UTC+2, Douglas wrote: > > My issue may be related to this bug: > > http://projects.puppetlabs.com/issues/13858 > > "Custom types in environments require loading into master's libdir" > > However, now I'm not so sure, This was working previously with a given > client. However, after trying on a fresh client, it's failing with: > > err: Could not run Puppet configuration client: Could not find a > default provider for logical_volume > > The server seems to have the files: > /var/lib/puppet/lib/puppet/provider/logical_volume > /var/lib/puppet/lib/puppet/type/logical_volume.rb > > And so does the client: > /var/lib/puppet/lib/puppet/type/logical_volume.rb > /var/lib/puppet/lib/puppet/provider/logical_volume > > pluginsync=true in /etc/puppet/puppet.conf. Using multiple > environments and puppet 2.7.1. > > *sigh* > > Doug. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/gf-jmlXC-tcJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
