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.

Bug 1596636

Summary: Callback from smart proxy to Foreman fails with error 403: "No SSL cert with CN supplied"
Product: Red Hat Satellite Reporter: Radovan Drazny <rdrazny>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9.7CC: aruzicka, hyu, inecas, rdrazny
Target Milestone: UnspecifiedKeywords: Reopened, 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: 2022-04-08 05:31:43 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 Radovan Drazny 2018-06-29 11:10:19 UTC
Description of problem:
When running a large number of remote execution tasks, a callback from smart proxy occasionally fails with the following error: 

2018-06-28T13:59:10 [I|app|f60e2] Processing by ForemanTasks::Api::TasksController#callback as */*
2018-06-28T13:59:10 [I|app|f60e2]   Parameters: {"callback"=>{"task_id"=>"709cffa0-74e5-4347-8f72-3b1fb3f77828", "step_id"=>3}, "data"=>{"result"=>[{"output_type"=>"stdout", "output"=>"Thu Jun 28 17:59:09 UTC 2018\r\n", "timestamp"=>1530208750.3636398}], "runner_id"=>"5a586668-6707-4f4f-8c5f-5cafd5c853ac", "exit_status"=>0}, "task"=>{}}
2018-06-28T13:59:10 [W|app|f60e2] No SSL cert with CN supplied - request from 172.25.1.1, 
2018-06-28T13:59:10 [I|app|f60e2]   Rendering api/v2/errors/access_denied.json.rabl within api/v2/layouts/error_layout
2018-06-28T13:59:10 [I|app|f60e2]   Rendered api/v2/errors/access_denied.json.rabl within api/v2/layouts/error_layout (3.3ms)
2018-06-28T13:59:10 [I|app|f60e2] Filter chain halted as #<Proc:0x00000000088e2170@/usr/share/foreman/app/controllers/concerns/foreman/controller/smart_proxy_auth.rb:14> rendered or redirected
2018-06-28T13:59:10 [I|app|f60e2] Completed 403 Forbidden in 61ms (Views: 31.5ms | ActiveRecord: 10.6ms)

Version-Release number of selected component (if applicable):
Satellite 6.4 Snap 9

How reproducible:
rarely

Steps to Reproduce:
Run many ReX tasks in parallel. My scenario was running simple "date" command on 200 docker containers. 

Actual results:
"No SSL cert with CN supplied", task never marked as successful, even if it was successfully performed on a client.

Expected results:
No error, task is marked as successful.

Comment 1 Brad Buckingham 2018-06-29 15:09:25 UTC
Is this scenario with custom certs or the default certs?

Comment 2 Ivan Necas 2018-06-29 17:07:02 UTC
Additional question: was this one capsule setup, or more of them was involved in the process?

Comment 3 Radovan Drazny 2018-07-02 12:34:32 UTC
Standard install, default certs, just one satellite server and its integrated smartproxy.

Comment 9 Bryan Kearney 2019-07-02 18:02:05 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 10 Bryan Kearney 2019-08-01 18:35:31 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.

Comment 11 Hao Chang Yu 2022-04-08 05:17:43 UTC
Reopen this bug because it is still happening in Satellite 6.9

Comment 13 Hao Chang Yu 2022-04-08 05:25:23 UTC
Maybe the possible workaround code fix for this is to:

1) Retry the callbacks.
2) Don't fail the succeeded remote task when the callback responded with failure. Let the main job on Satellite to pull the results after 10 minutes.

Comment 14 Hao Chang Yu 2022-04-08 05:31:43 UTC
Sorry, just notice that a new bug 2068480 has already raised for this issue so I will close this again.

*** This bug has been marked as a duplicate of bug 2068480 ***