Rhel yum install error for v0.32 enterprise

hi - any suggestions on this error:

-bash-4.2$ EL_VERSION=cat /etc/redhat-release | grep -oE '[0-9]+\.[0-9]+' && \

sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-${EL_VERSION%.*}.noarch.rpm
[sudo] password for pxo22631:
Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, search-disabled-repos, subscription-manager
epel-release-latest-7.noarch.rpm | 15 kB 00:00:00
Examining /var/tmp/yum-root-DiUuIW/epel-release-latest-7.noarch.rpm: epel-release-7-11.noarch
/var/tmp/yum-root-DiUuIW/epel-release-latest-7.noarch.rpm: does not update installed package.
Error: Nothing to do
Uploading Enabled Repositories Report
Loaded plugins: langpacks, product-id, subscription-manager

-bash-4.2$ sudo yum install kong-enterprise-edition-0.32.el7.noarch.rpm --nogpgcheck
Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, search-disabled-repos, subscription-manager

One of the configured repositories failed (Unknown),
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=<repoid> ...

 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 <repoid>
    or
        subscription-manager repos --disable=<repoid>

 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=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
Uploading Enabled Repositories Report
Loaded plugins: langpacks, product-id, subscription-manager
-bash-4.2$

Maybe check your:

/etc/yum.repos.d/

Repos and potentially try what this guy did: https://stackoverflow.com/questions/26734777/yum-error-cannot-retrieve-metalink-for-repository-epel-please-verify-its-path

I solved this issue editing both /etc/yum.repos.d/epel.repo and /etc/yum.repos.d/epel-testing.repo files, commenting all entries starting with mirrorlist=... and uncommenting all the entries starting with baseurl=...

And try

yum clean all

To rid yourself of bad cache entries.

And honestly just try this if you wanna pull and install the first RPM dependency manually

wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
sudo yum install epel-release-latest-7.noarch.rpm

thanks Jeremy - I tried editing epel.repo and so on but couldn’t get it to work - I ended up installing as root using rpm and it worked

1 Like