Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EPEL Yum Repo unreliable #1

Open
mjuric opened this issue Nov 25, 2019 · 0 comments
Open

EPEL Yum Repo unreliable #1

mjuric opened this issue Nov 25, 2019 · 0 comments

Comments

@mjuric
Copy link
Member

mjuric commented Nov 25, 2019

EPEL Yum keeps randomly failing when provisioning the hosts; e.g.:

failed: [broker5.do.alerts.wtf] (item=confluent-kafka-2.12) => {"ansible_loop_var": "item", "changed": false, "item": "confluent-kafka-2.12", "msg": "https://download.fedoraproject.org/pub/epel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 302 - Found\nTrying other mirror.\n\n\n One of the configured repositories failed (EPEL YUM repo),\n and yum doesn't have enough cached data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n     1. Contact the upstream for the repository and get them to fix the problem.\n\n     2. Reconfigure the baseurl/etc. for the repository, to point to a working\n        upstream. This is most often useful if you are using a newer\n        distribution release than is supported by the repository (and the\n        packages for the previous distribution release still work).\n\n     3. Run the command with the repository temporarily disabled\n            yum --disablerepo=epel ...\n\n     4. Disable the repository permanently, so yum won't use it by default. Yum\n        will then just ignore the repository until you permanently enable it\n        again or use --enablerepo for temporary usage:\n\n            yum-config-manager --disable epel\n        or\n            subscription-manager repos --disable=epel\n\n     5. Configure the failing repository to be skipped, if it is unavailable.\n        Note that yum will try to contact the repo. when it runs most commands,\n        so will have to try and fail each time (and thus. yum will be be much\n        slower). If it is a very temporary problem though, this is often a nice\n        compromise:\n\n            yum-config-manager --save --setopt=epel.skip_if_unavailable=true\n\nfailure: repodata/repomd.xml from epel: [Errno 256] No more mirrors to try.\nhttps://download.fedoraproject.org/pub/epel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 302 - Found\n", "rc": 1, "results": []}
failed: [broker3.do.alerts.wtf] (item=confluent-kafka-2.12) => {"ansible_loop_var": "item", "changed": false, "item": "confluent-kafka-2.12", "msg": "https://download.fedoraproject.org/pub/epel/7/x86_64/repodata/db5b66e99a11b604baecd9e3bd1ab1593f2bdffedad54947a91293e91cc1fa3d-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found\nTrying other mirror.\nTo address this issue please refer to the below wiki article \n\nhttps://wiki.centos.org/yum-errors\n\nIf above article doesn't help to resolve this issue please use https://bugs.centos.org/.\n\nhttps://download.fedoraproject.org/pub/epel/7/x86_64/repodata/b87dbaab66e2eb84587d260822ec1f4a0ea5235aa6d079d97fe97d08b9315c16-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found\nTrying other mirror.\nhttps://download.fedoraproject.org/pub/epel/7/x86_64/repodata/db5b66e99a11b604baecd9e3bd1ab1593f2bdffedad54947a91293e91cc1fa3d-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found\nTrying other mirror.\nhttps://download.fedoraproject.org/pub/epel/7/x86_64/repodata/db5b66e99a11b604baecd9e3bd1ab1593f2bdffedad54947a91293e91cc1fa3d-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found\nTrying other mirror.\n\n\n One of the configured repositories failed (EPEL YUM repo),\n and yum doesn't have enough cached data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n     1. Contact the upstream for the repository and get them to fix the problem.\n\n     2. Reconfigure the baseurl/etc. for the repository, to point to a working\n        upstream. This is most often useful if you are using a newer\n        distribution release than is supported by the repository (and the\n        packages for the previous distribution release still work).\n\n     3. Run the command with the repository temporarily disabled\n            yum --disablerepo=epel ...\n\n     4. Disable the repository permanently, so yum won't use it by default. Yum\n        will then just ignore the repository until you permanently enable it\n        again or use --enablerepo for temporary usage:\n\n            yum-config-manager --disable epel\n        or\n            subscription-manager repos --disable=epel\n\n     5. Configure the failing repository to be skipped, if it is unavailable.\n        Note that yum will try to contact the repo. when it runs most commands,\n        so will have to try and fail each time (and thus. yum will be be much\n        slower). If it is a very temporary problem though, this is often a nice\n        compromise:\n\n            yum-config-manager --save --setopt=epel.skip_if_unavailable=true\n\nfailure: repodata/db5b66e99a11b604baecd9e3bd1ab1593f2bdffedad54947a91293e91cc1fa3d-primary.sqlite.bz2 from epel: [Errno 256] No more mirrors to try.\nhttps://download.fedoraproject.org/pub/epel/7/x86_64/repodata/db5b66e99a11b604baecd9e3bd1ab1593f2bdffedad54947a91293e91cc1fa3d-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found\n", "rc": 1, "results": []}

It's likely this is due to unreliable mirrors. Rather than letting it pick the mirror, we should change the repo config to point to a reliable mirror (like we do for CentOS base).

Current workaround: rerun the playbook many times, until it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant