You need to look both in jclouds (runscript on instance creation) and Whirr (script action). On Dec 7, 2012 10:09 PM, "Steve Loughran" <[email protected]> wrote:
> I've just been hit by WHIRR-653 again; deploying to the latest AMIs hit a > version conflict between the snappy.i686 bin in EPEL with some dependencies > built into the AMI, and of course without exit code checking, the deploy > didn't halt with a useful message. > > What would it take to have exit codes examined? Is this in jclouds or whirr > -and if in whirr, where should I look? > > -steve >
