Closed Bug 1344054 Opened 9 years ago Closed 9 years ago

Some Bintray Downloads are Failing

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: frank, Unassigned)

Details

(Whiteboard: [SvcOps])

Not all are failing, just some. Unclear if this will be a persistent problem. Logs from a bootstrap script below. ``` #bintray--sbt-rpm - packages by from Bintray [bintray--sbt-rpm] name=bintray--sbt-rpm baseurl=http://dl.bintray.com/sbt/rpm gpgcheck=0 repo_gpgcheck=0 enabled=1 Loaded plugins: priorities, update-motd, upgrade-helper http://dl.bintray.com/sbt/rpm/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 500 Internal Server Error" Trying other mirror. One of the configured repositories failed (bintray--sbt-rpm), 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. Disable the repository, 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 bintray--sbt-rpm 4. 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=bintray--sbt-rpm.skip_if_unavailable=true failure: repodata/repomd.xml from bintray--sbt-rpm: [Errno 256] No more mirrors to try. ```
Whiteboard: [SvcOps]
Seems to be okay. Let's see if any of the jobs fail, and if not we'll close this bug as worksforme.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.