Bug 960878

Summary:	Can't upgrade Fedora 17 to Fedora 18 with encrypted LVM using fedup
Product:	[Fedora] Fedora	Reporter:	Yann Droneaud <yann>
Component:	fedup	Assignee:	Will Woods <wwoods>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	17	CC:	dennis, tflink, udovdh, wwoods
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-17 16:36:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yann Droneaud 2013-05-08 08:58:58 UTC

Hi,

After applying updates to one of Fedora 17 laptop, I installed and ran Fedup to upgrade to Fedora 18.

I've already done the same upgrade on another laptop with almost the same setup, eg. encrypted LVM, and it works without any problem.

But on the second laptop, fedup setup failed to upgrade with a boot problem:

Booting `System Upgrade (fedup)'

Chargement de Linux 3.3.4-5.fc17.x86_64?
Chargement du disque m?moire initial?
dracut-cmdline[96]: Warning: Kernel command line option 'KEYTABLE' is deprecated, use 'vconsole.keymap' instead.
dracut-cmdline[96]: Warning: Warning: Kernel command line option 'SYSFONT' is deprecated, use 'vconsole.font' instead.
[ 4.835070] systemd-cryptsetup-generator[298]: Failed to create unit file: File exists
Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode.
Give root password for maintenance
(or type Control-D to continue):

The two systems are using encrypted LVM (whole filesystem encryption, except /boot). The first one was installed initially with Fedora 16 (or 14), while the second one was installed first with Fedora 17, thus, it's its first upgrade to a newer Fedora release.

This bug is likely related to bug #879431 which is also looking like #904332, just like https://fedoraproject.org/wiki/Common_F18_bugs#Upgrade_doesn.27t_start_for_systems_with_more_than_one_encrypted_partition

But unlike the problem listed in Common F18 Bugs, I have only a single encrypted partition. But it seems the luks partition identifier is listed in crypttab and on kernel command line.

Regards.

Comment 1 Will Woods 2013-05-16 21:16:33 UTC

Are you using fedup-0.7.3-4.fc17? If so, this is a duplicate of bug 958586.

Comment 2 Yann Droneaud 2013-05-17 08:42:27 UTC

(In reply to comment #1)
> Are you using fedup-0.7.3-4.fc17? If so, this is a duplicate of bug 958586.

After checking bug #258586, I've tried again to boot on fedup entry and disable graphical boot: I'm now seeing the same boot problem:

  [ TIME ] Timed out waiting for device dev-disk-by\x2duuid-XXXXXXXXXXXXXXXXXXXXXXxxxxx
  [DEPEND] Dependency failed for /boot.
  [DEPEND] Dependency failed for Local File Systems.

(BTW I'm also seeing the problem when not booting on Fedup Grub entry)

I'm using fedup-0.7.3-4.fc17 systemd-44-24.fc17

PS: message "systemd-cryptsetup-generator[298]: Failed to create unit file: File exists" is in fact harmless, but it's the only one I get if graphical boot take place.

Regards.

Comment 3 Will Woods 2013-05-17 16:36:28 UTC


*** This bug has been marked as a duplicate of bug 958586 ***