Bug 1698951

Summary: ActionController::RoutingError (No route matches [GET] "/pulp/puppet/1…/PULP_MANIFEST") when syncing capsule
Product: Red Hat Satellite Reporter: Evgeni Golov <egolov>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: vijsingh
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: ehelms
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-08 13:14:13 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:

Description Evgeni Golov 2019-04-11 13:25:41 UTC 
Description of problem:

When syncing an external capsule, production.log contains the following errors:

2019-04-11T13:03:30 [I|app|] Started GET "/pulp/puppet/1-testcv-Library-puppet-33dab05c-3bb7-46a5-9d6f-8e88a97780be/PULP_MANIFEST" for 192.168.121.92 at 2019-04-11 13:03:30 +0000
2019-04-11T13:03:30 [F|app|]   
2019-04-11T13:03:30 [F|app|] ActionController::RoutingError (No route matches [GET] "/pulp/puppet/1-testcv-Library-puppet-33dab05c-3bb7-46a5-9d6f-8e88a97780be/PULP_MANIFEST"):
2019-04-11T13:03:30 [F|app|]   
2019-04-11T13:03:30 [F|app|] katello (3.10.0.45) lib/katello/prevent_json_parsing.rb:12:in `call'


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

How reproducible:
100%

Steps to Reproduce:
1. publish a content view with puppet modules
2. let it sync to an external capsule

Actual results:
See above

Expected results:
No RoutingError

Additional info:
I don't think this is bad per-se (this file does not exist in Pulp, and thus the Pulp backend does not reply to that request), but we should just disable Passenger/Rails for /pulp completely.
Comment 3 Evgeni Golov 2019-04-11 13:31:26 UTC 
Just to be clear, I don't care about the 404, I just don't think we should route that request to the Rails app at all. Either Pulp can handle it, or /dev/null.
Comment 4 Bryan Kearney 2020-05-01 14:22:51 UTC 
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Comment 5 Bryan Kearney 2020-06-08 13:14:13 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.