As of January 10th, 2024, HashiCorp no longer publishes packages of our products for end-of-life (EoL) distributions to our production packaging sites and going forward will migrate EoL versions to our new archive site. HashiCorp no longer supports versions of Linux operating systems that have reached EoL status.
These packages will be moved to the new Linux package archive site where users can continue to download them. Use these packages at your own risk. Please find more information regarding this changes in our recent blog post.
*** RHEL/7 and Debian/Buster will be archived at the end of July, 2024 ***
General FAQ
Q: Is this applicable to all HashiCorp products?
A: Yes, this is applicable to all HashiCorp Products.
Q: Why is this happening?
A: To improve release times, increase stability of the release pipeline, and increase ease of maintainability.
Q: How will this affect us?
A: After January 10th, 2024, users will no longer be able to download HashiCorp products using Package Manager on an EoL OS.
Q: What should we do if we are using EoL OS?
A: While you are still able to manually download the product binary from the archive site, we highly recommend that you upgrade to the supported versions of your Operating System.
Q: Is there a workaround if we choose to continue using EoL OS?
A: If you choose to continue using EoL Linux distribution, you can manually download the product binary from our archive site. Please be aware that HashiCorp will not be liable for any issues that arise with the EoL packages on the archive site.
Q: Will moving EoL versions to the archive site become a regular thing?
A: Yes. This process will become a regular occurrence when a distribution version reaches EoL status. We will follow the EoL cycles that distribution maintainers have set up for their distributions.
Q: What OS versions are impacted by this change? ***Updated***
A: As of this writing, below are the current list of impacted versions:
Fedora: 29, 30, 31, 32, 33, 34, 35, 36, and 37
Ubuntu: Eoan, Hirsute, Impish, Groovy, and Kinetic
Debian: Jessie, Stretch, Buster (Will be archived at the end of July, 2024 )
Special case: RHEL
Systems will need to be updated to use the major versions of Red Hat Enterprise Linux (RHEL) (7, 8, and 9) see our Official Packaging Guide for the appropriate hashicorp.repo configuration. While they are not EoL versions, as part of this effort we are also removing the minor version aliases of RHEL, which include:
7Server, 7Workstation, 7.x , 8.1, 8.2, and 8.3
Q: What is the best approach to upgrade our underlying Operating System with minimal downtime?
A: Please make sure you have data backup for all HashiCorp products. If you are a Vault or Consul user, please refer to the product specific FAQ regarding upgrades.
Vault FAQ
Q: What is the best approach to perform underlying OS maintenance with minimal downtime?
A: The process of upgrading the OS is similar to the process of upgrading Vault. Please find more information regarding Vault upgrade SOP in our documentation here.
Consul FAQ
Q: What is the best approach to perform underlying OS maintenance with minimal downtime?
A: Before starting an OS upgrade, please make sure you have Consul data backup. To avoid downtime, please make sure you are able to maintain the quorum. Check the current leader and start upgrading the host OS on one of the non-leader nodes in rotating fashion. From there, please follow our general upgrade process.
