Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1669609 - Server network installer fails to install bootable kernel 4.20.3-200.fc29.x86_64
Summary: Server network installer fails to install bootable kernel 4.20.3-200.fc29.x86_64
Keywords:
Status: CLOSED DUPLICATE of bug 1669256
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-25 19:03 UTC by Need Real Name
Modified: 2019-01-28 10:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-28 10:04:46 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Need Real Name 2019-01-25 19:03:40 UTC 
Description of problem:

Network installer ISO for custom "standard" components results in non-bootable system.

Version-Release number of selected component (if applicable):


How reproducible:

We first encountered this with failed kickstart installs on 2018-01-24
where the same kickstart recipe worked for Fedora 29 the week before.

The error can be reproduced with a manual GUI installation.

Steps to Reproduce:
1. Prepare a qemu-kvm VM with blank disk via libvirt/virt-manager
2. Boot Fedora-Server-netinst-x86_64-29.1.2.iso
3. Do minimal custom install via GUI

I chose custom partitioning but select the item to create /, /boot/, and swap automatically with the usual LVM partitioning scheme.

I chose "nearest mirror" for software source.

I chose custom install, minimal profile, and optional "standard" group.

Actual results:

Installer runs to completion, but resulting VM only bootstraps to 
the grub CLI. There are no bootable menu items.

Expected results:

New install should boot.

Additional info:

I can see that the /boot/ volume contains only an initramfs image for 4.20.3-200.fc29.x86_64 but no corresponding vmlinuz nor System.map. As a result, the grub.cfg doesn't have any boot items defined.

On existing systems with Fedora 29, dnf automatic seems to have installed the same kernel normally. So there seems to be a difference between an update on a live system and via anaconda.
Comment 1 Need Real Name 2019-01-26 00:05:49 UTC 
After further search, I guess this might be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1669256 which describes a systemd package dependency issue that causes the kernel-install step to fail if openssl-libs is not installed when the kernel-core package is installed from the updates repo.
Comment 2 Vendula Poncova 2019-01-28 10:04:46 UTC 

*** This bug has been marked as a duplicate of bug 1669256 ***
Note You need to log in before you can comment on or make changes to this bug.