https://github.com/stahnma/puppet-module-epel/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

[ravindraaiyer-hcl]

Getting the following error on yum install epel-release. The epel.repo is pointing to the correct GitHub repo. I also added the repo-gpgcheck=0 to epel.repo so it does not worry about checking the gpg keys. but I still get the same error. Seems the repo is having incorrect "repomd.xml".

https://github.com/stahnma/puppet-module-epel/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

Here is the complete output.

yum install epel-release

Loaded plugins: amazon-id, rhui-lb, search-disabled-repos https://github.com/stahnma/puppet-module-epel/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below knowledge base article https://access.redhat.com/articles/1320623 If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.

One of the configured repositories failed (Puppet EPEL Repo), 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=epel ...

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

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

failure: repodata/repomd.xml from epel: [Errno 256] No more mirrors to try. https://github.com/stahnma/puppet-module-epel/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

[rnelson0]

Can you share what code you are using? You seem to be pointed at github for the repo and this module does not do that.

[ravindraaiyer-hcl]

Thanks Rob. You are right. Here is the epel.repo file from the yum.repos.d and it is pointing to the github repo. I copied the code from one of our customer codes and trying to run it on AWS setup through Puppet.

[epel] name=Puppet EPEL Repo baseurl=https://github.com/stahnma/puppet-module-epel enabled=1 repo_gpgcheck=0

What should I point the baseurl to? mayb to the fedoraproject.org url mentioned below? Is there more configuration that is needed apart from this change.?

baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch

metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch

Thank you. Ravindra Aiyer.

---

From: Rob Nelson notifications@github.com Sent: Wednesday, June 19, 2019 5:46 AM To: stahnma/puppet-module-epel Cc: Ravindra Aiyer; Author Subject: Re: [stahnma/puppet-module-epel] https://github.com/stahnma/puppet-module-epel/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found (#85)

Can you share what code you are using? You seem to be pointed at github for the repo and this module does not do that.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fstahnma%2Fpuppet-module-epel%2Fissues%2F85%3Femail_source%3Dnotifications%26email_token%3DALHQTEFUUP726Z4UEPOAXD3P3IFBBA5CNFSM4HZFVDJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYBO5YY%23issuecomment-503508707&data=02%7C01%7Cravindra.aiyer%40hcl.com%7Cd2a4d0eac0934dae175408d6f4a36af0%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636965380050748942&sdata=QsOS6%2F9djmOfQ%2FMzCsIWpgg4EhKxWI4hXCxSixXAcy8%3D&reserved=0, or mute the threadhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALHQTEF2FCPV2LIPTLDX5Q3P3IFBBANCNFSM4HZFVDJQ&data=02%7C01%7Cravindra.aiyer%40hcl.com%7Cd2a4d0eac0934dae175408d6f4a36af0%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636965380050748942&sdata=%2F82JJ1b984dcgAeVNp7ReBnGTEBoSZHvyWyOMmAQfjQ%3D&reserved=0.

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.

[rnelson0]

This github repo isn't a yum repository itself, it's a puppet module to manage repositories. Please see the usage section on how to make use of it properly. Thanks.