Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1766155 - API call to list hostgroups does not list some attributes
Summary: API call to list hostgroups does not list some attributes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Group
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-28 13:04 UTC by Anton Nesterov
Modified: 2021-01-19 21:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-19 21:33:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Anton Nesterov 2019-10-28 13:04:49 UTC
Description of problem:
"GET https://$(hostname)//api/hostgroups" doesn't show all hostgroup attributes. At least content_host_id is not listed. It is present when listing one particular hostgroup via "GET https://$(hostname)//api/hostgroups/:id"

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

How reproducible:
Deterministic

Steps to Reproduce:
1. Create a hostgroup with non-empty "Content Source"
2. GET hostgroup through API:
# curl -u admin:<password> -H "Accept:  version=2, application/json" -H  "Content-Type: application/json" -k -X GET  https://$(hostname)/api/hostgroups/

Actual results:
Hostgroups are listed, but content_host_id (maybe other attrs) is missing

Expected results:
Hostgroups returned with all attributes


Additional info:
similar to BZ#1702676

Comment 3 Anton Nesterov 2019-10-28 14:55:28 UTC
I'm saying ___It is present when listing one particular hostgroup via "GET https://$(hostname)//api/hostgroups/:id"___

But ironically listing HG by ID misses compute_resource_id https://bugzilla.redhat.com/show_bug.cgi?id=1766199

Comment 4 Anton Nesterov 2019-10-29 12:13:29 UTC
compute_resource_id is also missing here

Comment 5 Mike McCune 2020-12-09 22:17:06 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in approximately a month. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Mike McCune 2021-01-19 21:25:23 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact your Red Hat Account Team. Thank you.


Note You need to log in before you can comment on or make changes to this bug.