Bug 2547382

Summary:	Installer does not enforce root filesystem reformat on LVM and Stratis leading to crash during installation
Product:	[Fedora] Fedora	Reporter:	Vojtech Trefny <vtrefny>
Component:	anaconda	Assignee:	Vojtech Trefny <vtrefny>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	45	CC:	alpha, anaconda-maint, kkoukiou, mkolman, rhbz, w
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:	AcceptedFreezeException
Fixed In Version:	anaconda-45.29-1.fc45	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-10-16 23:56:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2406955

Description Vojtech Trefny 2026-10-07 10:41:05 UTC

When reusing an existing filesystem for / (root), Anaconda is supposed to check whether the filesystem is empty or not and for filesystems that are not empty, re-creating the format should be enforced.
However this check doesn't work with LVM and Stratis (and potentially other complex storage devices) because when Anaconda tries to mount the device it is not set up. The mount operation silently fails:

-----
INFO:program:Running... mount -t xfs -o ro /dev/mapper/vgroup0-root /tmp/blivet-tmp.vgroup0-rootrfffnbk5
INFO:program:stderr:
INFO:program:b"mount: /tmp/blivet-tmp.vgroup0-rootrfffnbk5: fsconfig() failed: /dev/mapper/vgroup0-root: Can't lookup blockdev."
INFO:program:b'       dmesg(1) may have more information after failed mount system call.'
DEBUG:program:Return code: 32
-----

Installing on a filesystem that already contains existing (older) installation of Fedora than can randomly during the payload installation.


Reproducible: Always

Comment 1 Fedora Blocker Bugs Application 2026-10-07 11:02:34 UTC

Proposed as a Freeze Exception for 45-final by Fedora user vtrefny using the blocker tracking app because:

 Reusing filesystem with an old Fedora installation can lead to crash during the new payload installation (conflict between the existing "old" files and the new files that are being copied/installed).

This does not happen with btrfs and also requires user to explicitly disable the recreate option which is enabled by default for / so I don't think this is serious enough to be a blocker.

Comment 2 Adam Williamson (Fedora) 2026-10-08 18:16:20 UTC

+3 in https://forge.fedoraproject.org/quality/blocker-review/issues/2206 , marking accepted FE.

Comment 3 Vojtech Trefny 2026-10-09 11:15:51 UTC

upstream PR: https://github.com/rhinstaller/anaconda/pull/7344

Comment 4 Fedora Update System 2026-10-13 05:56:36 UTC

FEDORA-2026-d8c35ffdd6 (anaconda-45.29-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-d8c35ffdd6

Comment 5 Fedora Update System 2026-10-14 02:17:26 UTC

FEDORA-2026-d8c35ffdd6 has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-d8c35ffdd6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d8c35ffdd6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-10-16 23:56:18 UTC

FEDORA-2026-d8c35ffdd6 (anaconda-45.29-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.