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

HashiCorp APT repository missing Release files #32364

Closed
jethron opened this issue Dec 8, 2022 · 9 comments
Closed

HashiCorp APT repository missing Release files #32364

jethron opened this issue Dec 8, 2022 · 9 comments
Labels
bug new new issue not yet triaged

Comments

@jethron
Copy link

jethron commented Dec 8, 2022

Terraform Version

Terraform v1.3.6
on linux_amd64

Terraform Configuration Files

sudo apt update
deb https://apt.releases.hashicorp.com bookworm main

Debug Output

Ign:11 https://apt.releases.hashicorp.com bookworm InRelease                                                 
...
Err:13 https://apt.releases.hashicorp.com bookworm Release                   
  404  Not Found [IP: 18.67.93.76 443]
...
Reading package lists... Done
E: The repository 'https://apt.releases.hashicorp.com bookworm Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Expected Behavior

Hit:11 https://apt.releases.hashicorp.com bookworm InRelease                                                 

Actual Behavior

404 Not found error for Debian Bookworm.

I found this page which says only up to Bullseye is supported, but that also fails. As do the other distribution names, and the few Ubuntu ones I tried as a random stab. So this list probably also needs updating once the repository is fixed.

That page also mentions sid as an output for lsb_release -cs but that is explicitly not supported (#31816) so that's a bit confusing.

Steps to Reproduce

  1. echo "deb https://apt.releases.hashicorp.com bookworm main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
  2. sudo apt update

Additional Context

No response

References

No response

@jethron jethron added bug new new issue not yet triaged labels Dec 8, 2022
@junland
Copy link

junland commented Dec 8, 2022

I'd also like to add that using focal for Ubuntu does not work as well.

@ryancausey
Copy link

https://rpm.releases.hashicorp.com/ seems to be empty also. For example doing the following doesn't work:

$ yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
Loaded plugins: ovl
adding repo from: https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
grabbing file https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo to /etc/yum.repos.d/hashicorp.repo
Could not fetch/save url https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo to file /etc/yum.repos.d/hashicorp.repo: [Errno 14] HTTPS Error 404 - Not Found

@shankarpentyala07
Copy link

Trying to install terraform on RHEL 8.6 , but says 404

sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
Updating Subscription Management repositories.
Adding repo from: https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
Status code: 404 for https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo (IP: 13.225.41.101)
Error: Configuration of repo failed

@julieerle
Copy link

Thank you for reporting.

HashiCorp Release Engineering has discovered the issue affecting rpm and apt packages. Currently, they are working on a fix.

For updates, please see https://status.hashicorp.com/incidents/gdcwnfwt191c.

@michaelmoreira
Copy link

It looks like you are encountering a "404 Not found" error when trying to access the Debian Bookworm repository. This error indicates that the repository you are trying to access does not exist or is not available.

Based on the debug output you provided, it appears that the repository URL you are using is incorrect. The URL you are using is https://apt.releases.hashicorp.com bookworm Release, but this URL is missing a forward slash (/) between the hostname and the repository name.

To fix this error, you can try updating the repository URL to include the missing slash. The correct URL should be https://apt.releases.hashicorp.com/bookworm Release.

To update the repository URL, you will need to edit the sources.list file on your system. This file is typically located in the /etc/apt/ directory, and contains a list of the repositories that your package manager is configured to use.

To edit the sources.list file, you can use a text editor such as nano or vi. For example, to edit the file using nano, you can run the following command:

Copy code
sudo nano /etc/apt/sources.list
This will open the sources.list file in the nano editor, where you can find the repository URL that you are trying to access and update it to include the missing slash. Once you have made the change, save the file and exit the editor.

After updating the repository URL, you can try running the apt-get update command again to refresh your package list and see if the error persists. If the error continues, you may need

@james-s-w-clark
Copy link

james-s-w-clark commented Dec 9, 2022

https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo also seems to be broken, in a similar timeframe to apt.

Edit: The file just downloaded fine for me from my personal PC. Our CI is still getting a 404 on the file however.

Edit 2: I see @julieerle noted that rpm is affected, thanks!

@mahendra-maplelabs
Copy link

Getting 404 error while trying to install terraform on centos 7 machine.

$ sudo yum -y install terraform
Hashicorp Stable - x86_64                                                                                                               810  B/s | 313  B     00:00
Errors during downloading metadata for repository 'hashicorp':
  - Status code: 404 for https://rpm.releases.hashicorp.com/fedora/8/x86_64/stable/repodata/repomd.xml (IP: 99.84.160.7)
Error: Failed to download metadata for repo 'hashicorp': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

@crw
Copy link
Collaborator

crw commented Dec 9, 2022

Incident is closed per the incident page (#32364 (comment)), closing this issue. Thanks all for the reports!

@crw crw closed this as completed Dec 9, 2022
@github-actions
Copy link

github-actions bot commented Jan 9, 2023

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 Jan 9, 2023
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

9 participants