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.
1. Proposed title of this feature request -
Job_invocation reset API could support its output being formatted in clean JSON by providing an API endpoint that returns the output in a single field.
2. Who is the customer behind the request?
Account: name (acct #) TVA [540694]
TAM customer: no
SRM customer: yes
Strategic: yes
3. What is the nature and description of the request?
Customer executed job_invocation command `ps aux` via below API
~~~
curl -k -X POST -u admin:password --data '{ "job_invocation": { "inputs": {"command": "ps aux"}, "job_template_id": 94,"targeting_type": "static_query", "search_query": "name = client.example.com" } }' -H "Content-Type:application/json" https://Satellite.example.com/api/job_invocations/
~~~
When they try to get the output for a host using below API, the JSON output is split between multiple JSON outputs and has all the injected new line (such as the /n and /r statements)-
curl -k -X GET -u admin:password -H "Content-Type:application/json" https://satellite.example.com/api/job_invocations/14/hosts/65 | python -m json.tool
Customer wants to know if the json output from the rest call was just the raw data in one json object / string it would be ideal. But as it stands now the json output is split between multiple json outputs and has all the injected new line statements that make presenting it to a user as a legible list very difficult.
4. Why does the customer need this? (List the business requirements here)
Customer is in process of automating where they are running into situations where they need per-cursor information prior to running a complex automation job such as a very recent listing of a process ID.
Being able to use Satellites job_invocation API and getting its "STDOUT" in a clean and consistent format would be required going forward.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Customer would prefer it if the job_invocation reset API could support its output being formatted in clean JSON. Rather than the "Job invocations store output by the timestamp received" I think their should be an option to asynchronously submit a job and wait for its complete output in properly formatted JSON. This would ensure that the entire STDOUT would be available for logging / reporting in one block of JSON.
6. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? → no
7. Is the sales team involved in this request and do they have any additional input? → no
8. List any affected packages or components. → no
9. Would the customer be able to assist in testing this functionality if implemented? -→yes
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:1222
1. Proposed title of this feature request - Job_invocation reset API could support its output being formatted in clean JSON by providing an API endpoint that returns the output in a single field. 2. Who is the customer behind the request? Account: name (acct #) TVA [540694] TAM customer: no SRM customer: yes Strategic: yes 3. What is the nature and description of the request? Customer executed job_invocation command `ps aux` via below API ~~~ curl -k -X POST -u admin:password --data '{ "job_invocation": { "inputs": {"command": "ps aux"}, "job_template_id": 94,"targeting_type": "static_query", "search_query": "name = client.example.com" } }' -H "Content-Type:application/json" https://Satellite.example.com/api/job_invocations/ ~~~ When they try to get the output for a host using below API, the JSON output is split between multiple JSON outputs and has all the injected new line (such as the /n and /r statements)- curl -k -X GET -u admin:password -H "Content-Type:application/json" https://satellite.example.com/api/job_invocations/14/hosts/65 | python -m json.tool Customer wants to know if the json output from the rest call was just the raw data in one json object / string it would be ideal. But as it stands now the json output is split between multiple json outputs and has all the injected new line statements that make presenting it to a user as a legible list very difficult. 4. Why does the customer need this? (List the business requirements here) Customer is in process of automating where they are running into situations where they need per-cursor information prior to running a complex automation job such as a very recent listing of a process ID. Being able to use Satellites job_invocation API and getting its "STDOUT" in a clean and consistent format would be required going forward. 5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Customer would prefer it if the job_invocation reset API could support its output being formatted in clean JSON. Rather than the "Job invocations store output by the timestamp received" I think their should be an option to asynchronously submit a job and wait for its complete output in properly formatted JSON. This would ensure that the entire STDOUT would be available for logging / reporting in one block of JSON. 6. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? → no 7. Is the sales team involved in this request and do they have any additional input? → no 8. List any affected packages or components. → no 9. Would the customer be able to assist in testing this functionality if implemented? -→yes