[BUG] Error: Failed to query available provider packages

[scheung38]

Cloned this repo and without changing anything other than providing the Digital Ocean key:

export DIGITALOCEAN_TOKEN='Token from Digital Ocean'

Steps to produce:
cd terraform-provider-rke/examples/digitalocean
terraform init

Warning: Interpolation-only expressions are deprecated

on rke.tf line 64, in resource "rke_cluster" "cluster":
64: addons = "${data.template_file.addons.rendered}"

Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider
hashicorp/digitalocean: provider registry registry.terraform.io does not have
a provider named registry.terraform.io/hashicorp/digitalocean

Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider hashicorp/rke:
provider registry registry.terraform.io does not have a provider named
registry.terraform.io/hashicorp/rke

(.venv) ➜ digitalocean git:(master) terraform --version
Terraform v0.14.2

Mac Big Sur: 11.1

[munro]

I'm getting a similar error

I have

variable "do_token" {}

provider "digitalocean" {
  token = var.do_token
}

then when I run

terraform init

I get

Initializing the backend...

Initializing provider plugins...
- Finding latest version of hashicorp/digitalocean...

Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider
hashicorp/digitalocean: provider registry registry.terraform.io does not have
a provider named registry.terraform.io/hashicorp/digitalocean

If you have just upgraded directly from Terraform v0.12 to Terraform v0.14
then please upgrade to Terraform v0.13 first and follow the upgrade guide for
that release, which might help you address this problem.

Did you intend to use digitalocean/digitalocean? If so, you must specify that
source address in each module which requires that provider. To see which
modules are currently depending on hashicorp/digitalocean, run the following
command:
    terraform providers

[munro]

Oh, I figured it out. @scheung38 try adding this

terraform {
  required_providers {
    digitalocean = {
      source = "digitalocean/digitalocean"
    }
  }
}

[aireddy73]

Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider
hashicorp/digitalocean: provider registry registry.terraform.io does not have
a provider named registry.terraform.io/hashicorp/digitalocean

If you have just upgraded directly from Terraform v0.12 to Terraform v0.14
then please upgrade to Terraform v0.13 first and follow the upgrade guide for
that release, which might help you address this problem.

Did you intend to use digitalocean/digitalocean? If so, you must specify that
source address in each module which requires that provider. To see which
modules are currently depending on hashicorp/digitalocean, run the following
command:
terraform providers

I am using terraform 14.5 on Windows10

very simple code ..
provider "digitalocean" {
token = "XXXXXXXX"
}

resource "digitalocean_droplet" "mydroplet" {
image = "ubuntu-18-04-x64"
name = "web-1"
region = "sfo2"
size = "s-1vcpu-1gb"
}

[aireddy73]

It worked after adding below mentioned provider block

terraform {
required_providers {
digitalocean = {
source = "digitalocean/digitalocean"
}
}
}

[asmasud]

Oh, I figured it out. @scheung38 try adding this

terraform {
  required_providers {
    digitalocean = {
      source = "digitalocean/digitalocean"
    }
  }
}

[asmasud]

Thanks it worked for me too

[rawmind0]

Provider examples were created to use terraform 0.12.x. They has not been updated yet, to use tf 0.13.x and registry.terraform.io. We've published a guide to update this provider to tf 0.13.x, https://registry.terraform.io/providers/rancher/rke/latest/docs/guides/upgrade_to_0.13 .

As mentioned, this will make the example works

terraform {
  required_providers {
    digitalocean = {
      source = "digitalocean/digitalocean"
      version = "X.Y.Z"
    }
  }
}

Anyway, PR #272 has been submitted to update DO examples. Once reviewed, it would be merged.

[jadamcraig]

@rawmind0 , Yes, now that you mention it, the issue originally reported by @scheung38 above is actually what started me down the path of working on PR #272 .

I am currently working on a similar example template for Linode. Also, since I'm hearing rumours that RancherOS may soon be abandoned, I'll plan to review the DO example again once DigitalOcean themselves decide which container OS to include in their staff-maintained images. Presently, RancherOS is the only option there, though.

[rawmind0]

@jadamcraig , thanks for working on that PR.

RancherOS may be fine by the moment, but it's arriving to EOL soon, rancher/os#3000 (comment)

[manuelemeka]

terraform {
required_providers {
digitalocean = {
source = "digitalocean/digitalocean"
}
}
}

[air3ijai]

In our case the issue was related to the lack of the required_providers block in the module.

Root module - versions.tf

# Terraform settings
terraform {
  required_version = "~> 1.6"
  required_providers {
    digitalocean = {
      source  = "digitalocean/digitalocean"
      version = "~> 2.0"
    }
  }
}

Child module - modules/doks/versions.tf

# Terraform settings
terraform {
  required_providers {
    digitalocean = {
      source  = "digitalocean/digitalocean"
      version = "~> 2.0"
    }
  }
}

Reference

1. Using a non hashicorp provider in a module
2. Why doesn’t required_providers in a child module inherit declarations from the parent?