Bug 1460762
| Summary: | jobs API call returns: Invalid JSON received. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Storage Console | Reporter: | Filip Balák <fbalak> | ||||
| Component: | API | Assignee: | Nobody <nobody> | ||||
| Status: | CLOSED EOL | QA Contact: | sds-qe-bugs | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3 | CC: | fbalak, mkarnik, nthomas, sankarshan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Is this behaviour consistent? Or you just seen this once? I have seen this multiple times. Usually when some job fails. In BZ 1462807 is another reproducer. Once it fails, it keep failing for ever? Is there any workaround to get back to normal? 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.
This product is EOL now |
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: