Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #7387

closed

Tasks not delivered to resource-manager are not cleaned up

Added by osapryki over 4 years ago. Updated over 4 years ago.

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

Description

If task was not delivered to resource manager because of redis queue failure, it will forever stay in waiting state.

Steps to reproduce:

  1. Start API service.
  2. Trigger a task. Check a record is created in table core_task and it is in waiting state.
  3. Kill redis. (The best way to imitate the behavior is to disable pestistent storage for redis).
  4. Start redis.
  5. Start resource manager.
  6. Start worker.

Result:

  1. Task created on step 2 is not cleaned up from core_task database table and persists in waiting state.

Related issues

Related to Pulp - Issue #6449: Tasks stuck in Waiting stateCLOSED - CURRENTRELEASEdalleyActions
Related to Pulp - Issue #6533: Task get stuck in 'running' stateCLOSED - WORKSFORMEdalleyActions
Is duplicate of Pulp - Issue #6449: Tasks stuck in Waiting stateCLOSED - CURRENTRELEASEdalleyActions
Actions
Send by e-mail Copy link

Also available in: Atom PDF