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.
Descriptionsthirugn@redhat.com
2018-06-27 19:27:40 UTC
Description of problem:
production.log filled with too many no route errors for rhsm/consumer URLs for accessible_content calls
Version-Release number of selected component (if applicable):
Satellite 6.3.1
How reproducible:
Always
Steps to Reproduce:
Recently while analyzing a customer log, I saw a lot of Routing errors for the accessible_content api call similar to:
2018-06-20 03:37:05 81f8d85c [app] [I] Started GET "/rhsm/consumers/cfe19c3a-3250-4fec-98fe-785ed71eb6c5/accessible_content" for 169.36.64.55 at 2018-06-20 03:37:05 +0200
2018-06-20 03:37:05 81f8d85c [app] [F]
| ActionController::RoutingError (No route matches [GET] "/rhsm/consumers/cfe19c3a-3250-4fec-98fe-785ed71eb6c5/accessible_content"):
| lib/middleware/tagged_logging.rb:18:in `call'
|
|
# cat production.log | grep RoutingError | wc -l
35954
Actual results:
Flooding of errors, about 36k in the production.log for one day.
Expected results:
No Route errors
Additional info:
When I randomly reviewed few content hosts, they were all rhel 7.1, 7.3 but note that I reviewed about 15 vs. 36k
Comment 3sthirugn@redhat.com
2018-07-02 21:04:58 UTC
ON_QA verified:
@Satellite 6.5.0 snap 21
Steps/Observation:
- Upgrade a Satellite from 6.4.2 GA to Satellite 6.5.0 snap 21 which has pre-registered content host on it.
- After upgrade unable to see 'ActionController::RoutingError' during 'subscription-manager refresh'.
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-2019:1222