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.
Bug 1708154 - ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repositories/sync_complete")
Summary: ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repo...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.6.0
Assignee: Justin Sherrill
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-09 08:59 UTC by Evgeni Golov
Modified: 2023-12-15 16:29 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-katello-3.12.0.1-11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:52:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26836 0 Normal Closed ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repositories/sync_complete") 2020-12-07 16:35:39 UTC

Description Evgeni Golov 2019-05-09 08:59:06 UTC 
Description of problem:

When syncing (custom) repositories to Sat 6.5, I see the following in the log.

2019-05-09T04:50:33 [I|app|] Started POST "/katello/api/v2/repositories/sync_complete?token=XXX" for 10.8.29.228 at 2019-05-09 04:50:33 -0400
2019-05-09T04:50:33 [F|app|]   
2019-05-09T04:50:33 [F|app|] ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repositories/sync_complete"):
2019-05-09T04:50:33 [F|app|]   
2019-05-09T04:50:33 [F|app|] katello (3.10.0.46) lib/katello/prevent_json_parsing.rb:12:in `call'
2019-05-09T04:50:34 [I|app|] Started POST "/katello/api/v2/repositories/sync_complete?token=XXX" for 10.8.29.228 at 2019-05-09 04:50:34 -0400
2019-05-09T04:50:34 [F|app|]   
2019-05-09T04:50:34 [F|app|] ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repositories/sync_complete"):
2019-05-09T04:50:34 [F|app|]   
2019-05-09T04:50:34 [F|app|] katello (3.10.0.46) lib/katello/prevent_json_parsing.rb:12:in `call'
2019-05-09T04:50:36 [I|app|] Started POST "/katello/api/v2/repositories/sync_complete?token=XXX" for 10.8.29.228 at 2019-05-09 04:50:36 -0400
2019-05-09T04:50:36 [F|app|]   
2019-05-09T04:50:36 [F|app|] ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repositories/sync_complete"):
2019-05-09T04:50:36 [F|app|]   
2019-05-09T04:50:36 [F|app|] katello (3.10.0.46) lib/katello/prevent_json_parsing.rb:12:in `call'
2019-05-09T04:50:36 [I|app|] Started POST "/katello/api/v2/repositories/sync_complete?token=XXX" for 10.8.29.228 at 2019-05-09 04:50:36 -0400
2019-05-09T04:50:36 [F|app|]   
2019-05-09T04:50:36 [F|app|] ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repositories/sync_complete"):
2019-05-09T04:50:36 [F|app|]   
2019-05-09T04:50:36 [F|app|] katello (3.10.0.46) lib/katello/prevent_json_parsing.rb:12:in `call'


10.8.29.228 is the machine itself, so it's trying to access itself as it seems

Version-Release number of selected component (if applicable):
Satellite 6.5 Snap 26

How reproducible:
Not sure yet

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Evgeni Golov 2019-05-09 09:03:55 UTC 
(that's the call to post_sync_url)
Comment 4 Evgeni Golov 2019-05-09 09:06:16 UTC 
That endpoint was removed upstream in #24671 - remove dead sync plan code (Katello 3.9)
Comment 5 Evgeni Golov 2019-05-09 09:12:45 UTC 
It gets called by Pulp, even if I can't find where. Is it stored as part of the Repo/Product in the DB?
Comment 6 Justin Sherrill 2019-05-16 20:50:40 UTC 
Its a 'notifier' in pulp that was previously created and never deleted.   I swear we deleted it as part of an upgrade step but I see no step, so this seems to be valid issue.
Comment 7 Justin Sherrill 2019-05-20 15:28:13 UTC 
Created redmine issue https://projects.theforeman.org/issues/26836 from this bug
Comment 8 Bryan Kearney 2019-05-20 16:02:05 UTC 
Upstream bug assigned to jsherril
Comment 9 Bryan Kearney 2019-05-20 16:02:07 UTC 
Upstream bug assigned to jsherril
Comment 10 Bryan Kearney 2019-05-21 20:01:55 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26836 has been resolved.
Comment 13 Justin Sherrill 2019-06-19 19:50:35 UTC 
Testing procedure:

1. install satellite 6.4, setup a sync plan for 1 or more repositories to occur every day (or even more frequently if possible).
2. upgrade to 6.6 (via 6.5)
3. Wait a day or two and see if these errors show up in /var/log/foreman/production.log
Comment 14 Evgeni Golov 2019-06-19 19:58:50 UTC 
What I did in my tests is create a schedule that will fire in an hour and upgrade inbetween now and when it will fire.
Comment 15 Lai 2019-07-18 17:44:03 UTC 
Testing steps:

1. Install satellite 6.4
2. Setup sync plan for 1 or more repos to occur hourly and/or once every day (or even more frequently if possible)
3. Upgrade to 6.6 via 6.5
4. Wait a day or two
5. Check log in /var/log/foreman/production.log for ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repositories/sync_complete")

Expected result:
There is no presence of ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repositories/sync_complete")

Actual result:
No presence of ActionController::RoutingError (No route matches [POST] "/katello/api/v2/repositories/sync_complete")

Tested on 6.6 snap 11.

Marking issue as verified.
Comment 16 Bryan Kearney 2019-10-22 19:52:34 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-2019:3172
Note You need to log in before you can comment on or make changes to this bug.