Description of problem: Capsule Sync fails with below error, Error: It is not possible to add more than one advisory with the same id to a repository version. Affected advisories: FEDORA-EPEL-2021-6a6f32df5b,FEDORA-EPEL-2021-95153b56f6,FEDORA-EPEL-2022-ba3a353080,FEDORA-EPEL-2021-7423187914,FEDORA-EPEL-2021-2dd13f6ef4,FEDORA-EPEL-2022-c73561a49d,FEDORA-EPEL-2022-b3c1fe1949,FEDORA-EPEL-2021-2b6cb932e4,FEDORA-EPEL-2021-ec819ced94,FEDORA-EPEL-2022-b97efcd687,FEDORA-EPEL-2021-a1ec463301,FEDORA-EPEL-2021-6f281e9938,FEDORA-EPEL-2022-bca867d80a,FEDORA-EPEL-2021-d6e8e98189,FEDORA-EPEL-2021-c69de4d91a,FEDORA-EPEL-2022-568a1eb67d,FEDORA-EPEL-2021-aef67085da,FEDORA-EPEL-2021-162e554c6c,FEDORA-EPEL-2022-ac857a2b3b,FEDORA-EPEL-2021-9807ab7be4,FEDORA-EPEL-2021-cf45baf94d,FEDORA-EPEL-2021-77afb66b60,FEDORA-EPEL-2021-fec75b45df,FEDORA-EPEL-2021-bb1cf3150f,FEDORA-EPEL-2019-dd9e038712,FEDORA-EPEL-2021-90700253a8,FEDORA-EPEL-2021-77d452c188,FEDORA-EPEL-2022-04da0327c7,FEDORA-EPEL-2022-6c854bb52f,FEDORA-EPEL-2022-673d6fb241,FEDORA-EPEL-2021-ef6f185804,FEDORA-EPEL-2021-cae339ac16,FEDORA-EPEL-2022-cd2d056fd2,FEDORA-EPEL-2021-8391cd1abf,FEDORA-EPEL-2021-82b601cdc1,FEDORA-EPEL-2021-3fa01dac69,FEDORA-EPEL-2022-f153f686b8,FEDORA-EPEL-2021-144ba84404,FEDORA-EPEL-2022-2c11373be4,FEDORA-EPEL-2021-bb1dd0a552,FEDORA-EPEL-2021-1b387a86a0,FEDORA-EPEL-2021-d646b00c02,FEDORA-EPEL-2021-72e54715a5,FEDORA-EPEL-2022-3d64d4ef0a,FEDORA-EPEL-2021-4ee71938f8,FEDORA-EPEL-2022-ffc71d49e6,FEDORA-EPEL-2021-a0cdefb061,FEDORA-EPEL-2022-3b5489f94d,FEDORA-EPEL-2021-e111f18a26,FEDORA-EPEL-2021-7d6528d3c4,FEDORA-EPEL-2018-12b65c3a15,FEDORA-EPEL-2021-e53c3c1910,FEDORA-EPEL-2021-1650a2850e,FEDORA-EPEL-2021-4880e15b01,FEDORA-EPEL-2022-f37ca1b24a,FEDORA-EPEL-2021-dedf0dccfa,FEDORA-EPEL-2021-105556b7a0,FEDORA-EPEL-2021-f08778a753,FEDORA-EPEL-2021-1a59ba90e8,FEDORA-EPEL-2021-2f17d3b42f,FEDORA-EPEL-2021-d7e1791efa,FEDORA-EPEL-2022-9a459a9ba6,FEDORA-EPEL-2021-b27e4f19bd,FEDORA-EPEL-2022-e8f3b44948,FEDORA-EPEL-2022-ec54a85a5b,FEDORA-EPEL-2022-cfce1b546f,FEDORA-EPEL-2021-39fbf1bab9,FEDORA-EPEL-2021-25d5f28b97,FEDORA-EPEL-2022-c45b532db6,FEDORA-EPEL-2021-38471ada32,FEDORA-EPEL-2021-7732dd9053,FEDORA-EPEL-2021-f005e1b879,FEDORA-EPEL-2021-0cd46dc751,FEDORA-EPEL-2022-f1cbc0cb0a,FEDORA-EPEL-2021-b5bb89aebd,FEDORA-EPEL-2021-2f60663947,FEDORA-EPEL-2021-362a4a8324,FEDORA-EPEL-2021-103f7694fe,FEDORA-EPEL-2021-7845aa4c10,FEDORA-EPEL-2022-6733448ee2,FEDORA-EPEL-2022-2d515d4692,FEDORA-EPEL-2021-17106efc3f,FEDORA-EPEL-2021-42e3c821ab,FEDORA-EPEL-2021-00c215e1cb,FEDORA-EPEL-2021-bc5c979583,FEDORA-EPEL-2022-43c293ec91,FEDORA-EPEL-2022-3fa6022ee7,FEDORA-EPEL-2021-9998b1ae2a,FEDORA-EPEL-2016-42ecf5c111,FEDORA-EPEL-2021-bc5821ce86,FEDORA-EPEL-2021-abcb0bf762,FEDORA-EPEL-2021-0f4be3d7d2,FEDORA-EPEL-2021-d0a0c90fc6,FEDORA-EPEL-2021-d5e825b208,FEDORA-EPEL-2021-0fdc753583,FEDORA-EPEL-2021-ee8a110aeb,FEDORA-EPEL-2022-9065800cb5,FEDORA-EPEL-2021-0dfa66b9b1,FEDORA-EPEL-2021-96910d4652,FEDORA-EPEL-2019-ab6823fce4,FEDORA-EPEL-2021-00cbdaabb8,FEDORA-EPEL-2022-0fa6370195,FEDORA-EPEL-2021-8aa3e092da,FEDORA-EPEL-2021-d2dc3d28aa,FEDORA-EPEL-2021-59fb84dd86,FEDORA-EPEL-2021-f126598b15,FEDORA-EPEL-2020-01c60e3b5c,FEDORA-EPEL-2021-c958eae61d,FEDORA-EPEL-2020-580c53dfc3,FEDORA-EPEL-2021-ca3f5ea562,FEDORA-EPEL-2022-999767994f. Could not lookup a publication_href for repo 9813 Version-Release number of selected component (if applicable): Satellite 6.10.7 How reproducible: While executing below command on customer infrastructure # hammer capsule content synchronize --id 3 --lifecycle-environment-id 31 [...................................................................................................................................................................................] [100%] Error: It is not possible to add more than one advisory with the same id to a repository version. Steps to Reproduce: 1. Tried updating satellite version to 6.10.7 from 6.10.6, issue still persists 2. 3. Actual results: Expected results: Additional info:
Patch now available for 6.12, let me know if it is still strongly needed for 6.11 as it won't backport cleanly, we would need to adapt it.
Removing Triaged keyword to go back through high-level triage for the proposed releases. Dropped the proposed 6.13.0, since that release has GA'ed.
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 (Important: Satellite 6.14 security and bug fix 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:6818