Bug 1654383

Summary: POST katello/api/v2/host_collections doesn't return host_ids
Product: Red Hat Satellite Reporter: Andrii Balakhtar <abalakht>
Component: Host CollectionsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.5.0Keywords: PrioBumpQA, Regression
Target Milestone: Released   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-29 13:56:20 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 Andrii Balakhtar 2018-11-28 16:07:50 UTC
Description of problem:
In sat6.5 POST request to katello/api/v2/host_collections no longer returns host_ids field, which was present in 6.4 and below.

Version-Release number of selected component (if applicable):
Sat6.5 SNAP 5

How reproducible:
Always

Steps to Reproduce:
1. Make POST request to katello/api/v2/host_collections with some host ids, e.g.
{"name": "my_host_collection", "host_ids": [2], "organization_id": 3}
2. Take a look at received response
3.

Actual results:
No host ids in output:
{"name":"my_host_collection","organization_id":3,"max_hosts":null,"description":null,"total_hosts":1,"unlimited_hosts":true,"created_at":"2018-11-28 15:33:53 UTC","updated_at":"2018-11-28 15:33:53 UTC","id":9,"permissions":{"deletable":true,"editable":true}}

Expected results:
host_ids should be present in output, similar to GET:
{"host_ids": [2],"name":"my_host_collection","organization_id":3,"max_hosts":null,"description":null,"total_hosts":1,"unlimited_hosts":true,"created_at":"2018-11-28 15:33:53 UTC","updated_at":"2018-11-28 15:33:53 UTC","id":9,"permissions":{"deletable":true,"editable":true}}

Additional info:

Comment 3 Brad Buckingham 2018-11-29 13:56:20 UTC

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