Bug 1314027

Summary:	[anaconda] installs i686 PAE kernel on x86_64 system making it unbootable
Product:	[Fedora] Fedora	Reporter:	Joachim Frieben <jfrieben>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-02 18:37:45 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 Joachim Frieben 2016-03-02 18:37:10 UTC

Description of problem:
Using the latest network install media for Fedora 24 Workstation x86_64, a number of i686 packages get installed, in particular the kernel package. Not surprisingly, the resulting system hangs upon boot. Installed i686 packages are

- glibc-2.23.1-5.fc24.i686
- kernel-PAE-4.5.0-0.rc6.git0.1.fc24.i686
- kernel-PAE-core-4.5.0-0.rc6.git0.1.fc24.i686
- kernel-PAE-modules-4.5.0-0.rc6.git0.1.fc24.i686
- nss-softokn-freebl-3.22.2-1.0.fc24.i686
- xorg-x11-drv-geode-2.11.18-1.fc24.i686 .

Version-Release number of selected component (if applicable):
anaconda-24.13-1.fc24

How reproducible:
Always

Steps to Reproduce:
1. Perform network install of Fedora 24 Workstation x86_64.
2. Reboot system.

Actual results:
The boot loader lists i686 boot kernels alone which do not boot on the x86_64 system.

Expected results:
Installed kernels are x86_64 in agreement with the rest of the system.

Additional info:
- Current live media of Fedora 24 Workstation x86_64 exhibit both x86_64 and i686+PAE kernels which is also unusual but at least enable the user to boot the system successfully.

Comment 1 David Shea 2016-03-02 18:37:45 UTC


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