"No provider plugins meet the constraint" with only >= constraints

Terraform
1

Ran into a similar issue, which searching led me to this thread (and a few GH Issues)

I’m getting the following:

No provider "aws" plugins meet the constraint ">= 2.42,>= 2.42,>= 3.38".

$ terraform version
Terraform v0.12.20
$
$ terraform providers
├── provider.aws >= 3.38
...
├── module.alb_sg
│   └── provider.aws >= 2.42
...
├── module.svc_sg
│   └── provider.aws >= 2.42

I’d understand this not working if the constraint was ~> 2.42, however, the it’s using the >= operator, I’m confused why I’m getting this error.

2

Hi @SeanHood,

Unfortunately I don’t have any ready explanation for what you saw here. I wrote a simple configuration that ought to have the same effect in provider installation as yours, albeit without all of the separate modules:

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 2.42, >= 2.42, >= 3.38"
    }
  }
}

Ran terraform init on this with the current version of Terraform (v0.15.5) first, just because that happened to be what I had handy:

 terraform init

Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/aws versions matching ">= 2.42.0, >= 3.38.0"...
- Installing hashicorp/aws v3.44.0...
- Installed hashicorp/aws v3.44.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

That worked, but knowing that there were some quite significant changes to provider installation behavior in Terraform v0.13 I also tried with Terraform v0.12:

$ terraform init

Initializing the backend...

Initializing provider plugins...
- Checking for available provider plugins...
- Downloading plugin for provider "aws" (hashicorp/aws) 3.44.0...


Warning: Provider source not supported in Terraform v0.12

  on provider-version-constraints.tf line 3, in terraform:
   3:     aws = {
   4:       source  = "hashicorp/aws"
   5:       version = ">= 2.42, >= 2.42, >= 3.38"
   6:     }

A source was declared for provider aws. Terraform v0.12 does not support the
provider source attribute. It will be ignored.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

I got a warning here because I was still using the Terraform v0.13 syntax to explicitly select the hashicorp/aws provider, but as the message notes Terraform v0.12 just ignores the source argument and considers only the version, so I don’t expect this to affect the overall behavior aside from emitting that warning.

Given that, I’m not sure what to try next. If you wouldn’t mind sharing your own terraform init output in full – everything including the error message you saw – perhaps something else in the output will give me a clue for something to try next in order to reproduce the problem.