Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

subnet_id always expects a string #463

Closed
claudenm opened this issue Aug 8, 2019 · 2 comments
Closed

subnet_id always expects a string #463

claudenm opened this issue Aug 8, 2019 · 2 comments

Comments

@claudenm
Copy link

claudenm commented Aug 8, 2019

The documentation says "When working with spots, you can provide an array in which case the driver will try each subnet until it can get a spot."

However, when I specify an array in kitchen.yaml:

  subnet_id:
  - subnet-1
  - subnet-2
  - subnet-3

I get this error bubbled up from the aws-sdk:

[expected params[:network_interfaces][0][:subnet_id] to be a String, got value ["subnet-1", "subnet-2", "subnet-3"]]

Which makes sense, because subnet_id is a string in the run_instances command.

I am including a spot price as well. Is there something I'm missing?

Kitchen version: 2.2.5
Kitchen-ec2 version: 3.1.0

@github-vincent-miszczak
Copy link
Contributor

I can reproduce the issue when spot_price is not defined but it looks ok when it's defined.
I could set spot_price: 0.30 and spot_price: on-demand with success.
What's your value?

@claudenm
Copy link
Author

Thanks @vmiszczak-teads -- I think I had a missing dependency or wrong version, because it is working now. Closing and sorry for the inconvenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants