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.

Created attachment 422587 [details]
tarball with all logs

Description of problem:
Using the new ssh feature I can't ssh to the system because the user account is locked by default. 

My ks.cfg contains:
sshpw --user plainuser secret --plaintext

and I boot with 'linux sshd ks=...'

Version-Release number of selected component (if applicable):
anaconda-13.21.50-2.el6.x86_64


How reproducible:
always

Steps to Reproduce:
1. Create a kscfg with "sshpw --user plainuser secret --plaintext"
2. Boot with 'linux sshd ks=http://...'
3. After stage2 is started try to ssh to the system.
  
Actual results:
ssh fails

Expected results:
ssh succeeds

Additional info:
Logs will be attached.

Created attachment 422588 [details]
syslog

Fixed by 587d0d7eb6536a9f1a2cd30af6151393585b5888 in anaconda-13.21.51-1.el6.

The command should work as expected now. There were questions about giving a password to root, that's possible with something like:

sshpw --user root some_password

Verified on build RHEL6.0-20100701.0 with anaconda-13.21.56-1.el6.

$ ssh plainuser.eng.bos.redhat.com
plainuser.eng.bos.redhat.com's password: 
Last login: Fri Jul  2 03:12:48 2010 from vpn-8-10.rdu.redhat.com
-bash-4.1$ echo $USER
plainuser
-bash-4.1$ logout
Connection to ibm-js12-vios-01-lp1.rhts.eng.bos.redhat.com closed.

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.