Bug 1107844 - Consumer bind/unbind operations do not set task state to failed or use the error field in the TaskStatus when there is a problem
Summary: Consumer bind/unbind operations do not set task state to failed or use the er...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: consumers
Version: Master
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-10 18:48 UTC by Randy Barlow
Modified: 2015-02-28 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-28 22:10:06 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 449 0 None None None Never

Description Randy Barlow 2014-06-10 18:48:43 UTC
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.

Comment 1 Randy Barlow 2014-06-25 15:18:35 UTC
Because of this bug, attempting to bind a consumer that lacks the RPM handlers will lead to this error message:

pulp-admin -u admin -p admin rpm consumer bind --repo-id testrepo --consumer-id c1
This command may be exited via ctrl+c without affecting the request.
 
[-]
Waiting to begin...
 
[-]
Running...
 
Task Failed
 
Please see the Pulp server logs for details.

If we fix this bug, pulp-admin would be able to tell the user the specific error that happened without having to refer them to the logs.

Comment 2 Brian Bouterse 2015-02-28 22:10:06 UTC
Moved to https://pulp.plan.io/issues/449


Note You need to log in before you can comment on or make changes to this bug.