Issue #6907 has been updated by Stefan Schulte.
I have some problems with this patch. If you run in noop mode this raises the following error: <pre> err: /Stage[main]//Foo[my_foo_resource]: Could not evaluate: Provider bar is not functional on this host at /tmp/test/test.pp:4 </pre> While I can live with that (I would more like a warning like »skip resource: no suitable provider found«) I think using a provider in a puppetrun eventhough prefetching did not work (because the provider was not yet present during prefetching phase) can cause serious errors because the provider will most likely assume that there are currently no instances present. <pre> debug: Prefetching bar resources for foo err: Could not prefetch foo provider 'bar': Command some_binary is missing info: Applying configuration version '1320775712' notice: /Stage[main]//File[/tmp/foobinary]/ensure: created debug: /Stage[main]//File[/tmp/foobinary]: The container /tmp/foobinary will propagate my refresh event debug: /tmp/foobinary: The container Class[Main] will propagate my refresh event debug: Puppet::Type::Foo::ProviderBar: Executing '/tmp/foobinary ' notice: /Stage[main]//Foo[my_foo_resource]/ensure: created </pre> So I still prefer the "skip all resources with no suitable provider" approach. ---------------------------------------- Feature #6907: Ensure providers can be used in the same puppet run that their prerequisites are delivered in https://projects.puppetlabs.com/issues/6907 Author: Nigel Kersten Status: In Topic Branch Pending Review Priority: Urgent Assignee: Jason McKerr Category: provider Target version: 2.7.x Affected Puppet version: Keywords: Branch: This is possibly more accurately described as a collection of bug fixes, as we've aimed to fix this several times, however I'm characterizing this as a feature, and we're going to associate related bugs with it. Essentially we want to be able to use a provider in the same run that it's prerequisites (like :commands and paths) are delivered in. You should not have to run puppet twice to use a provider. We're aiming this at 2.6.x initially, but if it turns out that we need significant plumbing work to make this happen, we are re-targeting at Statler. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
