Issue #6907 has been updated by Luke Kanies.
Stefan Schulte wrote: > I have some problems with this patch. If you run in noop mode this raises the > following error: > [...] > > 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. > > [...] > > So I still prefer the "skip all resources with no suitable provider" approach. I'm a touch confused. We are skipping resources with no suitable provider, we're just doing it with an error (which causes dependencies to also be skipped) rather than with a warning (which would not skip dependencies). I'm less concerned about unsuitable providers having instances. Suitable providers downloaded in the same run are actually prefetched; it's only unsuitable providers that aren't. The major point of this bug is that you need to be able to download the plugins and use them in the same run; if you download, say, a gem provider and gems are already present, then the provider will be suitable and there's no problem. If you download and it's not suitable until Puppet installs rubygems, then you somewhat axiomatically don't have any ruby gems already on the system. Yes, there's a chance that installing the package system also installs packages and that you want to manage those at the same time, but that seems quite unlikely, and a significant amount of extra work for a very rare edge case. ---------------------------------------- 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: Jacob Helwig Category: provider Target version: 2.7.x Affected Puppet version: Keywords: Branch: https://github.com/lak/puppet/tree/tickets/2.7.x/6907-pluginsync_and_providers 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.
