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.
The reason is that latest dist-repo for epel7-infra failed: https://koji.fedoraproject.org/koji/taskinfo?taskID=30438295
Metadata Update from @mizdebsk: - Issue assigned to mizdebsk - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: bodhi
Patch with FBR request sent to infra list.
Metadata Update from @mizdebsk: - Issue priority set to: Waiting on External (was: Waiting on Assignee)
FBR was approved.
Metadata Update from @mizdebsk: - Issue priority set to: Waiting on Assignee (was: Waiting on External)
Fixed.
Metadata Update from @mizdebsk: - Issue close_status updated to: Fixed - Issue priority set to: None (was: Waiting on Assignee) - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.