doesn't invoke test while using ec2 driver #37
Comments
|
Yes that is strange and looks like the built in dummy (no-op) driver is getting selected. Could you post the result of |
|
Here is the output |
|
@JigarJoshi ok, I think I see here; you'll need to indent the configuration under the ---
driver:
name: ec2
aws_access_key_id: SOME_KEY
aws_secret_access_key: SOME_KEY
aws_ssh_key_id: id_rsa-aws
ssh_key: /path/to/jigaraws.pem
security_group_ids: ["SOME_GROUP"]
region: us-west-2
availability_zone: us-west-2c
require_chef_omnibus: true
subnet_id: SOME_SUBNETWhat the |
|
Thanks @fnichol it got further! Now the config is like and error message is Googling around, looks like this is common issue with confusing error message, I will update more |
|
this is very common error it seems, with lots of forum results, all suggesting change from |
|
looks like fog/fog#713 |
|
I was using security_group_name instead of id, it works I can startup instance with specific Thanks! |
|
Had the same problem and took me a while to find the solution. Thanks for the post, it helped a lot. Final working configuration for me is: driver:
aws_access_key_id: <%= ENV['AWS_ACCESS_KEY_ID'] %>
aws_secret_access_key: <%= ENV['AWS_SECRET_ACCESS_KEY'] %>
aws_ssh_key_id: <%= ENV['AWS_KEYPAIR_NAME'] %>
region: <%= ENV['AWS_REGION'] %>
availability_zone: <%= ENV['AWS_AVAILABILITY_ZONE'] %>
provisioner:
name: chef_zero
require_chef_omnibus: latest
platforms:
- name: ubuntu-12.04
driver:
name: ec2
image_id: ami-60a10117
flavor_id: t2.micro
security_group_ids: SOME_SG_ID
vpc_mode: true
vpc: SOME_VPC_ID
subnet_id: SOME_SUBNET_ID
username: ubuntu
ssh_key: <%= ENV['EC2_SSH_KEY_PATH'] %>@fnichol : Must admit it is making it quite difficult that the documentation on the configuration at this point in time is not mentioning at all some of the options cited here, including for instance This, IMHO, actually is a more widespread problem with Chef related tools and work (for instance chef-boneyard/chef-provisioning-aws#58 or this comment on a Chef Provisioning issue chef-boneyard/chef-provisioning/issues/186). I have too often found it difficult to find reliable, just reasonably up-to-date information to help me out working not only on new stuff like Chef Provisioning, but also with Chef and offsprings. Things get mixed up and give different information on docs.chef.io , on github and the other dedicated websites (http://kitchen.ci/ is a good "lets start from nothing" tutorial, but is no reliable and fully informative doc as it feels it is presented as). Sounds like a clearer and stronger policy about doc needs to be put in place there. Often I find that out-of-date documentation is worse than no documentation at all. And I have been too many times in that situation here. Don't get me wrong: I love the thing. Hence the extra time I am spending trying to figure out how it works. But how many people out there are being deterred from using Chef because of this? I would bet a fair few. It certainly is a significant break to a widerspread use of the tool, and on my side it makes it much more difficult to sell Chef internally, at my company. My 2 p. |
|
I completely agree with you @esciara it really is all a mess, which is a shame. |
This is my
.kitchen.ymllooks like, if I switch driver back tovagrantit is able to create virtual box instance and invoke the tests on itbut if I use
ec2driver it just exists with exit code0in less than a second and with following outputDid I miss something in configuration ? I am expecting it to spin up an instance on ec2 and execute bats test against it
The text was updated successfully, but these errors were encountered: