[RFE] pulp-admin adjust reconnect support
++ This bug was initially created as a clone of Bugzilla Bug #1156640 ++
Description of problem:
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.
--- Additional comment from email@example.com at 10/29/2014 18:36:06 ---
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.
Updated by bmbouter over 3 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.