Bug 1460762 - jobs API call returns: Invalid JSON received.
Summary: jobs API call returns: Invalid JSON received.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: API
Version: 3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3
Assignee: Nobody
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-12 16:13 UTC by Filip Balák
Modified: 2018-11-19 05:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
logs from hosts (2.91 MB, application/zip)
2017-06-12 16:13 UTC, Filip Balák
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github /Tendrl api issues 173 0 None None None 2017-06-12 16:22:32 UTC
Red Hat Bugzilla 1462807 0 unspecified CLOSED GlusterCreateBrick job fails and there are no messages 2021-02-22 00:41:40 UTC

Internal Links: 1462807

Description Filip Balák 2017-06-12 16:13:06 UTC
Created attachment 1287072 [details]
logs from hosts

Description of problem:
I tried to import gluster cluster but job failed. After the fail I checked `hostname/api/1.0/jobs` API call but the response is: `{"errors":{"message":"Invalid JSON received."}}`. This error message remains. The original import job was processing and nearly finished. Unfortunately I do not backup of messages before it started responding with error.

Version-Release number of selected component (if applicable):
tendrl-alerting-3.0-alpha.3.el7scon.noarch
tendrl-api-3.0-alpha.4.el7scon.noarch
tendrl-api-doc-3.0-alpha.4.el7scon.noarch
tendrl-api-httpd-3.0-alpha.4.el7scon.noarch
tendrl-commons-3.0-alpha.9.el7scon.noarch
tendrl-dashboard-3.0-alpha.4.el7scon.noarch
tendrl-node-agent-3.0-alpha.9.el7scon.noarch
tendrl-performance-monitoring-3.0-alpha.7.el7scon.noarch

How reproducible:
20% Very hard.

Steps to Reproduce:
1. Create import gluster cluster job.
2. Hope it fails.
3. If it fails check response of GET `hostname/api/1.0/jobs` API call

Actual results:
After failed import job the `hostname/api/1.0/jobs` API call returns: `{"errors":{"message":"Invalid JSON received."}}`

Expected results:
`hostname/api/1.0/jobs` API call should return valid response.

Additional info:

Comment 3 Nishanth Thomas 2017-06-20 04:11:36 UTC
Is this behaviour consistent? Or you just seen this once?

Comment 4 Filip Balák 2017-06-20 07:18:05 UTC
I have seen this multiple times. Usually when some job fails. In BZ 1462807 is another reproducer.

Comment 5 Nishanth Thomas 2017-06-20 08:14:27 UTC
Once it fails, it keep failing for ever? Is there any workaround to get back to normal?

Comment 6 Filip Balák 2017-06-20 08:33:15 UTC
Yes, it remains in the failing state. I am not sure if there is a workaround. I tried to delete the job I thought broke it from etcd /queue but it didn't fix the issue.
But API calls /jobs/:job_id: and /jobs/:job_id:/{messages|status|...} works.

Comment 8 Shubhendu Tripathi 2018-11-19 05:43:00 UTC
This product is EOL now


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