[chef] Re: Re: Re: Re: Layout of deploy_revision

[Adam Jacob < >]

It is intended - in the face of failure, we abort, and if it's
ephemeral, idempotency and convergence will get you where you want to
go.

Adam

On Tue, Oct 4, 2011 at 3:21 PM, Brad Knowles 
<
 >
 wrote:
> On Oct 4, 2011, at 2:46 PM, Malcolm Box wrote:
>
>> Thanks! Now I've re-run it again and am getting what I expected - current 
>> linking directly to a release. I'd swear it was working differently 
>> yesterday. Very odd.
>
> You might try running it on a "fresh" server, i.e., one where you had not 
> run into this problem before.
>
> One thing I've discovered is that sometimes Chef will run into what it 
> thinks are problems and bomb out, but in fact what it wanted to have done 
> was actually accomplished, so that all you need to do is run it again.  In 
> particular, I've seen this behaviour with Chef and yum, which sometimes 
> exits with non-zero codes even if it did what you asked it to do.
>
> I don't know if that is the intended behaviour of Chef, but it is what I 
> have observed.
>
> --
> Brad Knowles 
> <
 >
> SAGE Level IV, Chef Level 0.0.1
>
>



-- 
Opscode, Inc.
Adam Jacob, Chief Product Officer
T: (206) 619-7151 E: