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):
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 18.104.22.168 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
Flooding of errors, about 36k in the production.log for one day.
No Route errors
When I randomly reviewed few content hosts, they were all rhel 7.1, 7.3 but note that I reviewed about 15 vs. 36k
This should be reproducible by doing a subscription-manager refresh as mentioned in the other bug - https://bugzilla.redhat.com/show_bug.cgi?id=1449570#c2
Created redmine issue https://projects.theforeman.org/issues/26350 from this bug
@Satellite 6.5.0 snap 21
- 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'.
Will this fix be backported to Satellite 6.4.x? My customer has just updated to 6.4.3 and will not be going to 6.5 when it first releases.
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.