Bug 1192102

Summary: _href in event listeners retrieval response body is wrong
Product: [Retired] Pulp Reporter: Ina Panova <ipanova>
Component: API/integrationAssignee: pulp-bugs
Status: CLOSED DUPLICATE QA Contact: pulp-qe-list
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.6 BetaCC: igulina
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-12 19:08:43 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 Ina Panova 2015-02-12 15:58:53 UTC
Description of problem:

$ curl -H "Accept: application/json" -H "WebFrameworkSwitch: webpy" -X GET -k -u admin:admin -d '{}' "https://localhost/pulp/api/v2/events/"|python -m json.tool  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   282  100   280  100     2    937      6 --:--:-- --:--:-- --:--:--   936
[
    {
        "_href": "/pulp/api/v2/events/",
        "_id": {
            "$oid": "54dc960345ef48230956aea9"
        },
        "_ns": "event_listeners",
        "event_types": [
            "repo.sync.finish",
            "repo.publish.finish"
        ],
        "id": "54dc960345ef48230956aea9",
        "notifier_config": {
            "url": "http://localhost/api"
        },
        "notifier_type_id": "http"
    }
]


_href should contain the id of event listener like "_href": "/pulp/api/v2/events/4dc960345ef48230956aea9"


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




How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Irina Gulina 2015-02-12 18:53:07 UTC
I believe it's a duplicate of 1111255

Comment 2 Ina Panova 2015-02-12 19:08:43 UTC

*** This bug has been marked as a duplicate of bug 1111255 ***