-
Bug
-
Resolution: Done
-
Blocker
-
stream, 6.18.0
-
Phoenix - Content
-
3
-
False
-
libcomps-0.1.23
-
Critical
-
Artemis Sprint 155
-
sat-artemis
-
None
-
None
-
None
-
None
-
Yes
Description of problem:
In automation, when we sync the repository, it occasionally fails with a 'pulp task error' due to missing content.
How reproducible:
Not always
Is this issue a regression from an earlier version:
Yes
Steps to Reproduce:
This issue is difficult to reproduce, so we can review the logs from the CI pipeline failure for further analysis
Sharing a portion of the failure below -
'output': 'No content added.\nTotal steps: 82249/82249\n--------------------------------\nAssociating Content: 39000/39000\nDownloading Artifacts: 0/0\nDownloading Metadata Files: 11/11\nParsed Comps: 68/68\nParsed Modulemd: 926/926\nParsed Modulemd Obsolete: 0/0\nParsed Modulemd-defaults: 49/49\nParsed Packages: 42193/42193\nSkipping Packages: 2/2', 'errors': ['Pulp task error']}, 'cli_example': None, 'start_at': '2025-06-13 16:56:46 UTC', 'available_actions': {'cancellable': False, 'resumable': False}}"
Actual behavior:
Sometimes the content does not sync properly, resulting in a 'pulp task error'.
Expected behavior:
The content should be synchronized properly without any issues.
- relates to
-
SAT-36285 pulpcore worker stuck on parsing specific custom primary.xml metadata
-
- Closed
-