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 (Critical: Satellite 6.11.5 Async Security Update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:1151
Unfortunately, the customer in case 03449566 report that they still have this issue after patching their Satellite 6.11 server. They re-applied the workaround in KCS article 5960501 and it worked (again), but they would like to avoid having to apply this fix every time they patch their Satellite server.
(In reply to Jessica Richards from comment #10) > Unfortunately, the customer in case 03449566 report that they still have > this issue after patching their Satellite 6.11 server. They re-applied the > workaround in KCS article 5960501 and it worked (again), but they would like > to avoid having to apply this fix every time they patch their Satellite > server. Just one (minor) scenario was fixed by this bug - when multiple repos of the same 3rd party product are concurrently updated, either repo might disappear at clients (few days later). The original bugzilla is not yet fixed as we dont know the reproducer for the generic issue (yet..?).
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days