This issue https://pulp.plan.io/issues/5924 was fixed and closed for 3.2.
However we got the the similar errors when sync epel7. Is this a new issue?
"description": "Incoming and existing advisories have the same id and
timestamp but different and intersecting package lists. At least one of them is
wrong. Advisory id: FEDORA-EPEL-2020-1dafb95591",
"traceback": " File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/worker.py\", line
884, in perform_job\n rv = job.perform()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
664, in perform\n self._result = self._execute()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/rq/job.py\", line
670, in _execute\n return self.func(*self.args, **self.kwargs)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/tasks/synchronizing.py\",
line 152, in synchronize\n dv.create()\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/plugin/stages/declarative_version.py\",
line 149, in create\n loop.run_until_complete(pipeline)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulpcore/app/models/repository.py\",
line 782, in __exit__\n repository.finalize_new_version(self)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/models/repository.py\",
line 120, in finalize_new_version\n resolve_advisories(new_version,
previous_version)\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/advisory.py\",
line 65, in resolve_advisories\n previous_advisory, added_advisory\n File
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/pulp_rpm/app/advisory.py\",
line 138, in resolve_advisory_conflict\n raise AdvisoryConflict(_('Incoming
and existing advisories have the same id and '\n"
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list
