Bug 749360

Summary: Cannot unlock encrypted partition from serial console
Product: Red Hat Enterprise Linux 6 Reporter: Jiri Koten <jkoten>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.2CC: tpelka
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-27 21:01:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jiri Koten 2011-10-26 19:46:26 UTC
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'.

Comment 1 Ray Strode [halfline] 2011-10-27 20:59:41 UTC
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.

Comment 2 Ray Strode [halfline] 2011-10-27 21:01:41 UTC

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