Bug 1147082 - TaskStatus.queue attribute should be removed with Pulp 3.0.0
Summary: TaskStatus.queue attribute should be removed with Pulp 3.0.0
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: API/integration
Version: Master
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: 3.0.0
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-26 20:57 UTC by Brian Bouterse
Modified: 2015-02-28 22:36 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
revert the injection of the queue attribute (693 bytes, patch)
2014-09-26 20:57 UTC, Brian Bouterse 		no flags Details | Diff
revert the injection of the queue attribute (2.20 KB, patch)
2014-09-29 14:15 UTC, Brian Bouterse 		no flags Details | Diff
Show Obsolete (1) View All


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

Description Brian Bouterse 2014-09-26 20:57:11 UTC 
Created attachment 941718 [details]
revert the injection of the queue attribute

At one point the queue name was recorded in the TaskStatus attribute 'queue', which as part of 2.5.1 was renamed to 'worker_name' and now holds the worker name instead. For backwards compatibility the API of 2.5.1 introduced the 'worker_name' attribute, but copies the value of 'worker_name' to 'queue' as the task being looked up is serialized.

The 'queue' field injection should be removed with 3.0.0, and attached is a revert patch that will remove the injection of the queue attribute.

Also, a deprecation note needs to be added to the release notes for 3.0.0 that the 'queue' field is deprecated with 3.0.0.
Comment 1 Brian Bouterse 2014-09-29 14:15:23 UTC 
Created attachment 942335 [details]
revert the injection of the queue attribute
Comment 2 Brian Bouterse 2015-02-28 22:36:51 UTC 
Moved to https://pulp.plan.io/issues/553
Note You need to log in before you can comment on or make changes to this bug.