[chef] Re: Re: Re: ChefDK and Test Kitchen SSL issue

[Daniel DeLeo < >]

On Thursday, December 18, 2014 at 10:54 AM, Ryan Kelley wrote:
> using straight curl alone seems to work fine. i had a co-worker confirm 
> also.
>  
> 
 :~$
>  curl -I 
> https://opscode-omnibus-packages.s3.amazonaws.com/windows/2008r2/x86_64/chefdk-0.3.5-1.msi
> HTTP/1.1 200 OK
> x-amz-id-2: 
> w6BxBcDRByJUndEiNPu8sEXVmdsKx/r6XweQXrTmX7nVk5U3NyzJ1qw0s8+FT2soQfjHUBSn+9E=
> x-amz-request-id: 855D326C32841822
> Date: Thu, 18 Dec 2014 18:52:41 GMT
> Last-Modified: Fri, 14 Nov 2014 02:57:44 GMT
> ETag: "39a194da347481a41f88f0b02bc0fcc6"
> Accept-Ranges: bytes
> Content-Type: application/x-msi
> Content-Length: 229429754
> Server: AmazonS3
>  
> how do i find how vagrant is calling curl ?
I poked around in the /Applications/Vagrant directory on my mac and it looks 
like vagrant is bundling its own version of curl and its own cacert.pem 
(though I haven’t upgraded vagrant in forever, I have 1.4.2). Are you 
*always* seeing the errors from vagrant downloading boxes from S3 like in 
your original post, or do you get them during other operations as well? If 
you’re only seeing errors from vagrant, it’s possible they got bit by the 
Curl CA cert thing I linked. You might want to peruse their issue tracker to 
see if it’s been reported and fixed.


--  
Daniel DeLeo