Drop modularity from EPEL8. #11292

Open
opened 2023-02-16 03:43:08 +00:00 by dherrera · 21 comments
Contributor

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

As it was [approved by the EPEL Steering Committee](https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/GYX7BNBGIUJ53CGOCKWECWV3ZDI5DQUM/), 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](https://pagure.io/epel/issue/198)

Metadata Update from @phsmoura:

  • Issue tagged with: low-gain, low-trouble, ops
**Metadata Update from @phsmoura**: - Issue tagged with: low-gain, low-trouble, ops
Owner

Metadata Update from @humaton:

  • Issue assigned to humaton
**Metadata Update from @humaton**: - Issue assigned to humaton
Owner

Koji tags are removed and bodhi should not be pushing anything epel8-modular related.

Koji tags are removed and bodhi should not be pushing anything epel8-modular related.
Owner

Metadata Update from @humaton:

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

🍻

:beers:
Contributor

This was only partially completed. Remaining tasks:

Please re-open this ticket.

This was only partially completed. Remaining tasks: - archive the repo content (copy https://dl.fedoraproject.org/pub/epel/8/Modular/ to https://archive.fedoraproject.org/pub/archive/epel/8/Modular/) - update MirrorManager to send requests for `epel-modular-8` to archive mirrors Please re-open this ticket.
Contributor

Metadata Update from @churchyard:

  • Issue status updated to: Open (was: Closed)
**Metadata Update from @churchyard**: - Issue status updated to: Open (was: Closed)
Owner

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)

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)
Owner

CC: @abompard, do you think you can handle the mirrormanager stuff along with the other epel retiring 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-8 repos, for all arches?

Sure! It's a simple database update. It's just the `epel-modular-8` repos, for all arches?
Owner

yeah, that and if there's a testing version of it I suppose...

yeah, that and if there's a testing version of it I suppose...
Contributor

Should be all of these (grepped out of MM output when you ask for a repo that doesn't exist):

# repo=epel-modular-8&arch=aarch64
# repo=epel-modular-8&arch=ppc64le
# repo=epel-modular-8&arch=s390x
# repo=epel-modular-8&arch=x86_64
# repo=epel-modular-debug-8&arch=aarch64
# repo=epel-modular-debug-8&arch=ppc64le
# repo=epel-modular-debug-8&arch=s390x
# repo=epel-modular-debug-8&arch=x86_64
# repo=epel-modular-source-8&arch=source
# repo=testing-modular-debug-epel8&arch=aarch64
# repo=testing-modular-debug-epel8&arch=ppc64le
# repo=testing-modular-debug-epel8&arch=s390x
# repo=testing-modular-debug-epel8&arch=x86_64
# repo=testing-modular-epel8&arch=aarch64
# repo=testing-modular-epel8&arch=ppc64le
# repo=testing-modular-epel8&arch=s390x
# repo=testing-modular-epel8&arch=x86_64
# repo=testing-modular-source-epel8&arch=source
Should be all of these (grepped out of MM output when you ask for a repo that doesn't exist): ``` # repo=epel-modular-8&arch=aarch64 # repo=epel-modular-8&arch=ppc64le # repo=epel-modular-8&arch=s390x # repo=epel-modular-8&arch=x86_64 # repo=epel-modular-debug-8&arch=aarch64 # repo=epel-modular-debug-8&arch=ppc64le # repo=epel-modular-debug-8&arch=s390x # repo=epel-modular-debug-8&arch=x86_64 # repo=epel-modular-source-8&arch=source # repo=testing-modular-debug-epel8&arch=aarch64 # repo=testing-modular-debug-epel8&arch=ppc64le # repo=testing-modular-debug-epel8&arch=s390x # repo=testing-modular-debug-epel8&arch=x86_64 # repo=testing-modular-epel8&arch=aarch64 # repo=testing-modular-epel8&arch=ppc64le # repo=testing-modular-epel8&arch=s390x # repo=testing-modular-epel8&arch=x86_64 # repo=testing-modular-source-epel8&arch=source ```
Owner

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.

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.
Contributor

We still need to update MirrorManager to send requests for EPEL 8 Modular to archive mirrors. For example:

carl ~ 
❯ curl -s 'https://mirrors.fedoraproject.org/metalink?arch=x86_64&repo=testing-modular-epel8' | grep -m 1 url
    <url protocol="http" type="http" location="US" preference="100">http://mirrors.sonic.net/epel/testing/8/Modular/x86_64/repodata/repomd.xml</url>

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:

  • epel-modular-8
  • epel-modular-source-8
  • epel-modular-debug-8
  • testing-modular-epel8
  • testing-modular-source-epel8
  • testing-modular-debug-epel8

Once that is complete, we should be able to delete /pub/epel/8/Modular and /pub/epel/testing/8/Modular off the mirrors, then I believe we'll be done and the ticket can be closed.

We still need to update MirrorManager to send requests for EPEL 8 Modular to archive mirrors. For example: ``` carl ~ ❯ curl -s 'https://mirrors.fedoraproject.org/metalink?arch=x86_64&repo=testing-modular-epel8' | grep -m 1 url <url protocol="http" type="http" location="US" preference="100">http://mirrors.sonic.net/epel/testing/8/Modular/x86_64/repodata/repomd.xml</url> ``` 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: - epel-modular-8 - epel-modular-source-8 - epel-modular-debug-8 - testing-modular-epel8 - testing-modular-source-epel8 - testing-modular-debug-epel8 Once that is complete, we should be able to delete `/pub/epel/8/Modular` and `/pub/epel/testing/8/Modular` off 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.

@carlwgeorge I've done it for the first 3, but the `testing-*` ones have apparently not been copied to the archive yet.
Owner

testing/8/Modular should now be copied over to archive.

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.toml was lacking the appropriate section, so I've added:

[[repository_mapping]]
regex="pub/(archive/)?epel/testing/[\\d]+/Modular/.*"
prefix="testing-modular-epel"

[[repository_aliases]]
from="testing-modular-epel-debug-"
to="testing-modular-debug-epel"

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:

$ ls /srv/pub/archive/epel/testing/8/Modular/
aarch64  ppc64le  s390x  source  SRPMS  state  x86_64
It is copied but it's apparently not being scanned and loaded in the database. I thought it was because `scan-primary-mirror.toml` was lacking the appropriate section, so I've added: ``` [[repository_mapping]] regex="pub/(archive/)?epel/testing/[\\d]+/Modular/.*" prefix="testing-modular-epel" [[repository_aliases]] from="testing-modular-epel-debug-" to="testing-modular-debug-epel" ``` but it's still not adding those repos to the DB. The scan is done by [scan-primary-mirror](https://github.com/adrianreber/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: ``` $ ls /srv/pub/archive/epel/testing/8/Modular/ aarch64 ppc64le s390x source SRPMS state x86_64 ```
Owner

Metadata Update from @humaton:

  • Assignee reset
**Metadata Update from @humaton**: - Assignee reset
Contributor

Getting this resolved would allow us to drop /pub/epel/8/Modular and /pub/epel/testing/8/Modular from the mirrors, saving 6.5GB of space for every mirror.

Getting this resolved would allow us to drop `/pub/epel/8/Modular` and `/pub/epel/testing/8/Modular` from the mirrors, saving 6.5GB of space for every mirror.
Owner

CC: @adrian any thoughts on how to fix it?

CC: @adrian any thoughts on how to fix it?

Looking at the database I see a lot of matching directories in the database:

mirrormanager2=> select count(id) from directory where name like '%archive%testing%/8/Modular%';
 count 
-------
   130
(1 row)

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.

Looking at the database I see a lot of matching directories in the database: ``` mirrormanager2=> select count(id) from directory where name like '%archive%testing%/8/Modular%'; count ------- 130 (1 row) ``` 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.
patrikp added this to the Backlog project 2026-04-16 08:43:11 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
10 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
releng/tickets#11292
No description provided.