Bug 473292 - Upgrade fails on system with file-based encryption key
Upgrade fails on system with file-based encryption key
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lehman
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-11-27 09:38 EST by Joe Orton
Modified: 2010-12-05 02:05 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-05 02:05:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
anaconda.log (10.98 KB, text/plain)
2008-11-27 09:38 EST, Joe Orton
no flags Details

  None (edit)
Description Joe Orton 2008-11-27 09:38:06 EST
I've a system where /home is encrypted using an /etc/crypttab line of:

home UUID=a215dd56-c3ec-4140-af7b-eb1c29dd8254 /etc/home.key

this confused anaconda.  When prompted for a password for the underlying
partition, I have to press "cancel" to skip it.  Later, anaconda then fails
to mount everything correctly, claiming it cannot find a mount for "/" in fstab.
Comment 1 Joe Orton 2008-11-27 09:38:53 EST
Created attachment 324886 [details]
Comment 2 Joe Orton 2008-11-27 09:40:08 EST
/dev/mapper/luks-cacdadcb-81ee-40d2-81c3-3a6ef834aae6 is /
Comment 3 David Lehman 2008-12-08 14:34:56 EST
We do not support the use of keys at this point -- just passphrases. If you want to upgrade a system whose encrypted devices use keys, you should add a temporary passphrase before performing the upgrade.

We are hoping to add some support for keys for F11, but it is not the highest of priorities.
Comment 4 Joe Orton 2008-12-09 05:43:43 EST
It would be good to at least fail gracefully in this case.  If anaconda had managed to completely ignore the encrypted /home on this box after I hit "cancel" on the password prompt, the upgrade would have succeeeded.
Comment 5 Bug Zapper 2009-11-16 04:40:19 EST
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
Comment 6 Bug Zapper 2010-11-04 07:39:56 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 7 Bug Zapper 2010-12-05 02:05:34 EST
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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