On Wed, Jan 2, 2013 at 9:36 AM, Gavin Williams <[email protected]> wrote:
> Afternoon all > > I'm starting to put a bit more work into my NetApp Puppet device support. > > I've currently hit an issue whereby I can get the core 'create' def to run > fine, but when I try and loop in some of the other property methods, the > puppet run is failing with: > Puppet::Provider::Netapp_volume autoincrement=: Setting of auto-increment > for volume v_puppet_test020120131713 failed due to execution expired. > > The latest code changes were made under: > https://github.com/fatmcgav/fatmcgav-netapp/commit/9f6ef43c0f4320e04904c0a8284841d2d8199bb2 > I shamefully ripped the code snippet from the puppetlabs-f5 code :) Cheers > Nan. > > It looks like the autoincrement value does get set correctly, so the > setter is running, but it doesn't move on to the other methods in the > list... > > Any ideas??? > Execution expired usually means that an action a provider is carrying out took too long to complete and Puppet bailed out as a result. I recommend running with tracing enabled and then dropping into a debugger right before the execution expired exception is raised. Once you're in a debugger you could run the command manually and see if it is in fact taking a long time (>30 seconds) to complete. It may help to publish the code somewhere, ideally on Github, along with a gist of the backtrace so we could all see exactly what's happening. Hope this helps, -Jeff -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
