No module metadata when using yum proxy repositories

[yeradd12]

• What problem are you trying to solve?

I want to use Nexus Repository OSS to proxy Rocky yum repositories (for example Appstream) but Nexus doesn't create/support module metadata and there are issues when installing some packages. When executing dnf module list I get empty list. I'm looking for a way around this problem, I'm wondering if it's possible to somehow generate metadata manually or fix it in some other way.

One example is that when I'm using proxy repository I cannot install docker because module container-tools isn't visble for packet manager.

• Do you have a workaround you are using at present?

No, I am looking for one.

• What feature or behavior is this required for?

To install some packages which use modules feature from RHEL.

• How could we solve this issue? (Not knowing is okay!)

I think the problem is that Nexus does not generate a file module.yaml.gz in repodata? I'm not sure but that is my guess.

• Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

Nexus Repository OSS 3.53.1-02 on Rocky Linux 9.2

[nblair]

Thanks @yeradd12 for opening an issue. We aren't familiar with Rocky linux, so this is a new area for us. We'll keep this open to gauge demand and interest from the community.

[hartmannm]

I experience the same problem with almalinux

[yeradd12]

I experience the same problem with almalinux

I think this problem affects all derivatives of Red Hat 8+ as all of them use module functionality.

[hartmannm]

I experience the same problem with almalinux
I think this problem affects all derivatives of Red Hat 8+ as all of them use module functionality.

Do you plan add support for RHEL 8+ and when? CentOS is reaching eol and many companies will switch to alternatives.

[DanyPops]

Same issue. Since Nexus3 changed how files are stored it's trickier to create a script as workaround.
@nblair https://github.com/rpm-software-management/modulemd-tools this is the tool I have used to create the metadata previously.

[slhotellier]

Same use for me on RHEL8 and Oracle Linux 8.
I can't do "yum update" after installing some fonctionality like "cpan" that use module mode to download updates.

[905839698]

Same use for me on rockylinux9

[hojeonghan]

I have a same problem on rockylinux9 and almalinux9.

The error log is "Error: Failed to download metadata for repo 'baseos': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried" on rockylinux9 and almalinux9.

@nblair
Do you have any plan to support centOS 8+ ?
Can I know when will you support centOS 8+ ?

[anthonyeleven]

This happens to me with Rocky 8.9 and 'yum install ruby'

[hartmannm]

Just switched to pulp. bye nexus

[wahello]

Any idea to this issue?

[anthonyeleven]

Sonotype support eventually clued me in.

They have no plans to generate this wacky metadata, but there is a raw repository type that just serves up the data as-is, like a regular static web site. For local snapshots of Linux package repositories, this does the job, and avoids the manifold shortcomings of a proxy repository / group.

Use repoclone to snag an upstream snapshot then nexus3-cli to recursively stuff it into Nexus.

[wahello]

Just switched to pulp. bye nexus

I deployed pulp, and have a problem.
Did you have such problem?

[FredPraca]

Using Puppet as configuration system and switched to CentOS 9-stream, I'm also definitely stuck with the same problem.
And of course, central IT won't open the access to Internet for these machines...

[ihatethecloud]

Bummer.... I've been playing with nexus for the past 3 days and was very excited. This is such a show stopper because I heavy rely on modular packages, as probably most of the EL8+ users do.