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:
A kickstart installation with a user defined using the sshpw kickstart command doesn't allow to connect to the installation environment using ssh. The following traceback is reported in journalctl:
Jul 23 15:33:26 localhost handle-sshpw[1834]: Traceback (most recent call last):
Jul 23 15:33:26 localhost handle-sshpw[1834]: File "/usr/sbin/handle-sshpw", line 51, in <module>
Jul 23 15:33:26 localhost handle-sshpw[1834]: homedir=ud.homedir, shell=ud.shell, gecos=ud.gecos, root="/")
Jul 23 15:33:26 localhost handle-sshpw[1834]: AttributeError: 'F24_SshPwData' object has no attribute 'homedir'
Jul 23 15:33:26 localhost systemd[1]: anaconda-sshd.service: Control process exited, code=exited status=1
Jul 23 15:33:26 localhost systemd[1]: anaconda-sshd.service: Failed with result 'exit-code'.
Jul 23 15:33:26 localhost systemd[1]: Failed to start OpenSSH server daemon.
Version-Release number of selected component (if applicable):
RHEL-8.3.0-20200701.2
anaconda-33.16.3.10-1.el8
How reproducible:
always
Steps to Reproduce:
1. Create a kickstart file incluing the sshpw command:
sshpw --username=John --plaintext heslo
2. Start installation using the kickstart file, append "inst.sshd" on the kernel command line.
3. Try to connect to the installation environment using ssh, use the "John" user name.
Actual results:
sshd is not running:
Jul 23 15:33:26 localhost handle-sshpw[1834]: Traceback (most recent call last):
Jul 23 15:33:26 localhost handle-sshpw[1834]: File "/usr/sbin/handle-sshpw", line 51, in <module>
Jul 23 15:33:26 localhost handle-sshpw[1834]: homedir=ud.homedir, shell=ud.shell, gecos=ud.gecos, root="/")
Jul 23 15:33:26 localhost handle-sshpw[1834]: AttributeError: 'F24_SshPwData' object has no attribute 'homedir'
Expected results:
sshd is running, it's possible to login via ssh as "John".
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 (anaconda 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:4729