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.
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]
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".
Comment 2Satellite Program
2017-09-22 20:13:43 UTC
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]