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

Workshop won't deploy with Terraform >= 0.10.0 #11

Closed
ajacocks opened this issue Sep 27, 2017 · 10 comments
Closed

Workshop won't deploy with Terraform >= 0.10.0 #11

ajacocks opened this issue Sep 27, 2017 · 10 comments
Assignees

Comments

@ajacocks
Copy link
Contributor

When you try to deploy the workshop with Terraform versions of 0.10.0, or newer, you get the following error, indicating that the required plugins are missing:

TASK [terraform.infra.aws : Terraform apply (build/change infrastructure)] *****
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["terraform", "apply"], "delta": "0:00:00.020314", "end": "2017-09-27 16:09:08.015834", "failed": true, "rc": 1, "start": "2017-09-27 16:09:07.995520", "stderr": "\u001b[31merror satisfying plugin requirements\u001b[0m\u001b[0m", "stderr_lines": ["\u001b[31merror satisfying plugin requirements\u001b[0m\u001b[0m"], "stdout": "\u001b[0m\u001b[1m\u001b[33mPlugin reinitialization required. Please run \"terraform init\".\u001b[0m\n\u001b[33mReason: Could not satisfy plugin requirements.\n\nPlugins are external binaries that Terraform uses to access and manipulate\nresources. The configuration provided requires plugins which can't be located,\ndon't satisfy the version constraints, or are otherwise incompatible.\n\n\u001b[0m\u001b[31m2 error(s) occurred:\n\n* provider.aws: no suitable version installed\n  version requirements: \"(any version)\"\n  versions installed: none\n* provider.template: no suitable version installed\n  version requirements: \"(any version)\"\n  versions installed: none\n\n\u001b[0m\u001b[33mTerraform automatically discovers provider requirements from your\nconfiguration, including providers used in child modules. To see the\nrequirements and constraints from each module, run \"terraform providers\".\n\u001b[0m", "stdout_lines": ["\u001b[0m\u001b[1m\u001b[33mPlugin reinitialization required. Please run \"terraform init\".\u001b[0m", "\u001b[33mReason: Could not satisfy plugin requirements.", "", "Plugins are external binaries that Terraform uses to access and manipulate", "resources. The configuration provided requires plugins which can't be located,", "don't satisfy the version constraints, or are otherwise incompatible.", "", "\u001b[0m\u001b[31m2 error(s) occurred:", "", "* provider.aws: no suitable version installed", "  version requirements: \"(any version)\"", "  versions installed: none", "* provider.template: no suitable version installed", "  version requirements: \"(any version)\"", "  versions installed: none", "", "\u001b[0m\u001b[33mTerraform automatically discovers provider requirements from your", "configuration, including providers used in child modules. To see the", "requirements and constraints from each module, run \"terraform providers\".", "\u001b[0m"]}
        to retry, use: --limit @/home/ajacocks/.ansible-retry/site.retry

The issue is that the default plugin storage directory has changed. Reference this issue: 15705.

@dischord01
Copy link
Contributor

Try clearing out the .terraform folder and run it again. It is probably an older version of Terraform files in the folder.

@ajacocks
Copy link
Contributor Author

This is on a brand new git clone...so it's not that. As soon as I replaced Teraform 0.10.6 with 0.9.11, everything worked.

@dischord01
Copy link
Contributor

Which workshop?

@ajacocks
Copy link
Contributor Author

Ah, I thought that Github noted that...it's openshift_terraform.

@dischord01
Copy link
Contributor

Looks like a terraform bug that gets fixed in the next version. use v0.9.3 for now.

@ecwpz91
Copy link
Contributor

ecwpz91 commented Sep 27, 2017

FYI - https://github.com/ecwpz91/workshopper is meant to replace openshift_terraform, and does not have a dependency on terraform.

@ajacocks
Copy link
Contributor Author

Sounds good, Mike. Why not move it to RedHatGov github, then? I wasn't aware of it.

@ecwpz91
Copy link
Contributor

ecwpz91 commented Sep 30, 2017

@ajacocks It's almost ready.. Meaning, I have a list of TODOs within the repo.

Mainly, I want to implement two more networking options within AWS before turning over a copy to RedHatGov.

Feel free to set up a 1:1 to further discuss the project, I was waiting for the next meeting and did send you an invite to become project owner as well.

@ajacocks
Copy link
Contributor Author

@ecwpz91 Cool...yeah, I saw the invite...just didn't have any time to do anything with it, this week.

@ajacocks
Copy link
Contributor Author

Closed...this was fixed by a recent merge.

matmille pushed a commit that referenced this issue Nov 9, 2019
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

6 participants