Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 2070971

Summary: tlog causing SSH to not reliably run commands
Product: Red Hat Enterprise Linux 8 Reporter: Brian Smith <briasmit>
Component: tlogAssignee: jstephen
Status: CLOSED ERRATA QA Contact: Anuj Borah <aborah>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.6CC: aborah, aboscatt, jstephen, lmiksik, mthacker, nhosoi, nikolai.kondrashov, rmeggins, spoore
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tlog-12.1-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2072697 2077473 (view as bug list) Environment:
Last Closed: 2022-11-08 09:45:37 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:
Bug Depends On:    
Bug Blocks: 2072697, 2077473    

Description Brian Smith 2022-04-01 13:29:39 UTC
Description of problem:
On RHEL 8.6 beta, with tlog session recording enabled, I am seeing the following problems:

- Ansible consistently hangs on "gathering facts"
- SSH connections to run commands intermittently hang until input is provided


Version-Release number of selected component (if applicable):
tlog-12-1.el8.x86_64

How reproducible:
Every time

Steps to Reproduce:
1.  Setup RHEL 8.6 beta system
2.  Enable tlog session recording for all users (I did this from Cockpit)
3.  Create a test user account
4.  Setup SSH keys so this test user account can SSH to the localhost with key authentication
5.  Run the following command:

while true; do ssh localhost date; done


Actual results:
With session recording disabled, this command will continuously run and show the  date.

With session recording enabled, this command will randomly hang until you press "enter".  Once you press "enter", the command will keep running and then randomly hang again.


Expected results:
Session recording should not cause this command to randomly hang until input is provided


Additional info:
This is affecting Ansible "gather facts" as well which causes the playbook to hang.

Comment 1 Brian Smith 2022-04-01 13:55:31 UTC
Additional information:  I do not see this issue on RHEL 8.5.

Comment 8 Andre Boscatto 2022-04-06 20:14:40 UTC
PO ack granted

Comment 25 errata-xmlrpc 2022-11-08 09:45:37 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 (tlog bug fix and enhancement update), 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/RHBA-2022:7586