Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionAndrii 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.
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.
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.