Bug 475912

Summary: Bootup drops into text mode (--hide-splash) upon detection of non luks encrypted filesystems.
Product: [Fedora] Fedora Reporter: Fred Wells <fredcwells>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: notting, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-12-16 15:06:53 UTC Type: ---
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:    
Bug Blocks: 446452    
Attachments:
Description Flags
start of a patch none

Description Fred Wells 2008-12-11 02:28:06 UTC 
Description of problem:

rc.sysinit drops into text mode (plymouth --hide-splash) when detecting non-luks encrypted filesystems, even if the filesystems are otherwise properly created with cryptsetup (sans luksFormat).

Version-Release number of selected component (if applicable):

Fedora 10
initscripts-8.86-1.i386

How reproducible:

Every time

Steps to Reproduce:
1.  Create non-luks encrypted filesystem using cryptsetup
2.  Update /etc/crypttab accordingly
3.  Reboot
  
Actual results:

Plymouth drops into text mode at line 233 of /etc/rc.d/rc.sysinit due to detection of non-luks formatted encrypted filesystem.

Expected results:

Since non-luks encryption is perfectly valid, Fedora shouldn't drop into text mode as though this is an error.

Additional info:

I'm really not looking forward to reformatting my encrypted filesystems.  Would be great if Fedora was less restrictive.
Comment 1 Fred Wells 2008-12-11 14:25:16 UTC 
This problem is also triggered simply by encrypting "swap", whether luks or not.   I guess I don't understand why either condition should force text boot.
Comment 2 Bill Nottingham 2008-12-11 15:36:12 UTC 
Created attachment 326630 [details]
start of a patch

Try this  - it should catch the first part where this triggers.
Comment 3 Fred Wells 2008-12-11 23:29:11 UTC 
That works!  

Tested with a a mix of luks and non-luks encrypted filesystems as well as swap.

Will this fix be making it's way into a future initscripts update?
Comment 4 Bill Nottingham 2008-12-16 15:06:53 UTC 
At some point, yes.

Fixed in  http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=7b8ad9cd0d276da648bb41ffa9fb27f2b123e07f (ignore the changelog, it's for the other part of that change.)