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.

Description of problem:

Due to a system configuration error, it was discovered that tlog-rec-session will fail to start if the system hostname cannot be determined.

The easiest way to reproduce this is to edit /etc/nsswitch.conf and set the hosts entry to files. Then, remove any entries related to the local host (besides 127.0.0.1 entries) from /etc/hosts.

At this point, setting a user's shell to tlog-rec-session should result in the user being unable to access the system.

Given that this may be set to the root user's account, this should not be a failing scenario for system access.

Now, adding myhostname to the end of the hosts line does remedy the issue, but I don't think that this should be a failure case for tlog at any rate. Anything preventing users from actually accessing the system due to external system configuration issues is quite bad.

Upstream ticket: https://github.com/Scribery/tlog/issues/269

Fixed upstream:

https://github.com/Scribery/tlog/commit/bf97227fd08d4ead58748492f2ac0b2c25b2771c

I can reproduce this one. Is is tested in upstream testsuite? If not, do we want it there? If not I can create a downstream test easily.

Thanks Ondrej, we do not have an upstream test for this, that would be great if you don't mind creating a downstream test.

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-2020:4739