Oracle Linux 8 - Remi Repo Sync Failure

[Uyunifier]

Problem description

Syncing Remi Repo fails with PREPENDED_DIR

Steps to reproduce

1. Try to sync ol8 Repo Remi with Url: http://cdn.remirepo.net/enterprise/8/remi/x86_64/mirror

...

Uyuni version

Information for package Uyuni-Server-release:
---------------------------------------------
Repository     : uyuni-server-stable
Name           : Uyuni-Server-release
Version        : 2024.12-241000.225.1.uyuni5
Arch           : x86_64
Vendor         : openSUSE
Support Level  : Level 3
Installed Size : 1.4 KiB
Installed      : No
Status         : not installed
Source package : Uyuni-Server-release-2024.12-241000.225.1.uyuni5.src
Upstream URL   : https://www.uyuni-project.org/
Summary        : Uyuni Server
Description    : 
    Uyuni lets you efficiently manage physical, virtual,
    and cloud-based Linux systems. It provides automated and cost-effective
    configuration and software management, asset management, and system
    provisioning.

Uyuni proxy version (if used)

uyuni-tools version used to deploy/manage the server or proxy (if relevant)

Useful logs

14:18:57     6756/6758 : wordpress-6.7.1-1.el8.remi.noarch.rpm
14:19:04     6757/6758 : wordpress-6.7.2-1.el8.remi.noarch.rpm
14:19:13     6758/6758 : wkhtmltopdf-opt-0.12.4-3.el8.remi.x86_64.rpm
14:19:14 Filtering packages that failed to download
14:19:14 
14:19:14   Importing packages to DB:
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR
14:19:14 PREPENDED_DIR

Additional information

No response

[dfaltum]

I think this is fixed here: #8916

[agraul]

Thank you for the bug report @Uyunifier! We have had similar issues in the past. I'm adding this to our internal tracker.

@dfaltum that's the same type of error, but #8916 does not fix this. For both errors, the problem is that we look for a configuration value in the wrong place. rhnConfig internally splits the "namespaces" of our config (/etc/rhn/rhn.conf). When we access a config value, we first specify the namespace (called component in the code) and then access the "name" of the the config value, e.g. PREPENDED_DIR. This error occurs when the wrong namespace is used.

[Uyunifier]

Hi :)
any workarround i could implement to get it synced until its fixed in next release?

[m-czernek]

Looking at this issue, I don't believe this is related to a particular repository you're trying to sync. On my test server, I managed to sync the repo without problems multiple times:

...
14:48:56     6765/6768 : unit-1.34.1-1.el8.remi.x86_64.rpm
14:48:57     6766/6768 : unit-1.34.2-1.el8.remi.x86_64.rpm
14:49:09     6767/6768 : wordpress-6.7.2-1.el8.remi.noarch.rpm
14:49:19     6768/6768 : wkhtmltopdf-opt-0.12.4-3.el8.remi.x86_64.rpm
14:49:19 
14:49:19   Importing packages to DB:
14:49:20   Package batch #2 of 339 completed...
14:49:21   Package batch #1 of 339 completed...
...
14:51:27   Linking packages to the channel.
14:51:28     1000 packages linked
...
14:52:00 Sync completed.
14:52:00 Total time: 0:07:07

While I'm looking deeper into the issue, @Uyunifier , I have a few questions:

• Would you be willing to share your /etc/rhn/rhn.conf file? (Note, if you do, please remove any username / password / secret / ... - you can also send it to my [email protected] email, which you can either compose from the name in my profile, or find it in the git log of the uyuni-project/uyuni repository)
• Is the fail consistent? I.e. when you re-try syncing the repository, do you always get this error?
• Can you sync other repositories without issues?