On Tue, Nov 20, 2012 at 12:51 PM, Andy Parker <a...@puppetlabs.com> wrote: >> This is on 2.7.19. Added ticket >> http://projects.puppetlabs.com/issues/17747.
Sweet, thank you for taking the time to do this. > I believe this is related to 2.7 eagerly loading the providers during > pluginsync. In 3.0 the providers are loaded only after the pluginsync is all > done and I think they are delayed until they are needed, but I'm not certain > about that. That's true, but I don't think the improved behavior in Puppet 3.0 is sufficient to resolve this specific issue. This specific issue is a chicken and egg problem where by a provider needs a gem, but the catalog run itself is the thing that provides the gem dependency. That is to say, even in Puppet 3.0 where we delay loading all of the providers until after pluginsync finishes, the catalog run hasn't yet installed the gem when the provider is loaded. The reason I think this is basically a very specific incarnation of #6907 is because that ticket is pretty specific from a product functionality perspective, "You should not have to run puppet twice to use a provider." -Jeff -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
