Bug 1026341

Summary: task._href attribute of a task API item has different meaning when the task is part of a task-group
Product: [Retired] Pulp Reporter: mkovacik
Component: API/integrationAssignee: pulp-bugs
Status: CLOSED CURRENTRELEASE QA Contact: pulp-qe-list
Severity: unspecified Docs Contact:
Priority: medium    
Version: 2.2CC: cduryee, skarmark
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-12 03:05:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mkovacik 2013-11-04 13:26:58 UTC
Description of problem:
The task._href[1] attribute doesn't point to a particular task item URL in cases where more tasks are spawned by pulp to fulfill a request. This breaks compatibility with cases when just a single task is spawned and renders task.task_group_id field redundant.

Version-Release number of selected component (if applicable):
2.2

Actual results:
task._href attribute of a task points to a task_group URL in cases where pulp spawns more than one task to fulfill a request

Expected results:
task._href always points to particular tasks URL no matter whether it is part of a task group or not

[1] task item anatomy, https://pulp-dev-guide.readthedocs.org/en/latest/conventions/sync-v-async.html#call-report

Comment 1 Chris Duryee 2014-11-12 03:05:12 UTC
task groups have been removed as part of pulp 2.4

http://pulp.readthedocs.org/en/latest/user-guide/release-notes/2.4.x.html

Marking BZ as closed/currentrelease.