Description of problem: API calls related to getting information about non-existent jobs (invalid job id) are returning `200 OK` statuses. Version-Release number of selected component (if applicable): tendrl-selinux-1.5.3-2.el7rhgs.noarch tendrl-commons-1.5.4-3.el7rhgs.noarch tendrl-api-httpd-1.5.4-2.el7rhgs.noarch tendrl-grafana-selinux-1.5.3-2.el7rhgs.noarch tendrl-ansible-1.5.4-1.el7rhgs.noarch tendrl-node-agent-1.5.4-3.el7rhgs.noarch tendrl-ui-1.5.4-3.el7rhgs.noarch tendrl-grafana-plugins-1.5.4-4.el7rhgs.noarch tendrl-notifier-1.5.4-2.el7rhgs.noarch tendrl-api-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.5.4-4.el7rhgs.noarch How reproducible: 100% Steps to Reproduce: 1. Call following API calls with valid access token: curl -XGET -H "Authorization: Bearer access_token" http://127.0.0.1/api/1.0/jobs/invalid curl -XGET -H "Authorization: Bearer access_token" http://127.0.0.1/api/1.0/jobs/invalid/messages curl -XGET -H "Authorization: Bearer access_token" http://127.0.0.1/api/1.0/jobs/invalid/output curl -XGET -H "Authorization: Bearer access_token" http://127.0.0.1/api/1.0/jobs/invalid Actual results: All calls above return empty list or empty dictionary with response status `200 OK`. Only /api/1.0/jobs/invalid/status returns `404 Not Found`. Expected results: All calls above should return status `404 Not Found`. Additional info:
Looks ok. --> VERIFIED Tested with: tendrl-ansible-1.6.1-2.el7rhgs.noarch tendrl-api-1.6.1-1.el7rhgs.noarch tendrl-api-httpd-1.6.1-1.el7rhgs.noarch tendrl-commons-1.6.1-1.el7rhgs.noarch tendrl-grafana-plugins-1.6.1-1.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.1-1.el7rhgs.noarch tendrl-node-agent-1.6.1-1.el7rhgs.noarch tendrl-notifier-1.6.0-1.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.1-1.el7rhgs.noarch
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-2018:2616