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

Error tls: crypto/x509: system root pool is not available on Windows #1384

Closed
ivialex-mcd opened this issue May 21, 2021 · 6 comments · Fixed by #1387
Closed

Error tls: crypto/x509: system root pool is not available on Windows #1384

ivialex-mcd opened this issue May 21, 2021 · 6 comments · Fixed by #1387
Assignees

Comments

@ivialex-mcd
Copy link

ivialex-mcd commented May 21, 2021

Description

After the merge of this pull request 1339, when executing the terraform apply command to create the eks cluster and the managed nodes groups, it gives the following error as shown in the image below.

image

Versions

  • Terraform:

$ terraform -version
Terraform v0.15.0
on windows_amd64

  • Provider(s):

provider registry.terraform.io/hashicorp/aws v3.40.0
provider registry.terraform.io/hashicorp/cloudinit v2.2.0
provider registry.terraform.io/hashicorp/kubernetes v1.13.3
provider registry.terraform.io/hashicorp/local v2.1.0
provider registry.terraform.io/hashicorp/null v3.1.0
provider registry.terraform.io/hashicorp/random v3.1.0
provider registry.terraform.io/hashicorp/template v2.2.0
provider registry.terraform.io/terraform-aws-modules/http v2.4.0

  • Module:

terraform-aws-eks

Reproduction

Steps to reproduce the behavior:
I'm trying to deploy EKS and Nodes Groups using the example launch_templates_with_managed_node_groups as a model.
And I'm using Git Bash to run the terraform commands.

Code Snippet to Reproduce

Example launch_templates_with_managed_node_groups

Expected behavior

Work on both Windows and Linux platforms.

Actual behavior

After I runned the commando terraform apply -auto-approve show this error below:

│ Error: Error tls: crypto/x509: system root pool is not available on Windows

│ on .terraform\modules\eks\cluster.tf line 68, in data "http" "wait_for_cluster":
│ 68: data "http" "wait_for_cluster" {

Terminal Output Screenshot(s)

image

Additional context

N/A

@barryib
Copy link
Member

barryib commented May 21, 2021

Thanks @ivialex-mcd for reporting this issue. I'll try to fix this during the weekend.

@nareshkhatiwada
Copy link

I got same issue

Error: Error tls: crypto/x509: system root pool is not available on Windows

on .terraform\modules\eks\cluster.tf line 68, in data "http" "wait_for_cluster":
68: data "http" "wait_for_cluster" {

@barryib
Copy link
Member

barryib commented May 22, 2021

I just published https://github.com/terraform-aws-modules/terraform-provider-http/releases/tag/v2.4.1 to try to fix the provider issue on Windows.

@ivialex-mcd @nareshkhatiwada @rkinganduril can you please test it with terraform-aws-modules/terraform-provider-http v2.4.1 ?

terraform {
  required_providers {
    http = {
      source = "terraform-aws-modules/http"
      version = "2.4.1"
    }
  }
}

@ivialex-mcd
Copy link
Author

ivialex-mcd commented May 24, 2021

I just published https://github.com/terraform-aws-modules/terraform-provider-http/releases/tag/v2.4.1 to try to fix the provider issue on Windows.

@ivialex-mcd @nareshkhatiwada @rkinganduril can you please test it with terraform-aws-modules/terraform-provider-http v2.4.1 ?

terraform {
  required_providers {
    http = {
      source = "terraform-aws-modules/http"
      version = "2.4.1"
    }
  }
}

Hi @barryib ,

It works for me. But it generated another problem as shown below.

This error had happened with version 15.2.0 of the EKS module. And even upgrading to version 16.1.0 did not solve it. Do you already have any other tickets for this problem?

image

@barryib
Copy link
Member

barryib commented May 24, 2021

Thanks for your feedback. Indeed this is not related to the wait_for_cluster datasource. Please, we can continue to discuss on #1386

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants