Hashicorp Stable yum repository down?

Trying to install Consul on Amazon Linux 2 per the documentation, but it’s failing with the following:

$ sudo yum install -y yum-utils
$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
$ sudo yum -y install consul
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
amzn2-core                                                                                                                           | 3.7 kB  00:00:00
amzn2extra-docker                                                                                                                    | 3.0 kB  00:00:00
amzn2extra-kernel-5.10                                                                                                               | 3.0 kB  00:00:00
hashicorp                                                                                                                            | 1.4 kB  00:00:00
hashicorp/2/x86_64/primary     FAILED
https://rpm.releases.hashicorp.com/AmazonLinux/2/x86_64/stable/repodata/c9a8aa18b37e7a72392290df43e33c79189f8d4c-primary.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://rpm.releases.hashicorp.com/AmazonLinux/2/x86_64/stable/repodata/c9a8aa18b37e7a72392290df43e33c79189f8d4c-primary.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.


 One of the configured repositories failed (Hashicorp Stable - x86_64),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=hashicorp ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable hashicorp
        or
            subscription-manager repos --disable=hashicorp

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=hashicorp.skip_if_unavailable=true

failure: repodata/c9a8aa18b37e7a72392290df43e33c79189f8d4c-primary.xml.gz from hashicorp: [Errno 256] No more mirrors to try.
https://rpm.releases.hashicorp.com/AmazonLinux/2/x86_64/stable/repodata/c9a8aa18b37e7a72392290df43e33c79189f8d4c-primary.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
2 Likes

I see the same error. I’m trying to install Vault as well as Consul on Amazon Linux 2.
Release Archives are incorrectly showing as Operational on https://status.hashicorp.com/

3 Likes

I’m getting the same error too. HashiCorp, please fix this so we can keep developing :slight_smile:

1 Like

I’m also seeing this, FWIW.

1 Like

As mentioned in the Nomad gitter, this affects all yum/rpm packages.
https://rpm.releases.hashicorp.com/fedora/ shows a no such key error, and https://rpm.releases.hashicorp.com/ shows nothing underneath

1 Like

My builds are working again, so the repository looks like it’s back up.