View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000304||AlmaLinux-8||-OTHER||public||2022-09-19 15:33||2022-12-02 10:39|
|Summary||0000304: Pulp 3 synchronizations failing because of Advisory issues. ALSA-2022:1762 in particular.|
|Description||"Incoming and existing advisories have the same id and timestamp but different and intersecting package lists, and neither package list is a proper subset of the other. At least one of the advisories is wrong. To allow this behavior, set ALLOW_AUTOMATIC_UNSAFE_ADVISORY_CONFLICT_RESOLUTION = True (q.v.) in your configuration. Advisory id: ALSA-2022:1762"|
I receive the above error while trying to synchronize our Pulp repositories. Even enabling ALLOW_AUTOMATIC_UNSAFE_ADVISORY_CONFLICT_RESOLUTION fails, as the backend PostgreSQL database spits out:
"2022-09-19 15:21:36.593 UTC  ERROR: duplicate key value violates unique constraint "core_artifact_sha256_key"
2022-09-19 15:21:36.593 UTC  DETAIL: Key (sha256)=(dfe49eec7de8a49933ea921f884fac99ea6cd80cb87cbb5de09f1ca7b6ce606b) already exists."
|Steps To Reproduce||Synchronize AlmaLinux 8 BaseOS using Pulp 3.|
|Additional Information||This is a major issue as it prevents the deployment of updates to our systems.|
|Tags||No tags attached.|
Has anyone looked at this? We still receive this failure.
"traceback": " File
\"/usr/local/lib/python3.8/site-packages/pulpcore/tasking/pulpcore_worker.py\", line 445,
result = func(*args, **kwargs)
line 547, in synchronize
repo_version = dv.create() or repo.latest_version()
line 161, in create
File \"/usr/local/lib/python3.8/site-packages/pulpcore/app/models/repository.py\", line
1044, in __exit__
File \"/usr/local/lib/python3.8/site-packages/pulp_rpm/app/models/repository.py\", line
308, in finalize_new_version
File \"/usr/local/lib/python3.8/site-packages/pulp_rpm/app/advisory.py\", line 136, in
to_add, to_remove, to_exclude = resolve_advisory_conflict(
File \"/usr/local/lib/python3.8/site-packages/pulp_rpm/app/advisory.py\", line 261, in
"description": "Incoming and existing advisories have the same id and timestamp but
different and intersecting package lists, and neither package list is a proper subset of
the other. At least one of the advisories is wrong. To allow this behavior, set
ALLOW_AUTOMATIC_UNSAFE_ADVISORY_CONFLICT_RESOLUTION = True (q.v.) in your configuration.
Advisory id: ALSA-2022:1762"
This is from Monday's sync. This appears to still be broken.
||FYI it looks like this was correct when the 8.7 update was pushed out!|
||Hi, this issue is still actual?|