Failed sync task with subtasks still in running state

Problem:
Failed sync task with subtasks still in running state
Expected outcome:
All subtasks are in failed state.

Pulpcore version:
3.22.4

Pulp plugins installed and their versions:
pulp-ansible 0.16.1
pulp-cli 0.19.0
pulp-deb 2.20.2
pulp-file 1.12.0
pulp-glue 0.19.0
pulp-rpm 3.19.3
pulp-rpm-client 3.19.3
pulpcore 3.22.4
pulpcore-client 3.22.4

Operating system - distribution and version:
rhel 8.6

Other relevant data:
Should all subtask in the failed state is the main sync process fails? Just want make sure this is an expected behavior and won’t cause any issue in the future.

{
“pulp_href”: “/pulp/api/v3/tasks/1ade038b-45d0-4430-be0c-8149faaca333/”,
“pulp_created”: “2023-05-01T19:45:19.721270Z”,
“state”: “failed”,
“name”: “pulp_rpm.app.tasks.synchronizing.synchronize”,
“logging_cid”: “f9df4522152d4dccbf1d9231a5775ed0”,
“started_at”: “2023-05-01T20:13:48.412285Z”,
“finished_at”: “2023-05-04T01:06:07.956131Z”,
“error”: {
“reason”: “Aborted during worker shutdown.”
},
“worker”: null,
“parent_task”: null,
“child_tasks”: [],
“task_group”: null,
“progress_reports”: [
{
“message”: “Skipping Packages”,
“code”: “sync.skipped.packages”,
“state”: “completed”,
“total”: 0,
“done”: 0,
“suffix”: null
},
{
“message”: “Parsed Packages”,
“code”: “sync.parsing.packages”,
“state”: “completed”,
“total”: 86,
“done”: 86,
“suffix”: null
},
{
“message”: “Downloading Metadata Files”,
“code”: “sync.downloading.metadata”,
“state”: “completed”,
“total”: null,
“done”: 4,
“suffix”: null
},
{
“message”: “Downloading Artifacts”,
“code”: “sync.downloading.artifacts”,
“state”: “running”,
“total”: null,
“done”: 83,
“suffix”: null
},
{
“message”: “Associating Content”,
“code”: “associating.content”,
“state”: “running”,
“total”: null,
“done”: 0,
“suffix”: null
}
],
“created_resources”: [],
“reserved_resources_record”: [
“/pulp/api/v3/repositories/rpm/rpm/b694e4fa-514f-49d3-bdfa-4cde489d0649/”,
“shared:/pulp/api/v3/remotes/rpm/rpm/db203b58-8c5a-4990-912a-605773cc675d/”
]

Technically these are not subtasks, but progress reports of the one task. There is another concept of a parent task which renders tasks as subtasks and a concept of task groups, but not here.
These progress reports are there to report on the progress of different aspects of the same task (as in one item of execution). With the task canceled/aborted for whatever reason, all these progress reports loose their scope. They now merely show the status of the task right before the moment of it’s violent end.
If you still think we should mark them as failed/canceled along with the task for consistency and less user confusion, please file an issue. But as a whole, I can assure you this is not a data consistency issue.

1 Like

Existing report here https://github.com/pulp/pulpcore/issues/3609

2 Likes