[chef] Re: Re: Deployment triggered when it shouldn't be

[Clif Smith < >]

On Jan 9, 2012, at 12:01 PM, Clif Smith wrote:

> 
> On Jan 9, 2012, at 10:33 AM, Daniel DeLeo wrote:
> 
>> 
>> 
>> On Monday, January 9, 2012 at 8:09 AM, Clif Smith wrote:
>> 
>>> I have a recipe that, if a remote file is newer (using head), will 
>>> retrieve it, untar it, stop apache and start apache. It's been working 
>>> great and I use it to deploy a number of different builds. It's been 
>>> working great, except for one of the latest builds. With this build, it's 
>>> deploying every time chef-client runs even though the file hasn't 
>>> changed. Any ideas?
>> 
>> Have you tried running a request with curl to see if the server is doing 
>> the right thing?
>> 
> I hadn't prior but it looks good to me:
> 
> # curl -I http://fileserver.foo.com/deployments/stage01.tgz
> HTTP/1.1 200 OK
> Date: Mon, 09 Jan 2012 17:58:04 GMT
> Server: Apache/2.2.17 (Ubuntu)
> Last-Modified: Sun, 08 Jan 2012 22:40:46 GMT
> ETag: "24838-7d347ca-4b60bf90fd63d"
> Accept-Ranges: bytes
> Content-Length: 131286986
> Content-Type: application/x-gzip
> 
I couldn't determine the cause so I deleted the local temp file 
(/tmp/stage01.tgz).  On the next run chef deployed as it should have and 
hasn't again on subsequent runs (which is a good thing).  If anyone has any 
ideas why this happened, as I'm told it's happened prior, I'd appreciate it.