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

could not query provider registry for registry.terraform.io/hashicorp/vsphere: failed to retrieve authentication checksums for provider: 404 Not Found #27867

Closed
cpaggen opened this issue Feb 22, 2021 · 10 comments
Labels
bug new new issue not yet triaged

Comments

@cpaggen
Copy link

cpaggen commented Feb 22, 2021

Terraform Version

0.14.4

Terraform Configuration Files

terraform {
  required_providers {
    vsphere = {
      source = "hashicorp/vsphere"
      version = "1.24.3"
    }
  }
}

provider "vsphere" {
  user                 = var.vsphere_user
  password             = var.vsphere_password
  vsphere_server       = var.vsphere_server
  allow_unverified_ssl = true
}

data "vsphere_datacenter" "dc" {
  name = var.datacenter_name
}

Debug Output

�Terraform v0.14.4
Initializing plugins and modules...

Initializing the backend...

Successfully configured the backend "remote"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...

  • Finding hashicorp/vsphere versions matching "1.24.3"...

Error: Failed to install provider

Error while installing hashicorp/vsphere v1.24.3: could not query provider
registry for registry.terraform.io/hashicorp/vsphere: failed to retrieve
authentication checksums for provider: 404 Not Found

Operation failed: failed running terraform init (exit 1)�

More context

This has been running fine for weeks and suddenly stopped. Note that I'm starting my plan from TF cloud; the code is executed on a TF cloud agent. I restarted the agent, rm -rf .terraform.d and that did not help. It just refuses to fetch the checksum for the vsphere provider. The problem started occurring roughly 35 minutes ago (9am PST).

@cpaggen cpaggen added bug new new issue not yet triaged labels Feb 22, 2021
@dsavell
Copy link

dsavell commented Feb 22, 2021

Hey, looks like it could be related to this aswell: #27866

@rrazor
Copy link

rrazor commented Feb 22, 2021

I'm seeing this for hashicorp/aws on at least 3.28.0 and 3.29.0 as well.

@Lasering
Copy link

The urls for providers in the registry were:

registry.terraform.io/hashicorp/vsphere

But now they are:

registry.terraform.io/providers/hashicorp/vsphere

Notice the extra /providers. This is what is causing the error.

@igorescobar
Copy link

Any workaround? 🤔

@punmechanic
Copy link

punmechanic commented Feb 22, 2021

Find the provider in a different .terraform folder on your machine :D unfortunately there's no work around if initializing as terraform will always consult the online provider list

@rrazor
Copy link

rrazor commented Feb 22, 2021

I worked around things by identifying the most recent provider version I had in my .terraform.d/plugin-cache and setting the version in required_providers to exactly that.

@cpaggen
Copy link
Author

cpaggen commented Feb 22, 2021

@rrazor - would you kindly share the exact steps to do that? In my case, I'm starting terraform from tfcloud via an agent running on-prem.

@cpaggen
Copy link
Author

cpaggen commented Feb 22, 2021

Looks like Hashicorp is aware of the issue - https://status.hashicorp.com/

@danieldreier
Copy link
Contributor

Hi! I really appreciate everyone reporting this. The root cause here is an incident in the releases.hashicorp.com and registry infrastructure. I'm going to close this and related issues and consolidate any ongoing discussion into #27872. Please do let us know in that issue if you are still having trouble downloading Terraform or providers.

@ghost
Copy link

ghost commented Mar 25, 2021

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.

@ghost ghost locked as resolved and limited conversation to collaborators Mar 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug new new issue not yet triaged
Projects
None yet
Development

No branches or pull requests

7 participants