Bug 2237379 - anaconda uses the same default name for the second created volume device,if users create btrfs volume first
Summary: anaconda uses the same default name for the second created volume device,if u...
Keywords:
Status: CLOSED DUPLICATE of bug 2237375
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: anaconda-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F39BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2023-09-05 07:59 UTC by lnie
Modified: 2023-09-05 13:01 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-09-05 13:01:33 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
anaconda.log (6.06 KB, text/plain)
2023-09-05 07:59 UTC, lnie 		no flags Details
storage.log (1.55 MB, text/plain)
2023-09-05 08:00 UTC, lnie 		no flags Details
View All

Description lnie 2023-09-05 07:59:16 UTC 
Create btrfs volume,then create lvm or software raid volume you will find the device name is also blivet,just as the btrfs volume.
This will cause some problems:#2237375，#2236433，etc
FYI,if you create a third volume,the name will be different.

Reproducible: Always
Comment 1 lnie 2023-09-05 07:59:55 UTC 
Created attachment 1987031 [details]
anaconda.log
Comment 2 lnie 2023-09-05 08:00:49 UTC 
Created attachment 1987032 [details]
storage.log
Comment 3 Fedora Blocker Bugs Application 2023-09-05 08:10:19 UTC 
Proposed as a Freeze Exception for 39-beta by Fedora user lnie using the blocker tracking app because:

 This bug will introduce other bugs as described.
Comment 4 Vojtech Trefny 2023-09-05 13:01:33 UTC 
Marking as duplicate of rhbz#2237375 This is the same issue with different reproducer: device names are internally used as unique identifiers by both Anaconda and Blivet and we shouldn't allow creating two devices with the same name.

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