Closed nwolff closed 9 years ago
The error seems to be occurring prior to Packer being run in build.sh. Berkshelf is updating Cookbook dependencies, and is connecting to an invalid URL for Ark or Build-essential. #12 is unrelated, and would cause issues later on in the deployment process, when Chef attempts to download RPM files from GitHub once it begins to build the AMI.
We have some information on purging the Berkshelf cache to allow the berks vendor
command to fetch a fresh set of cookbook indexes from Chef Supermarket: https://github.com/datasift/datasift-connector/blob/97b3a12de7c62cc38255f42aefc7511f06d6f8bc/README.md#packer-builds-and-vagrant-provisioning
If the issue re-appears, attempt the following:
cd packer
rm -rf ~/.berkshelf/*
./build.sh <access-key> <secret-key>
FWIW I just reran ./build.sh a few hours later and it worked. Maybe berkshelf automatically removed the stale cache entries ?
This was caused by a temporary opscode availability issue. Refer to last post by Nathen Harvey in the following thread:
For release https://github.com/datasift/datasift-connector/releases/tag/1.0.19-1
I run ./build.sh ....
I get:
I tried this 4 times over a one hour period and always got the same error.
Maybe related to #12 ?
Do you think you could publish the amazon AMI so that we wouldn't have to run packer at all?