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.
Description of problem:
With ssh debug mode enabled, all job invocations fail to complete
Version-Release number of selected component (if applicable):
6.12 snap 1
How reproducible:
always
Steps to Reproduce:
1. set "ssh_log_level: debug" in /etc/foreman-proxy/settings.d/remote_execution_ssh.yml
2. restart foreman-proxy
3. execute a remote job
Actual results:
Job fails with
Initialization error: RestClient::NotFound - 404 Not FoundError loading data from Capsule: NoMethodError - undefined method `code' for "404 Not Found":String
Did you mean? encode
Expected results:
successful execution
Additional info:
Without ssh debug everything works as expected
The issue was in ssh debug level being higher than the regular debug:
[W] Error details for Couldn't enable 'script': <RuntimeError>: ssh_log_level cannot be more verbose than regular log level
The error is logged, but the issue does not prevent foreman-proxy restart, so it can go unnoticed until the job is run.
Keeping the bz open to see if we can somehow communicate the config requirement more intuitively. What comes to mind:
- ssh_log_level misconfig could prevent successful foreman-proxy restart
- maybe a comment in /etc/foreman-proxy/settings.d/remote_execution_ssh.yml saying #ssh_log_level cannot be more verbose than regular log level ?
- ?
Verified on satellite 6.12 snap 10, the error message is now more informative it the described case: "Failed to initialize: Actions::ProxyAction::ProxyActionStopped - Failed to trigger task on the capsule: 404 Not Found"
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 (Important: Satellite 6.12 Release), 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-2022:8506