Good Day, working on setting up some systems for my fellow Dev’s and the REPO for RHEL seems to be giving 404 errors for me.
This is what I am seeing:
failure: repodata/repomd.xml from hashicorp: [Errno 256] No more mirrors to try.
https://rpm.releases.hashicorp.com/RHEL/7Workstation/x86_64/stable/repodata./rempmd.cml: [Errno 14] HTTPS Error 404 - Not Found
I too am getting an error/404 from the Hashicorp repo on RHEL/Rocky 8
Hashicorp Stable - x86_64 4.9 kB/s | 842 B 00:00
Errors during downloading metadata for repository 'hashicorp':
- Status code: 404 for https://rpm.releases.hashicorp.com/RHEL/8/x86_64/stable/repodata/90aae048a9b43f1d85c8c01b4dcf34ac10a2f4e0-primary.xml.gz (IP: 151.101.62.49)
- Status code: 404 for https://rpm.releases.hashicorp.com/RHEL/8/x86_64/stable/repodata/8b6dfeca5a79320267551358c4f85f15dbd558c4-filelists.xml.gz (IP: 151.101.62.49)
Error: Failed to download metadata for repo 'hashicorp': Yum repo downloading error: Downloading error(s): repodata/8b6dfeca5a79320267551358c4f85f15dbd558c4-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/90aae048a9b43f1d85c8c01b4dcf34ac10a2f4e0-primary.xml.gz - Cannot download, all mirrors were already tried without success
Edit: tried setting it up in a Rocky 8 VM, worked fine - looks like just the EL7 repo is broken. For now I can do development work in this VM but will need to install vault on EL7 systems at some point.
I don’t think the distribution name “7Server” is supported by the HashiCorp repository. The documented supported distribution names for RHEL at the time I’m writing this are: 7, 8, 9.
I don’t currently have a RHEL system handy to test with, but I would suggest trying to use “7” instead of “7Server” in the repository URL, to match with what the HashiCorp release engineering team has documented.
Note also that the HashiCorp repository does not carry packages for end-of-life distribution versions. Maintenence support for RHEL 7 ends in June this year, and so the HashiCorp RPM repository is likely to stop offering packages for RHEL 7 shortly afterwards. I suggest planning to upgrade to a newer RHEL release on at least the systems where you are running Terraform.
The HashiCorp release engineering team has recently purged a set of unsupported distribution versions that were previously present.
The Official Packaging Guide seems up-to-date with what’s supported, as far as I can tell. I assume that 7Server was previously included in the repository – probably as a copy of 7, since the Terraform package contents are identical across all distributions anyway – but it has now been removed.
The hashicorp.repo file doesn’t encode any specific release version, but it does include the $releasever substitution, so indeed it will work only if your system replaces $releasever with one of the supported distribution versions. For systems that use unsupported names for that variable, such as 7Server, I suspect you’ll need to manually edit the entry to use just 7 instead to match how the repository is configured.
(I’m just sharing the context I have here. I don’t know anything more than what I’ve mentioned above and am not involved in the maintenance of these repositories.)
I get the why, bit it’s just that the official documentation shares those steps as a way to install Terraform:
sudo yum install -y yum-utils
sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
sudo yum -y install terraform
And the instructions do not work if the machine returns 7server instead of 7 for $releasever. Pretty annoying to remove that repo which breaks all automation.
The issue that this topic was originally discussing was resolved a long time ago and I don’t think it’s helpful to bundle every single problem someone might have with RPM installation into a single long topic that never ends, so I’m going to close this topic.
If you are having trouble installing Terraform – whether from RPM or not – please start a new topic and share all of the context about what you have tried and what’s happened. I know it’s tempting to assume that you have the same problem as someone else who had a similar symptom earlier, but there are many different ways that package installation can fail so it’s important to always start fresh with each new question.