Drop modularity from EPEL8. #11292
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
10 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets#11292
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As it was approved by the EPEL Steering Committee, Modularity support is getting retired from EPEL 8.
To complete the retirement, we need some support from releng, specifically in tasks regarding archiving repositories, removing tags and targets, and things like removing epel modules from MBS.
A more comprehensive list of tasks can be found in the corresponding epel ticket
Metadata Update from @phsmoura:
Metadata Update from @humaton:
Koji tags are removed and bodhi should not be pushing anything epel8-modular related.
Metadata Update from @humaton:
🍻
This was only partially completed. Remaining tasks:
epel-modular-8to archive mirrorsPlease re-open this ticket.
Metadata Update from @churchyard:
I syned the content over.
We need to sort out how to get mirrormanager to move now. (like we do for the other eol epel stuff)
CC: @abompard, do you think you can handle the mirrormanager stuff along with the other epel retiring stuff?
Sure! It's a simple database update. It's just the
epel-modular-8repos, for all arches?yeah, that and if there's a testing version of it I suppose...
Should be all of these (grepped out of MM output when you ask for a repo that doesn't exist):
Hey @carlwgeorge!
Can you check and let us know if there's some work left for this? If not we can close this, if there is shoot so we can resolve and fix it.
We still need to update MirrorManager to send requests for EPEL 8 Modular to archive mirrors. For example:
Hey @abompard, can you perform the database update you mentioned to switch these to archive links? It needs to be done for the following repos on all architectures:
Once that is complete, we should be able to delete
/pub/epel/8/Modularand/pub/epel/testing/8/Modularoff the mirrors, then I believe we'll be done and the ticket can be closed.@carlwgeorge I've done it for the first 3, but the
testing-*ones have apparently not been copied to the archive yet.testing/8/Modular should now be copied over to archive.
It is copied but it's apparently not being scanned and loaded in the database. I thought it was because
scan-primary-mirror.tomlwas lacking the appropriate section, so I've added:but it's still not adding those repos to the DB. The scan is done by scan-primary-mirror, which is in Rust, and I don't know how to debug it or make it log more. Any help @adrian ? What info would you need to debug it?
The path does exist on the server:
Metadata Update from @humaton:
Getting this resolved would allow us to drop
/pub/epel/8/Modularand/pub/epel/testing/8/Modularfrom the mirrors, saving 6.5GB of space for every mirror.CC: @adrian any thoughts on how to fix it?
Looking at the database I see a lot of matching directories in the database:
What is the error we are talking about. I guess one of the move-to-archive scripts is not working because of some data missing, right? What is the output of the move-to-archive script? Or how can I run the script to see the error for myself.