Bug 1876261 - Anaconda does not use UUID in fstab for Workstation with btrfs
Summary: Anaconda does not use UUID in fstab for Workstation with btrfs
Keywords:
Status: CLOSED DUPLICATE of bug 1860602
Alias: None
Product: Fedora
Classification: Fedora
Component: python-blivet
Version: 33
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Blivet Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1851166
TreeView+ depends on / blocked
 
Reported: 2020-09-06 19:19 UTC by Erich Eickmeyer
Modified: 2020-09-09 06:43 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-09 06:43:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Erich Eickmeyer 2020-09-06 19:19:42 UTC
Description of problem:
When installing Fedora Workstation 33 using btrfs, Anaconda (or blivet) populates /etc/fstab with the btrfs partition's logical location (/dev/sdxy) as opposed to UUID. This creates problems when Fedora is installed onto an external drive and that drive is moved to a different computer with a different configuration as it renders it unable to boot on that computer. This problem does not exist in my testing on the KDE spin or the Fedora Jam spin.

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

How reproducible:
Every time

Steps to Reproduce:
1. Attempt btrfs installation of Workstation onto external drive.
2. Boot new installation on installation computer.
3. Move external drive to a different computer and attempt to boot.

Actual results:
With /etc/fstab populated with the logical location (/def/sdxy), installation on external drive fails to boot.

Expected results:
Installation on external drive boots without issue.


Additional info:
This should be as simple as populating /etc/fstab with the UUID of the btrfs partition as opposed to the /dev/sdxy of the partition. This issue is only reproducible on Workstation.

Comment 1 Chris Murphy 2020-09-08 23:28:48 UTC
Sounds like a dup of bug 1860602.

Comment 2 Vojtech Trefny 2020-09-09 06:43:56 UTC

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


Note You need to log in before you can comment on or make changes to this bug.