Issue #2787: Fatal exceptions from tasks not being reported by tasks API - Pulp

Actions

Send by e-mail Copy link

Issue #2787

closed

Fatal exceptions from tasks not being reported by tasks API

Added by dkliban@redhat.com over 7 years ago. Updated about 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Groomed:

Sprint Candidate:

Yes

Tags:

Sprint:

Quarter:

Description

The Task model has an error field. It is a JSON field. After a task succeeds or fails, this field is supposed to contain a dictionary representing any fatal exception encountered during the task. If no fatal exception is encountered the field should be set to None. This happens here[0] in the code, but the API for tasks does not report an 'error' field.

[0] https://github.com/pulp/pulp/blob/3.0-dev/platform/pulp/tasking/tasks.py#L322

Actions

Copy link

Updated by dkliban@redhat.com over 7 years ago

Tracker changed from Story to Issue
Subject changed from Record fatal exceptions from tasks in 'error' field of Task object to Fatal exceptions from tasks not being reported by tasks API
Description updated (diff)
Severity set to 2. Medium
Triaged set to No