Hi, David. It is true that jclouds chooses not to enforce script timeout right now. We can still change this before 1.2.0, as it is a valid concern. Note that in doing so, we'll need the timeout property set to a reasonably high value, but not infinite.
Would you like this to throw an exception on timeout? -A On Thu, Oct 13, 2011 at 4:45 PM, David Alves <[email protected]> wrote: > Hi All > > I lost track of the discussion…. > What was the final status of the script timeout problems (I mean > when the init script takes longer than 10 mins the configure scripts are > executed as if all went well). > Is this expected? should a jira be open (or has it)? > I just ran into this problem on one of my tests… > … at the very least configure phase should not be executed on nodes > that have not finished init'ing right? > > -david
