Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Is VC1S supported at AMS1? #21

Closed
gris-gris opened this issue Aug 7, 2018 · 3 comments
Closed

Is VC1S supported at AMS1? #21

gris-gris opened this issue Aug 7, 2018 · 3 comments

Comments

@gris-gris
Copy link

Is it possible to deploy k8s at VC1S instances?

terraform apply \
-var region=ams1 \
-var arch=x86_64 \
-var server_type=VC1S \
-var nodes=1 \
-var server_type_node=VC1S \
-var weave_passwd=fk43fnk%4$ \
-var docker_version=17.12.0-ce-0-ubuntu
provider.scaleway.organization
  The Organization ID (a.k.a. 'access key') for Scaleway API operations.

  Enter a value: XXXXXXXXXXXXXXXXXx

provider.scaleway.token
  The API key for Scaleway API operations.

  Enter a value: XXXXXXXXXXXXXXXXXXx

data.scaleway_image.xenial: Refreshing state...

Error: Error refreshing state: 1 error(s) occurred:

* data.scaleway_image.xenial: 1 error(s) occurred:

* data.scaleway_image.xenial: data.scaleway_image.xenial: The query returned more than one result. Please refine your query.

@justinclift
Copy link

At a general thought, from the The query returned more than one result. Please refine your query bit it sounds like the problem is in the query not being specific enough, so more results were returned than can be handled.

You'll probably need to hit it with a debugger (or even add a Println() type of thing) to display the returned results so you can figure out what bit needs changing. 😄

@stephenmoloney
Copy link
Collaborator

I think this might work with a newer version of the terraform-scaleway-provider.

@stefanprodan
Copy link
Owner

Closing this as it was a Scaleway Terraform provider bug and not related to this project.

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

No branches or pull requests

4 participants