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:
When booting rhel from serial console with encrypted home partition, plymouth provides password prompt, but I'm unable to unlock the partition. 
Kernel cmd entry is 'console=tty0 console=ttyS0,115200'. 
When booting w/o local console only with 'console=ttyS0' I'm able to enter the password and unlock the partition.

Version-Release number of selected component (if applicable):
plymouth-0.8.3-23.el6

How reproducible:
100%

Steps to Reproduce:
1. Have some encrypted disk
2. boot with kernel cmd entry 'console=tty0 console=ttyS0,115200'
3. try to enter the password from serial console
  
Actual results:
cannot enter password from serial console

Expected results:
able to unlock the partition from serial console. 

Additional info:
It is a regression (introduced in rhel6.1) in functionality as It worked in rhel60 because plymouthd crashed with multiple console entries (bug 631924) and password prompt was handled by cryptsetup. It is similar case as bug 719569, therefor proposing as a blocker for rhel6.2.
Workaround is to disable plymouth - boot with 'rd_NO_PLYMOUTH'.

This is conceptually fairly similar to bug 741515.  I fixed the output side, but neglected the input side.  Let's reopen that bug report instead of having two.

*** This bug has been marked as a duplicate of bug 741515 ***