Bug 1217781

Summary:	Installation to existing setup renders other fedoras unbootable
Product:	[Fedora] Fedora	Reporter:	Jaroslav Kortus <jkortus>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	21	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
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:	2015-05-04 19:41:08 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 Jaroslav Kortus 2015-05-01 15:33:54 UTC

Description of problem:
I've standard encrypted setup (luks+LVM). I'm creating new LV volume on which I'd like to install new fedora system. The /boot partition is common and is the first unencrypted partition on the disk.

I start the livecd and run anaconda (icon on the desktop), go through the install procedure and unlock the existing luks setup. Then I assign / to the previously created partition and /boot to current /boot partition.

Everything seems to be correct, but in the end anaconda misteriously decides to regenerate ALL initramfs disks that are present in /boot, which does not really work well. It should not touch them at all!

It also rewrites grub.cfg with wrong variables, rendering the previous system unbootable, as the root= no longer matches what it was.

The same issue is with latest centos7.1 live. FC22 beta does not even get to that point. With Centos it's even worse, as the last available kernel was older that one in my fedora and it completely messed up the boot entries.

Version-Release number of selected component (if applicable):
Fedora-Live-KDE-x86_64-21-5.iso

How reproducible:
always

Steps to Reproduce:
1. run default fedora encrypted install of F19 (leave some space in the VG). I run it from livecd
2. (I'm always fully updating the system here)
3. create a LV with sufficient space available to hold new F21 installation (I'm using 10G)
3. Get Fedora-Live-KDE-x86_64-21-5.iso and try installing fedora onto that new partition
4. reboot and boot to previous F19 installation

Actual results:
the previous installation is not bootable (you end up in F21)

Expected results:
* no initramfs rewritten for kernels that have not been newly installed
* no grub entries changed, just new ones added for new installation
* older installations bootable as if the installation of new fedora never happened (this was the case with F19)

Additional info:

Comment 1 David Shea 2015-05-04 19:41:08 UTC


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