Actions
Issue #449
closed
Consumer bind/unbind operations do not set task state to failed or use the error field in the TaskStatus when there is a problem
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
If there are errors during a consumer bind operation (and I suspect unbind as well), the Pulp server will set the Task state to "finished" instead of "failed". Additionally, it will not include any human readable error message in the Task.
The only way to detect failures is to inspect the progress report, and even that doesn't include a generic enough data structure for the platform CLI to be able to find and render error messages for users.
We need to refactor the error handling code in this area to use the new standard Task error state and message fields.
+ This bug was cloned from Bugzilla Bug #1107844 +
Actions
.