releng

#12204 Fix metalink results for f38 repo
Closed: Fixed with Explanation by kevin. Opened by jlebon.

Closed: Fixed with Explanation
Reopen Issue
  • Describe the issue

Looks like f38 content was finally moved to the archive on the mirrors, but the metalinks still reference the non-archive URLs

$ curl -sL 'https://mirrors.fedoraproject.org/metalink?repo=updates-released-f38&arch=s390x' | grep dl.fedoraproject.org
    <url protocol="https" type="https" location="US" preference="99">https://dl.fedoraproject.org/pub/fedora-secondary/updates/38/Everything/s390x/repodata/repomd.xml</url>
    <url protocol="http" type="http" location="US" preference="99">http://dl.fedoraproject.org/pub/fedora-secondary/updates/38/Everything/s390x/repodata/repomd.xml</url>

vs f37:

$ curl -sL 'https://mirrors.fedoraproject.org/metalink?repo=updates-released-f37&arch=s390x' | grep dl.fedoraproject.org
    <url protocol="https" type="https" location="US" preference="96">https://dl.fedoraproject.org/pub/archive/fedora-secondary/updates/37/Everything/s390x/repodata/repomd.xml</url>
    <url protocol="http" type="http" location="US" preference="96">http://dl.fedoraproject.org/pub/archive/fedora-secondary/updates/37/Everything/s390x/repodata/repomd.xml</url>
  • When do you need this? (YYYY/MM/DD)

Within a couple of days ideally

  • When is this no longer needed or useful? (YYYY/MM/DD)

Hopefully we can drop our dependency on older content soon (see next question).

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

For Bad Reasons We're Trying To Fix, some of our tests in older RHCOS streams use older Fedora repos. Those tests are currently failing. We're going to work in parallel on cleaning up this tech debt.

cc: @abompard

Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble, ops

Ah, MirrorManager's move-to-archive script has probably not been run yet for F38.
It's related to #12185, we need to choose the best way to do that with the new mirrormanager. I don't think it'll take too long, we're almost there.

OK the command is ready, I'm going to run:

ansible-playbook -v /srv/web/infra/ansible/playbooks/manual/mirrormanager-move-to-archive.yml --extra-vars="product='Fedora' version='38'"
Edited by abompard

It failed on the codecs repositories, do those get archived at all?

Note: it's "only" the secondary arches that haven't been archived in MirrorManager, the main ones are returning the archive links in metalink.
I've fixed it for those, but I'm still interested to know if the codecs repo get archived or not :-)
Edited by abompard

Nope, codecs is not archived, but all the old ones are still there. I don't think cisco removes anything from it ever...

Alright, I ignored the Fedora Codecs category. The playbook and script ran fine, the links returned from the curl command are now archive links. Can we close this?

Yep. Lets! Thanks so much for all the work on this...

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

medium-gain medium-trouble ops

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.