Red Hat Bugzilla – Bug 461696
cannot upgrade encrypted system
Last modified: 2009-01-20 16:37:52 EST
+++ This bug was initially created as a clone of Bug #437604 +++
Anaconda does not present the option to "upgrade" an encrypted system. This is
reasonable, since anaconda can't read the disk in order to tell that there is an
existing Fedora installation on it. There needs to be some way of providing the
LUKS key to anaconda so that it can read the filesystems and do the upgrade.
--- Additional comment from email@example.com on 2008-03-15 11:40:00 EDT ---
Upgrade support may not land for F9 given that this is the first release with
encrypted root support.
But Dave was looking at it and we'll decide based on how the patch ends up looking.
--- Additional comment from firstname.lastname@example.org on 2008-05-14 02:04:55 EDT ---
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
--- Additional comment from email@example.com on 2008-06-09 13:28:07 EDT ---
(In reply to comment #1)
> Upgrade support may not land for F9 given that this is the first release with
> encrypted root support.
I guess this didn't happen? Running the install/upgrade DVD, it unlocks my
encrypted partition ok, but doesn't offer the option of upgrading rather than
I have an encrypted PV with an F8 install on LVs within, created as per bug
#124789 comment #95.
It looks like this is the same layout as F9 creates for an encrypted install?
I can upgrade by migrating the LVs to an unencrypted PV, running upgrade, then
moving them back to the encrypted PV.
Once I've done this, will mkinitrd (on F9 LiveCD or the installation if need be)
correctly build to boot from the encrypted PV? Or do I need any explicit
addition config that anaconda might generate to flag stuff up to mkinitrd?
--- Additional comment from firstname.lastname@example.org on 2008-06-10 08:46:53 EDT ---
Nope, this was intended as more of a long-term TODO item rather than something
that had to be fixed prior to release. So no upgrade support in anaconda. Adding
to F10Blocker just so we don't lose sight of it.
--- Additional comment from email@example.com on 2008-06-12 10:41:19 EDT ---
(In reply to comment #3)
> Once I've done this, will mkinitrd (on F9 LiveCD or the installation if need be)
> correctly build to boot from the encrypted PV?
In case anyone else ends up in this situation, yes, by and large this works.
I've listed the steps I took in bug #124789 comment #122.
The only thing that might be of more general interest is that mkinitrd seens to
tie the encrypted PV to a specific disk device (e.g. /dev/sda) rather than
something invariant. So in step 5) when I removed the temporary external USB
drive the PV "moved" from sdb2 to sda2 as the drive ordering changed, and the
initrd I'd previously built failed to work (chrooting from the rescue disk and
running mkinitrd fixed this).
--- Additional comment from firstname.lastname@example.org on 2008-06-12 11:30:12 EDT ---
The F9 live installer does prompt to open all available LUKS partitions between
the root password step and the disk partitioning step. Would it work to simply
move the LUKS-opening step to the very beginning so the upgrade check sees
--- Additional comment from email@example.com on 2008-08-14 15:52:43 EDT ---
Fix will be in anaconda-126.96.36.199-1. This is in rawhide, and is intended to lead to support for upgrade of encrypted F9 systems to F10 using anaconda.
Since cryptsetup-luks has been in RHEL5 since GA we should have the capability to upgrade a 5.2 system that the user has manually set up with LUKS block devices.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Fixed in anaconda-188.8.131.52-1.
1) Installed a system with RHEL5.3 Beta using default partitioning + encryption.
2) Booted snap #2
3) Entered pass phrase to unlock encrypted block devices
4) Anaconda presented me with the option to install or upgrade
5) After choosing upgrade it calculated dependencies and started installing packages
6) System is able to boot to runlevel 3 after the upgrade completes.
I'm moving this one to VERIFIED
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.