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.
Description of problem:
Running the upstream testsuite (including the client testsute) fails in torture_auth tests in 1minutetip.
/CoreOS/libssh/Sanity/upstream-testsuite
Version-Release number of selected component (if applicable):
libssh-0.8.5-2.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Run the above test
Actual results:
1/1 Test #29: torture_auth .....................***Failed 0.97 sec
The failure is coming from sshd, which is being killed by signal SIGXFSZ, when the preauth child tried to write to the pipe an error message (about failing to write a message to or from pam thread).
Expected results:
The tests passes
Additional info:
This seems very similar to the upstream bug that I reported and investigated last year [1], which:
* also reproduces when running a test (in this case torture_auth_kbdint_nonblocking) for the second time (first passes, second fails)
* the logs point to the pam_wrapper, where is the last message coming from in the log.
* the test makes all the foollowing tests running against the same sshd fail.
The upstream issue was workaround by disabling the PAM in sshd, which helped me in master. In this case the pam is what is actually tested in the torture_auth_kbdint_nonblocking test.
This does not require any immediate action or investigation, but is more like tracking bug so we know there is an issue somewhere.
Note, that running the same testsuite outside of the 1minutetip infrastructure is working.
[1] https://bugs.libssh.org/T122
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, 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-2019:3657