Project

Profile

Help

Issue #5673

closed

Ansible Plugin - Story #5517: [EPIC] Automation Hub Release Blockers

Resource reservations are not cleaned up if worker is killed

Added by osapryki about 3 years ago. Updated about 3 years ago.

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

Description

It pulp worker is killed while executing task that has reserved resources, resources are not cleaned up.
All subsequent task that use any of the reserved resources are assigned to the same worker (which is dead).

Steps to reproduce:

1. Spawn import_collection task from pulp_ansible (T1).
2. While task is running kill worker (W1).
3. Start another worker (W2)
4. Spawn import_collection task from pulp_ansible (T2)

Expected behavior:

Task T2 is assigned on worker W2 or Cancelled if assigned on W1 before cleanup is performed.

Actual behavior:

Task T2 is assigned on worker W1 and remains in waiting state forever.
Resources are not cleaned up.

Environment:

pulpcore + pulp_ansible.
1 worker

Also available in: Atom PDF