Bug 1156640 - [RFE] pulp-admin adjust reconnect support
Summary: [RFE] pulp-admin adjust reconnect support
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: Master
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-24 21:34 UTC by Brian Bouterse
Modified: 2015-02-28 23:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-19 01:20:05 UTC
Embargoed:


Attachments (Terms of Use)


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

Description Brian Bouterse 2014-10-24 21:34:54 UTC
pulp-admin reconnect support should be adjusted (and probably removed) because it does not distinguish between submitting a new job (ie: sync) and reconnecting to a previous job.

Several times new work could not be submitted by users (including developers) because work got removed from the system but not canceled in certain failure cases. The user thought they were submitting new work, but they were attaching to an existing job that would never finish. They did not have the information they needed to realize that and could not move forward.

One option is to have pulp-admin always make a new task and stay connected to the task it just dispatched. We could leave it at that, or introduce a --reattach option that accepted a task id perhaps.

Comment 1 Brian Bouterse 2014-10-29 18:36:06 UTC
I would like to see this RFE simply drop the reconnect support. We could add a --reattach option also, but it would be nice to not just add it for sync so it may be a larger effort than this simple RFE calls for.

Comment 2 Brian Bouterse 2015-02-19 01:20:05 UTC
Moved to https://pulp.plan.io/issues/265


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