Bug 1387569

Summary: API Discovery rule POST and PUT requests do not return organization_ids and location_ids
Product: Red Hat Satellite Reporter: Andrii Balakhtar <abalakht>
Component: Discovery PluginAssignee: Lukas Zapletal <lzap>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.3.0Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-02 20:58:45 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 Andrii Balakhtar 2016-10-21 09:56:38 UTC
Description of problem:
As per #1324508, `organization_ids` and `location_ids` are accepted for Discovery rule's POST and PUT requests, however this requests do not return these parameters and their values.

Version-Release number of selected component (if applicable):
Sat 6.3.0 Snap 4

How reproducible:
Always

Steps to Reproduce:
1. Issue HTTP POST request to /api/v2/discovery_rules. Example of request body: {"discovery_rule": {"organization_ids": [15], "name": "test", "search": "cpu_count > 3", "hostgroup_id": 1, "location_ids": [42]}}
2. Issue HTTP PUT request to /api/v2/discovery_rules/:id. Example of request body: {"discovery_rule": {"organization_ids": [16], "location_ids": [43]}}
3.

Actual results:
`organization_ids` and `location_ids` are accepted but never returned.
Example of output:
{
"id": 3
"name": "test4"
"search": "cpu_count > 3"
"hostgroup_id": 1
"hostname": ""
"max_count": 0
"priority": 0
"enabled": true
"created_at": "2016-10-21T12:47:36.244+03:00"
"updated_at": "2016-10-21T12:47:36.244+03:00"
}

Expected results:
List of associated organizations and locations should be returned altogether with the rest parameters, preferably in the same way as we have for GET request:
{
[...]
"locations":[{"id":42,"name":"scsdfdfsd","title":"scsdfdfsd","description":""}],
"organizations":[{"id":15,"name":"3J89gV","title":"3J89gV","description":null}]
}

Additional info:
Low-priority issue as we can still get the list of associated organizations and locations by issuing GET request.

Comment 4 Bryan Kearney 2018-08-02 20:58:45 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.