repo.sonatype.com: rpm repository broken

[martin-schlossarek]

Hello,

I don't know if this is the right place, but we use the sonatype rpm repository to sync the rpm packages to our Red Hat Satellite. Unfortunately, the repository cannot be synced anymore since a few days because the primary.xml.gz cannot be found (404).

https://repo.sonatype.com/repository/sonatype-yum-hosted/repodata/repomd.xml:

<repomd xmlns="http://linux.duke.edu/metadata/repo" xmlns:rpm="http://linux.duke.edu/metadata/rpm">
    <revision>1736864206</revision>
    <data type="filelists">
        <checksum type="sha256">e0460fe9231d743d00e0d55d695fae8a665d5e94f6f64d304621e8e2e188665e</checksum>
        <open-checksum type="sha256">afe1194e4db651ea1ff0379b1476eae5c18ad41363c68e56059c671cdca78195</open-checksum>
        <location href="repodata/e0460fe9231d743d00e0d55d695fae8a665d5e94f6f64d304621e8e2e188665e-filelists.xml.gz"/>
        <timestamp>1736864206</timestamp>
        <size>3381</size>
        <open-size>14393</open-size>
    </data>
    <data type="other">
        <checksum type="sha256">0fa1bbe2df9d6a88f2b4896648d9b62e8193e28ad11140fd6dcb01781093dffd</checksum>
        <open-checksum type="sha256">86b29667edf893c145309481f54f36861053594870be9e27d5ce7f3914040888</open-checksum>
        <location href="repodata/0fa1bbe2df9d6a88f2b4896648d9b62e8193e28ad11140fd6dcb01781093dffd-other.xml.gz"/>
        <timestamp>1736864206</timestamp>
        <size>3348</size>
        <open-size>12111</open-size>
    </data>
    <data type="primary">
        <checksum type="sha256">ec07088a61294ccb5ea17e3f96bad1819ab247dec80d48560bc8390b335cee11</checksum>
        <open-checksum type="sha256">ae16ef8cefef8a3244f57d549c8114f205527f639cce93ca208aced85fe46318</open-checksum>
        <location href="repodata/ec07088a61294ccb5ea17e3f96bad1819ab247dec80d48560bc8390b335cee11-primary.xml.gz"/>
        <timestamp>1736864206</timestamp>
        <size>9706</size>
        <open-size>80028</open-size>
    </data>
</repomd>

https://repo.sonatype.com/repository/sonatype-yum-hosted/repodata/ec07088a61294ccb5ea17e3f96bad1819ab247dec80d48560bc8390b335cee11-primary.xml.gz: 404

[awerner]

Other users are also affected by this bug: https://community.sonatype.com/t/yum-group-repositories-not-creating-correct-repomd-xml-files/14157

My own nexus Instance shows the same behaviour, Version 3.76.0. RPM Repositories became completely unusable.

[IMBArator]

Same problem here! Can't use any of the configured RPM repos.

[gnuts]

I can confirm, all RPM repositories are broken with version 3.76.0. :( Other Repos are not affected. Just RPM.

[strony1980]

I can confirm this bug as well.

We recently upgraded Nexus Repository Manager from version 3.74.0-05 to 3.76.0-03 and are experiencing the same issue. However, we performed the upgrade a couple of days ago and only noticed the bug today, likely after an upload to the repository.
Unfortunately, we cannot restore a snapshot because, in the meantime, other teams have uploaded significant amounts of data to other repositories.

I understand that it is not possible to downgrade to a previous version—correct me if I'm wrong.
Is there any workaround to manage this situation until a fix is released?

[IMBArator]

I can confirm this bug as well.

We recently upgraded Nexus Repository Manager from version 3.74.0-05 to 3.76.0-03 and are experiencing the same issue. However, we performed the upgrade a couple of days ago and only noticed the bug today, likely after an upload to the repository. Unfortunately, we cannot restore a snapshot because, in the meantime, other teams have uploaded significant amounts of data to other repositories.

I understand that it is not possible to downgrade to a previous version—correct me if I'm wrong. Is there any workaround to manage this situation until a fix is released?

I didn't find any downgrade possibility either. We are restoring a backup and update to 3.74 for now.

[strony1980]

I can confirm this bug as well.
We recently upgraded Nexus Repository Manager from version 3.74.0-05 to 3.76.0-03 and are experiencing the same issue. However, we performed the upgrade a couple of days ago and only noticed the bug today, likely after an upload to the repository. Unfortunately, we cannot restore a snapshot because, in the meantime, other teams have uploaded significant amounts of data to other repositories.
I understand that it is not possible to downgrade to a previous version—correct me if I'm wrong. Is there any workaround to manage this situation until a fix is released?

I didn't find any downgrade possibility either. We are restoring a backup and update to 3.74 for now.

If I restore a backup, all new files uploaded to Nexus since that time will be lost.
Is there a way to prevent this from happening?
We urgently need a solution to resolve this issue. Is there an expected release date for a fix?