Bug 768984 - preupgrade (f14_>f16) unable to mount encrypted drives
Summary: preupgrade (f14_>f16) unable to mount encrypted drives
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: preupgrade
Version: 14
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-19 15:40 UTC by chris.thornton
Modified: 2012-08-16 13:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 13:24:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description chris.thornton 2011-12-19 15:40:07 UTC
Description of problem:
preupgrade is unable to mount all encrypted drives.  The anaconda screen requests the pass phrase for /dev/sda1 but not for any of the other drives. After a brief moment the response is no upgrade directory could be found. 

I'm using a Dell M6500 where /dev/sdc1 is non-encrypted "/boot", /dev/sdc2 (ssd) is the "root", /dev/sda2 is "/var", /dev/sda1 is "swap" and /dev/sdb1 is "/srv".

here is my grub.conf (upgrade does not work, second entry does boot):

boot=/dev/sdc
default=1
timeout=3
splashimage=(hd0,0)/grub/splash.xpm.gz

title Upgrade to Fedora 16 (Verne)
	kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=cba40638-ab04-444b-a1a0-dad0bed35460:/upgrade/ks.cfg
	initrd /upgrade/initrd.img

title Fedora (2.6.35.14-106.fc14.x86_64)
	root (hd0,0)
	kernel /vmlinuz-2.6.35.14-106.fc14.x86_64 ro root=/dev/mapper/luks-be4ee319-2e45-404b-a659-151fda1f3cc1 rd_LUKS_UUID=luks-be4ee319-2e45-404b-a659-151fda1f3cc1 rd_LUKS_UUID=luks-02693a56-8acd-4388-9720-7ffeeb34d700 rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us quiet nouveau.modeset=0 rdblacklist=nouveau
	initrd /initramfs-2.6.35.14-106.fc14.x86_64.img

Version-Release number of selected component (if applicable):
PreUpgrade - 1.1.10 (yum - 3.2.28)

How reproducible:
Every time I try to upgrade.

Steps to Reproduce:
1. sudo preupgrade
2. follow the bouncing ball
3. reboot
4. wait (long time)
5. get input field for pass phrase for /dev/sda1 (my swap partition)
6. watch progress bar
7. get "no upgrade directory found - exit" result window."
8. that is all.
  
Actual results:
no upgrade.

Expected results:
One of the following:
 a. ask for pass phrase for each drive and mount and continue, or
 b. use the pass phrase on each encrypted drive (until it fails) and continue.


Additional info:

Comment 1 Fedora End Of Life 2012-08-16 13:24:16 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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