Project

Profile

Help

Issue #7386

closed

Issue #8912: [EPIC] Issues with the traditional tasking system

Task that does not exist in worker or resource-manager are never cleaned up

Added by osapryki over 1 year ago. Updated 11 months ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Possible race condition when deploying pulp in multi node configuration.

Prerequisites:

Pulp plugin codebase has task called task_1.

Steps to reproduce.

  1. Deploy pulp api, resource manager and worker, version 1.
  2. Rename task_1 to task_2.
  3. Deploy version 2 only to pulp resource manager and worker.
  4. Trigger execution of task_1 from API.
  5. Deploy new version of api service.

Result:

Task that was created on step 4 is never cancelled and stays in database in waiting state.


Related issues

Related to Pulp - Issue #7907: Failed task did not clean up properly resource reservationsCLOSED - CURRENTRELEASEbmbouterActions
Actions #1

Updated by fao89 over 1 year ago

  • Triaged changed from No to Yes
Actions #2

Updated by fao89 over 1 year ago

  • Related to Issue #7907: Failed task did not clean up properly resource reservations added
Actions #3

Updated by mdellweg 11 months ago

  • Parent task set to #8912
Actions #4

Updated by bmbouter 11 months ago

  • Status changed from NEW to CLOSED - WONTFIX

Users are recommended to upgrade to the new tasking system as the resolution to this issue. If someone is not able to do that, please comment here with information on why we should reopen the issue.

Also available in: Atom PDF