Description of problem:
RHEL8 HBT repo sync is failed to sync module streams. This is happening with currently with repo 'Red Hat Enterprise Linux 8 for x86_64 - AppStream HTB RPMs'.
Works well with repo 'Red Hat Enterprise Linux 8 for x86_64 - AppStream HTB Kickstart'
Version-Release number of selected component (if applicable):
Not always only the first time, but module streams are never shown
Steps to Reproduce:
1.Upload the RHEL8 manifest with HBT
2. Add repos 'Red Hat Enterprise Linux 8 for x86_64 - AppStream HTB Kickstart' and 'Red Hat Enterprise Linux 8 for x86_64 - AppStream HTB RPMs'
3. now sync the repos.
Syncing for repo 'Red Hat Enterprise Linux 8 for x86_64 - AppStream HTB RPMs'
failed for module stream with an error
Sync should work and module stream count should be displayed
PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "katello_module_stream_artifacts_name_mod_stream_id_uniq"
DETAIL: Key (module_stream_id, name)=(213, libsodium-static-0:1.0.16-4.el8+2111+bbd4edaa.x86_64) already exists.
: INSERT INTO "katello_module_stream_artifacts" ("module_stream_id", "name", "created_at", "updated_at") VALUES ($1, $2, $3, $4) RETURNING "id"
Created attachment 1508262 [details]
I was able to find a manifest that works, though it had the actual RHEL8 beta rather than the HTB.
I tried syncing with both "Red Hat Enterprise Linux 8 for x86_64 - AppStream Beta Kickstart" and "Red Hat Enterprise Linux 8 for x86_64 - AppStream Beta RPMs". The sync tasks completed successfully.
If you try again with the actual beta's do you see the same issue?
I tried the HTB repos upstream and these both synced correctly:
Red Hat Enterprise Linux 8 for x86_64 - AppStream HTB Kickstart
Red Hat Enterprise Linux 8 for x86_64 - AppStream HTB RPMs
We just branched katello 3.10, which (iiuc) will be the base for the 6.5 builds. I'm guessing a change that will be in katello 3.10 is not in 3.9 (which 6.5 builds are currently based on).
Can we check this again once the Satellite 6.5 builds are based on Katello 3.10? I can look further if that still fails, but since upstream is so close to 6.5 builds right now, it should be fixed in the upcoming Satellite builds.
*** Bug 1644007 has been marked as a duplicate of this bug. ***
Verified on Satellite with Snap 6.5.7 version. Repos are getting synced successfully. The issue is fixed now.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.