Network Device type & 'failed due to execution expired'

19 views
Skip to first unread message

Gavin Williams

unread,
Jan 2, 2013, 12:36:51 PM1/2/13
to puppe...@googlegroups.com
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???

Cheers
Gavin

Jeff McCune

unread,
Jan 2, 2013, 1:31:28 PM1/2/13
to puppe...@googlegroups.com
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 

fatmcgav

unread,
Jan 2, 2013, 1:46:11 PM1/2/13
to puppe...@googlegroups.com

Jeff

Cheers for the response.

Will give that a go tomorrow and post back, once I've worked out how to trace and debug... ;-)

Cheers
Gav

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To post to this group, send email to puppe...@googlegroups.com.
To unsubscribe from this group, send email to puppet-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.

Gavin Williams

unread,
Jan 3, 2013, 12:22:42 PM1/3/13
to puppe...@googlegroups.com
Good news... It looks like the timeout issue was a device symptom rather than a code issue :)

Rebooted the test filer, and it's now working as expected...

Happy days :)

Cheers
Gav
To unsubscribe from this group, send email to puppet-dev+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages