Bug 2237379

Summary: anaconda uses the same default name for the second created volume device,if users create btrfs volume first
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: anacondaAssignee: anaconda-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 39CC: anaconda-maint, vslavik, vtrefny, w
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-05 13:01:33 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: 2143445    
Attachments:
Description Flags
anaconda.log
none
storage.log none

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 ***