Bug 1021962

Summary:	Role - different id in request and response
Product:	[Retired] Pulp	Reporter:	Pavlina Bartikova <pbartiko>
Component:	API/integration	Assignee:	pulp-bugs
Status:	CLOSED UPSTREAM	QA Contact:	pulp-qe-list
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	2.2	CC:	cduryee, skarmark
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-28 21:59:32 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:

Description Pavlina Bartikova 2013-10-22 12:22:11 UTC

Description of problem:
Request for create role expects "role_id", but in response is only "id".

How reproducible:
always

Steps to Reproduce:
1. create role

Actual results:
post role_id
get id

Expected results:
post id
get id

Additional info:
https://pulp-dev-guide.readthedocs.org/en/pulp-2.2/integration/rest-api/role/cud.html

Comment 1 Chris Duryee 2014-11-12 01:19:46 UTC

This is still outstanding as of 2.4.3

from server_calls.log when creating a role:

2014-11-12 01:16:19,360 - INFO - POST request to /pulp/api/v2/roles/ with parameters {"display_name": null, "description": null, "role_id": "foo-role"}
2014-11-12 01:16:19,361 - INFO - Response status : 201 

2014-11-12 01:16:19,361 - INFO - Response body :
 {
  "display_name": "foo-role", 
  "description": null, 
  "_ns": "roles", 
  "permissions": {}, 
  "_id": {
    "$oid": "5462b4e3d7a7470368373223"
  }, 
  "id": "foo-role", 
  "_href": "/pulp/api/v2/roles/foo-role/"
}

Assigning this to 3.0.0 since that is our next opportunity to fix this.

Comment 2 Brian Bouterse 2015-02-28 21:59:32 UTC

Moved to https://pulp.plan.io/issues/380