You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having a problem running this cookbook on AWS through Packer / chef-solo. i have a feeling it's a problem with chef, but this is my first chef deploy so i'm just guessing. I'm calling it like this (that line into is destined for a Jenkins job) /opt/packer/packer build coldfusion10.json
here's the json file
my mistake.
a trap for middle-aged players : this repo is called chef-coldfusion10, but the folder has to be called
cookbooks/coldfusion10
otherwise the first time chef tries to access a resource on the target system it can't find it (even though it's been running the rest of the scripts succesfully)
you can close this issue.
andrewlorien
changed the title
erb file does not exist (but it does)
erb file does not exist (but it does) - SOLVED
Feb 11, 2015
I'm having a problem running this cookbook on AWS through Packer / chef-solo. i have a feeling it's a problem with chef, but this is my first chef deploy so i'm just guessing. I'm calling it like this (that line into is destined for a Jenkins job)
/opt/packer/packer build coldfusion10.json
here's the json file
the recipe starts an instance successfully with RedHat 6.6 or 7, but fails at the first template call like this
The only similar problem i've found is one guy who seems to have been having the same problem with packer and chef-solo for quite a while. i can't believe there are only two of us though - maybe he and i both have the same config problem.
https://tickets.opscode.com/browse/COOK-3501
https://tickets.opscode.com/browse/COOK-3961
The text was updated successfully, but these errors were encountered: