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:
When ssh debug logging is enabled, it prints only the facility which emitted the message, not the message itself.
Version-Release number of selected component (if applicable):
rubygem-smart_proxy_remote_execution_ssh-0.3.0-3
rubygem-foreman_remote_execution_core-1.3.0-1
How reproducible:
Always
Steps to Reproduce:
1. Set ssh_log_level to debug in /etc/smart_proxy_dynflow_core/settings.d/remote_execution_ssh.yml
2. Restart smart_proxy_dynflow_core
3. Run a REX job
4. Watch /var/log/foreman-proxy/smart_proxy_dynflow_core.log
Actual results:
The log contains logs like
socket[2abe13ae57f8]socket[2abe13ae57f8]net.ssh.connection.session[3fcbf60ee3e8]net.ssh.connection.channel[3fcbf6108dec]socket[2abe13ae57f8]net.ssh.connection.channel[3fcbf6108dec]socket[2abe13ae57f8]socket[2abe13ae57f8
(also hitting BZ1851379)
It does not show what is actually supposed to be logged, only that a session or a channel emitted a log message.
Expected results:
Log messages like
net.ssh.transport.algorithms[2b0600e23494]: negotiating algorithms
net.ssh.transport.algorithms[2b0600e23494]: negotiated:
* kex: ecdh-sha2-nistp521
* host_key: ecdsa-sha2-nistp256
* encryption_server: aes256-ctr
* encryption_client: aes256-ctr
* hmac_client: hmac-sha2-512-etm
* hmac_server: hmac-sha2-512-etm
* compression_client: none
* compression_server: none
* language_client:
* language_server:
Additional info:
Verified on Satellite 6.9 snap 4, ssh debug logs are stored as expected. However, there is side effect occurring on FIPS-enabled machines, separate bug created here https://bugzilla.redhat.com/show_bug.cgi?id=1906023
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 (Moderate: Satellite 6.9 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-2021:1313