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.
Created attachment 1042475[details]
Output of foreman-debug from a Satellite 6.1.0 system running RHEL 7.1.
Description of problem:
When issuing a POST request to /api/v2/hosts, you can provide the following attributes, among others:
* host_parameters_attributes
* puppet_classes
When issuing a GET request to /api/v2/hosts/:id, the following attributes are returned:
* parameters
* puppetclasses
This mis-match between attribute names when issuing POST and GET requests is troublesome and forces API clients to write up manual hacks. POST and GET requests should return identically named attributes.
Version-Release number of selected component (if applicable):
Tested against Satellite 6.1.0 on RHEL 7.1. Foreman-debug is attached.
How reproducible:
100%
Steps to Reproduce:
1. Create a host by issuing a POST request to /api/v2/hosts.
2. Read a host by issuing a GET request to /api/v2/hosts/:id.
3. Discover that the POST request accepts differently named parameters than the GET request.
Actual results:
POST and GET work with differently named parameters.
Expected results:
POST and GET work with identically named parameters.
Additional info:
Comment 1RHEL Program Management
2015-06-23 19:02:33 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Created attachment 1042475 [details] Output of foreman-debug from a Satellite 6.1.0 system running RHEL 7.1. Description of problem: When issuing a POST request to /api/v2/hosts, you can provide the following attributes, among others: * host_parameters_attributes * puppet_classes When issuing a GET request to /api/v2/hosts/:id, the following attributes are returned: * parameters * puppetclasses This mis-match between attribute names when issuing POST and GET requests is troublesome and forces API clients to write up manual hacks. POST and GET requests should return identically named attributes. Version-Release number of selected component (if applicable): Tested against Satellite 6.1.0 on RHEL 7.1. Foreman-debug is attached. How reproducible: 100% Steps to Reproduce: 1. Create a host by issuing a POST request to /api/v2/hosts. 2. Read a host by issuing a GET request to /api/v2/hosts/:id. 3. Discover that the POST request accepts differently named parameters than the GET request. Actual results: POST and GET work with differently named parameters. Expected results: POST and GET work with identically named parameters. Additional info: