Bug 1476895
| Summary: | [Bug] - Applicable Errata API for Satellite v.6.2.10 fails with 404 Error | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | anerurka |
| Component: | Errata Management | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Ales Dujicek <adujicek> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2.10 | CC: | adujicek, bbuckingham, cnolte, mhulan, nshaik, tstrachota |
| Target Milestone: | 6.4.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://projects.theforeman.org/issues/20480, http://projects.theforeman.org/issues/20478 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-16 19:33:12 UTC | 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: | |||
Thanks for the report, please use more specific component next time. You already mentioned in subject, this is "Applicable Errata API", so it belongs to "Errata Management". The API is for generic API requests and bugs, such as "provide YAML format as alternative JSON". Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20480 has been resolved. 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:2927 |
Description of problem: Applicable Errata API for Satellite v.6.2.10 fails with 404 Error Version-Release number of selected component (if applicable): Satellite Server v.6.2.10 How reproducible: Steps to Reproduce: 1. Try using Applicable Errata API from Satellite Server fails "https://<satellite-fqdn>/apidoc/v2/hosts_bulk_actions/installable_errata.html" 2. curl -k -u admin:redhat -X POST -d '{"included": {"ids": [3, 11]}, "organization_id": 1, "search": ""}' -H 'Accept: application/json' -H 'Content-Type: application/json' https://satellite.example.com/api/v2/hosts/bulk/applicable_errata {"status":"404","error":"Not Found"} 3. Below is the observation from Production log: +++++ Production log ----------------- 2017-07-28 22:00:27 70aea569 [app] [I] Started POST "/api/v2/hosts/bulk/applicable_errata" for ::1 at 2017-07-28 22:00:27 +0530 2017-07-28 22:00:27 70aea569 [app] [F] | ActionController::RoutingError (No route matches [POST] "/api/v2/hosts/bulk/applicable_errata"): | lib/middleware/tagged_logging.rb:18:in `call' +++++ Actual results: - Applicable Errata API fails Expected results: - Applicable Errata API should work Additional info: Also observed that if we click on Applicable Errata over Satellite Server Web UI API doc [POST /api/hosts/bulk/applicable_errata], and verify the web browser address, then it redirects us to Installable errata : i.e [https://satellite_fqdn/apidoc/v2/hosts_bulk_actions/installable_errata.html]