This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 455343 - booty doesn't handle encrypted block devices
booty doesn't handle encrypted block devices
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: booty (Show other bugs)
5.2
All Linux
high Severity high
: rc
: ---
Assigned To: Peter Jones
Alexander Todorov
:
Depends On:
Blocks: 229865
  Show dependency treegraph
 
Reported: 2008-07-14 17:57 EDT by David Lehman
Modified: 2009-01-20 16:05 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-20 16:05:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
teach getPhysicalDevices about luks devices, sort of (491 bytes, patch)
2008-07-14 18:07 EDT, David Lehman
no flags Details | Diff

  None (edit)
Description David Lehman 2008-07-14 17:57:15 EDT
Description of problem:
If root is on an encrypted block device, booty will traceback at the end of install.

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

How reproducible:
Always if you encrypt the rootfs' block device.

Steps to Reproduce:
1. Run the 5.3 installer with luks bits, encrypt root device
2. wait for traceback
3.
  
Actual results:
traceback

Expected results:


Additional info:
Comment 1 David Lehman 2008-07-14 18:07:41 EDT
Created attachment 311781 [details]
teach getPhysicalDevices about luks devices, sort of
Comment 4 David Lehman 2008-07-21 18:30:59 EDT
Fixed in booty-0.80.5-1.
Comment 8 errata-xmlrpc 2009-01-20 16:05:40 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0138.html

Note You need to log in before you can comment on or make changes to this bug.