Project

Profile

Help

Issue #401

closed

Response body of role creation call is different from role's retrieval call

Added by ipanova@redhat.com about 9 years ago. Updated over 3 years ago.

Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Description of problem:
There is a discrepancy in the response body content in:
1) Role creation call
curl H "Accept: application/json" POST -k -u admin:admin -d '{"role_id":"myrole"}' 'https://example.com/pulp/api/v2/roles/' | python -m json.tool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 206 100 173 100 33 202 38 -
:--:-- --:--:-- --:--:-- 235
{
"_href": "/pulp/api/v2/roles/myrole/",
"_id": {
"$oid": "5307601b356cdf01fefdeeb6"
},
"_ns": "roles",
"description": null,
"display_name": "myrole",
"id": "myrole",
"permissions": {}

2) Retrieval of a single role:
$ curl H "Accept: application/json" GET -k -u admin:admin 'https://example.com/pulp/api/v2/roles/myrole/' | python -m json.tool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 186 100 186 0 0 192 0 -
:--:-- --:--:-- --:--:-- 228
{
"_href": "/pulp/api/v2/roles/myrole/",
"_id": {
"$oid": "5307601b356cdf01fefdeeb6"
},
"_ns": "roles",
"description": null,
"display_name": "myrole",
"id": "myrole",
"permissions": {},
"users": []

In first case "user" field is missing, in the second case it is present.

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

pulp-server-2.4.0-0.2.alpha.git.9.236d540.fc19.noarch
How reproducible:

Steps to Reproduce:
1.Create role
2.Retrieve that role
3.Compare results of the response body

Actual results:
response body of role creation call is different from response body of role retrieval

Expected results:
response body of role creation and role retrieval should be the same

Additional info:

+ This bug was cloned from Bugzilla Bug #1068633 +

Also available in: Atom PDF