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 1838677

Summary: Cannot login as a user created by the sshpw kickstart command
Product: Red Hat Enterprise Linux 8 Reporter: Jan Stodola <jstodola>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: pzatko
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: lorax-28.14.46-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1843609 (view as bug list) Environment:
Last Closed: 2020-11-04 02:46:06 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: 1860058    
Bug Blocks: 1812825, 1843609    
Attachments:
Description Flags
anaconda.log
none
program.log
none
kickstart none

Description Jan Stodola 2020-05-21 14:49:58 UTC
Description of problem:
It's not possible to login to the system being installed as the user defined by the sshpw kickstart command:

sshpw --username=John --plaintext heslo

$ ssh John.122.183
Warning: Permanently added '192.168.122.183' (ECDSA) to the list of known hosts.
John.122.183's password: 
This account is currently not available.
Connection to 192.168.122.183 closed.
$

On the system being installed:
[anaconda root@localhost ~]# getent passwd John
John:x:1000:1000::/home/John:/sbin/nologin
[anaconda root@localhost ~]#

Changing "/sbin/nologin" to "/bin/bash" solves the problem and it's possible to login as "John" during the installation.

Version-Release number of selected component (if applicable):
RHEL-8.2 GA
anaconda-29.19.2.17-1.el8

How reproducible:
always

Steps to Reproduce:
1. prepare a kickstart file containing:
sshpw --username=John --plaintext heslo
2. start the installation with the "inst.sshd ks=<PATH>" on the kernel command line
3. try to login as John

Actual results:
Unable to login.

Expected results:
John is able to login.

Comment 1 Jan Stodola 2020-05-21 14:55:50 UTC
Created attachment 1690669 [details]
anaconda.log

Comment 2 Jan Stodola 2020-05-21 14:56:12 UTC
Created attachment 1690670 [details]
program.log

Comment 4 Jan Stodola 2020-05-21 14:56:51 UTC
Created attachment 1690672 [details]
kickstart

Comment 6 Jan Stodola 2020-05-21 20:09:07 UTC
This can be fixed in lorax by keeping /etc/default/useradd in the installation image, switching the component.

https://github.com/weldr/lorax/pull/1020

Comment 13 errata-xmlrpc 2020-11-04 02:46:06 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 (lorax 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:4662