Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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 1202564 - GET /api/v2/config_templates/build_pxe_default returns non-JSON message
Summary: GET /api/v2/config_templates/build_pxe_default returns non-JSON message
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: Tomas Strachota
QA Contact: Kedar Bidarkar
Depends On:
TreeView+ depends on / blocked
Reported: 2015-03-16 21:55 UTC by jaudet
Modified: 2021-07-21 12:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-08-12 14:02:45 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10715 0 Normal Closed GET /api/v2/config_templates/build_pxe_default returns non-JSON message 2020-06-10 13:39:47 UTC

Description jaudet 2015-03-16 21:55:07 UTC
Description of problem:
GET /api/v2/config_templates/build_pxe_default returns a message that has a content-type of application/json but is not JSON.

Version-Release number of selected component (if applicable):
Tested against Satellite-6.1.0-RHEL-6-20150311.1 and Satellite-6.1.0-RHEL-7-20150311.1.

How reproducible:

Steps to Reproduce:
1. GET /api/v2/config_templates/build_pxe_default
2. Examine the response payload.

Actual results:
'PXE Default file has been deployed to all Smart Proxies'

Expected results:
The payload is valid JSON. For example, something like this:

        'status': 'success',
        'message': 'PXE Default file has been deployed to all Smart Proxies',

Additional info:

Comment 2 jaudet 2015-03-16 22:02:11 UTC
An automated test for this bug will be added to QE's test suite shortly. See:

Comment 3 RHEL Program Management 2015-03-16 22:12:59 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.

Comment 5 Lukas Zapletal 2015-03-17 14:15:47 UTC
Valid bug, we have two of these in the app/controllers/api/v2/config_templates_controller.rb file.

Comment 6 Tomas Strachota 2015-06-05 14:00:10 UTC
Created redmine issue from this bug

Comment 7 Bryan Kearney 2015-06-08 10:04:48 UTC
Moving to POST since upstream bug has been closed
Applied in changeset commit:2950fe116fd37b0a7b8c7df8446c687e9ac6b8d7.

Comment 10 Kedar Bidarkar 2015-06-15 18:13:47 UTC

Currently the payload is JSON, but has no "success" status info as requested by the initial bug info. 

{"message":"PXE Default file has been deployed to all Smart Proxies"}

Tested with Sat61-GA-snap8-c2

Comment 11 Tomas Strachota 2015-06-25 14:35:04 UTC
Just for the record: the status is already contained in http status. Having it in the json would be redundant.

Comment 12 Bryan Kearney 2015-08-11 13:37:30 UTC
This bug is slated to be released with Satellite 6.1.

Comment 13 Bryan Kearney 2015-08-12 14:02:45 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.

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