Issue #1582: Task Group ID status returning 404 - Pulp

Actions

Send by e-mail Copy link

Issue #1582

closed

Task Group ID status returning 404

Added by paji@redhat.com about 8 years ago. Updated about 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Category:

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Master

Platform Release:

2.8.0

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Pulp 2

Sprint:

Quarter:

Description

Get the zoo5 repo from -> https://github.com/Katello/runcible/tree/master/test/fixtures/repositories/zoo5
Steps below will assume file:///var/www/repositories/zoo5 is the destination

$ pulp-admin rpm repo create --repo-id=ideate --feed=file:///var/www/repositories/zoo5
$ pulp-admin rpm repo sync run --repo-id=ideate

$ echo '{"repo_criteria":{"filters":{"id":{"$in":["ideate"]}}}}' |http --json --verify no --auth admin:admin POST "https://localhost/pulp/api/v2/repositories/actions/content/regenerate_applicability/"
HTTP/1.1 202 ACCEPTED
Connection: close
Content-Length: 127
Content-Type: application/json; charset=utf-8
Date: Tue, 26 Jan 2016 06:08:00 GMT
Server: Apache/2.4.6 (CentOS)

{
    "_href": "/pulp/api/v2/task_groups/e1def059-1d83-4ff2-9b3d-25df70b98d5a/", 
    "group_id": "e1def059-1d83-4ff2-9b3d-25df70b98d5a"
}

$  http --json --verify no --auth admin:admin GET "https://localhost/pulp/api/v2/task_groups/e1def059-1d83-4ff2-9b3d-25df70b98d5a/state_summary/"

HTTP/1.1 404 NOT FOUND
Connection: close
Content-Encoding: utf-8
Content-Length: 553
Content-Type: application/json; charset=utf-8
Date: Tue, 26 Jan 2016 06:09:19 GMT
Server: Apache/2.4.6 (CentOS)

{
    "_href": "/pulp/api/v2/task_groups/e1def059-1d83-4ff2-9b3d-25df70b98d5a/state_summary/", 
    "error": {
        "code": "PLP0009", 
        "data": {
            "resources": {
                "resource_id": "e1def059-1d83-4ff2-9b3d-25df70b98d5a"
            }
        }, 
        "description": "Missing resource(s): resource_id=e1def059-1d83-4ff2-9b3d-25df70b98d5a", 
        "sub_errors": []
    }, 
    "error_message": "Missing resource(s): resource_id=e1def059-1d83-4ff2-9b3d-25df70b98d5a", 
    "exception": null, 
    "http_request_method": "GET", 
    "http_status": 404, 
    "resources": {
        "resource_id": "e1def059-1d83-4ff2-9b3d-25df70b98d5a"
    }, 
    "traceback": null
}

Actions

Copy link

Updated by paji@redhat.com about 8 years ago

Subject changed from Group ID status returning 404 to Task Group ID status returning 404

Actions

Copy link

Updated by dkliban@redhat.com about 8 years ago

This makes sense based on the implementation. The repository does not have any consumers associated it with it. As result no work needs to be done. We return a task group id, but task group has 0 tasks associated with it.

Would the better behavior be a data structure with 0 for each state?

{
 "accepted": 0,
 "finished": 0,
 "running": 0,
 "canceled": 0,
 "waiting": 0,
 "skipped": 0,
 "suspended": 0,
 "error": 0,
 "total": 0
}

Actions

Copy link

Updated by paji@redhat.com about 8 years ago

0 better than 404

Added by dkliban@redhat.com about 8 years ago

Revision 9b1cd29e | View on GitHub

Sends back a group call report for summary of task group with 0 tasks

Originally we wanted to return a 404 when querying for a task group that has no tasks associated with it. However, we always return a task group id when kicking off the applicability regeneration task. User should be able to see that 0 tasks were dispatched as part of that task group.

https://pulp.plan.io/issues/1582 closes #1582