Closed trevor-vaughan closed 1 year ago
@op-ct I'm 99% sure that the issue is that the epel-modular
material is overriding the AppStream
material (I think).
In a clean installation, when I enable 389-directory-server
then 389-ds-base
installs but the other necessary RPMs are missing. When I run the spec test, everything works properly pointing at AppStream
.
It doesn't seem like pulp
is grabbing the AppStream
389 material.
Tried using bolt-pulp3
to only include the epel-modular
and AppStream
modules but the system hung on Pulp3RpmRepoSlimmer: pagination: 0, total considered: 0/0
Not quite sure yet, but it seems like the repo href being called in the slim-pulp-repo-copy.rb
is not correct for some reason.
The reference is generated in slim_repos_data_for()
.
Digging further:
do_copy_rpms_into_slim_repos
function.conf.epel-modular.slim
repository with the following configuration:
epel-modular:
url: https://dl.fedoraproject.org/pub/epel/8/Modular/x86_64/
modules:
- stream: 389-directory-server:stable
Looks like it may have been an issue with not handling an edge case where there were too few packages to page. However, it's still not downloading the 389DS RPMs
Confirmed the edge case, fix incoming
Continues on with cascading failures from there.
Tried:
CentOS*.repo
filesOutput of
dnf module list