Bug 1569644

Summary:	Firmware provided ramdisk images ignored as install media
Product:	[Fedora] Fedora	Reporter:	ardb
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	anaconda-maint-list, jonathan, kellin, mkolman, pjones, vanmeeuwen+fedora, v.podzimek+fedora, vponcova, wwoods
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-28 19:56:13 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 ardb 2018-04-19 16:16:22 UTC

Description of problem:

When installing Fedora 28 netinst via HTTP boot, the installer boots into the kernel, but does not detect the .iso image block device (/dev/pmem0) that the non-volatile memory subsystem creates for the firmware provided ramdisk holding the .iso image (which is exposed to the OS via the NFIT ACPI table)

Booting the exact same image via USB works fine, and in this case, the .iso image is exposed as /dev/sda

Version-Release number of selected component (if applicable):
Fedora-Server-netinst-aarch64-28-20180415.n.0.iso

How reproducible:


Steps to Reproduce:
1. Use a HTTP boot capable system to boot the above image
2. Wait for the kernel to boot
3. Observe that the boot stalls at '[  OK  ] Reached target Basic System'

Actual results:
The boot stalls.

Expected results:
The boot proceeds in the same way as it does when booting the same image from USB

Additional info:
/proc/partitions and blkid both list /dev/pmem0 with the expected FS type, label name etc.

Comment 1 Martin Kolman 2018-04-19 16:29:14 UTC

Adding Peter Jones to CC as our bootloader guru.

Comment 2 Ben Cotton 2019-05-02 21:54:34 UTC

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 3 Ben Cotton 2019-05-28 19:56:13 UTC

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.