Created attachment 1957298 [details] anaconda.log Description of problem: Installation to a NVMe device using the server DVD and no network fails due to the nvme-cli package not being on the DVD Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Boot from DVD/usb on a machine with an NVMe disk 2. Do a default install without enabling network Actual results: Installation will fail due to missing nvme-cli package Expected results: Installation will not fail Additional info:
Proposed as a Blocker for 38-final by Fedora user tflink using the blocker tracking app because: This violates the F38 Final criterion: The installer must be able to use all supported local and remote package and installer sources.
Installing to the same machine with F37 Server DVD and no network access results in a successful install as expected. It sounds like a change to blivet since F37 is responsible for the new package requirement and comps was never updated. adamw has already sent a pull request to comps to fix the issue: https://pagure.io/fedora-comps/pull-request/829
This installation was done using a DVD iso burned to usb stick via dd on to a desktop/server machine that was connected to network but that wasn't enabled for installation.
Fedora 38 RC 1.5 installs properly on Slimbook with NVMe storage and no network.
On the same Slimbook, we didn't get a traceback with RC 1.4 as Tim did, but we got an interactive prompt saying that nvme-cli package is missing, and whether we want to ignore that error and continue with installation, or exit. Continuing the installation finished OK. This happened both for graphical and text installation. Tim, were you using a kickstart? Or some other specific approach?
Anyway, in RC 1.5 it works without issues, setting as verified.
The interactive dialog is visible in bug 2178508. Marking as a duplicate.
*** Bug 2178508 has been marked as a duplicate of this bug. ***
The traceback Tim reported is printed only when I hit "No" in the interactive dialog. I haven't been able to make anaconda crash right away, without the dialog, even when using kickstart. However, my kickstart skills are now rusty and I've had problems when forcing a non-interactive kickstart install, so it might be a problem on my part. It's likely that some specific install fails right away.
(In reply to Kamil Páral from comment #5) > On the same Slimbook, we didn't get a traceback with RC 1.4 as Tim did, but > we got an interactive prompt saying that nvme-cli package is missing, and > whether we want to ignore that error and continue with installation, or > exit. Continuing the installation finished OK. This happened both for > graphical and text installation. > > Tim, were you using a kickstart? Or some other specific approach? No, I just interpreted the interactive prompt as a failed install and didn't attempt to continue without the package even though it didn't generate a traceback.
Created attachment 1957356 [details] screenshot of the warning attaching the screenshot here for convenience.
This was discussed at today's go/no-go meeting - https://meetbot.fedoraproject.org/fedora-meeting/2023-04-13/f38_final_gono-go_meeting.2023-04-13-17.05.html - and accepted as a blocker as a violation of "The installer must be able to complete an installation using any supported locally connected storage interface" combined with "Any installation method or process designed to run unattended must do so. There should be no prompts requiring user intervention", in the case of an attempted unattended install of Server DVD to NVMe storage.
I did some testing with kickstarts: Using a kickstart that installs from a rc1.4 cdrom in graphical mode, it stops at the same prompt you see when doing an interactive install. If you continue the install, it has the same behavior. Using a kickstart that installs from a rc1.4 cdrom in text mode, you get the same prompt but rendered as a text tui. Continuing the install produces a working system. Using a kickstart that installs from a mirrorlist url, the installation completes without issue.
This issue is not present in F38 RC 1.6
This can be closed, the fix is in comps so there's nothing further to do.