fedora-infrastructure

#12713 MirrorManager: in move-to-archive, the Modular repo is blocking and should be dropped
Closed: Duplicate by abompard. Opened by abompard.

Closed: Duplicate
Reopen Issue

From @kevin on Matrix:

we need to drop modular from the move to archive job...
Error: Unable to find a directory in [Fedora Archive] for pub/fedora/linux/updates/testing/40/Modular/source/tree

The move-to-archive job currently crashes if the destination repo in the target Archive category does not exist in the database. What should it do in that situation?
1. Ignore the repo and leave it in place? This means that there will be leftovers in the database with repos still in the wrong category
2. Delete the repo instead of moving it. This seems risky if the destination repo doesn't exist for other reasons or hasn't been created by the primary mirror crawler yet.
3. Something else? Leave as is and manually delete the repos from the database before moving? I can write a script to delete repos from the DB to make that easier.

I'm happy to make the change in MirrorManager when decided.

Ref: https://pagure.io/releng/issue/12868

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: dev, high-gain, medium-trouble

Duplicate of the releng issue, closing here.

Metadata Update from @abompard:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)
Metadata
None

dev high-gain medium-trouble

None
None
Normal
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.