#7241 The epel7Server-infra Yum repo is down
Closed: Fixed 5 years ago Opened 5 years ago by mprahl.

  • Describe what you need us to do:

When accessing the epel7Server-infra Yum repo I get a 403 HTTP error:
https://kojipkgs.fedoraproject.org/repos-dist/epel7Server-infra/latest/x86_64/repodata/repomd.xml

  • When do you need this?

Currently, it's just causing our unit tests to fail on MBS PRs, but it'll block us from deployments after the Fedora infra freeze thaws. So no rush, but within the next couple of weeks would be appreciated.

  • When is this no longer needed or useful?

N/A

  • If we cannot complete your request, what is the impact?

Our MBS units tests on PRs continue to fail and we won't be able to deploy MBS after the Fedora Infra freeze thaws.


Fixed.

The problem is that the dist-repos expire after 1 week...
we need to setup a cron job to (re)make them every few days or something.

:rabbit2:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata Update from @mprahl:
- Issue status updated to: Open (was: Closed)

5 years ago

@kevin the issue is back. Could someone from Fedora Infrastructure please take a look at this again?

@mprahl I am working on cron job mentioned by @kevin, see ticket #7246 for more details. The fix can't be implemented right now because infrastructure is in beta freeze and code regenerating dist repos in deployed on one of frozen hosts (bodhi-backend).

For now, as a workaround, you can tag packages to appropriate infra tags to trigger dist repo regeneration, or ask Koji admins to regen it manually.

The repo should be regenerated now.

As @mizdebsk mentioned he is going to put in place a script after our freeze to keep these repos set.

Sorry for the trouble.

:repeat_one:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata