Bug 1859514

Summary: failed to change device type after set it to btrfs
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: anaconda-maint-list, jkonecny, jonathan, kellin, vanmeeuwen+fedora, vponcova, vslavik, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-12 11:24:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screencast
none
storage.log
none
anaconda.log none

Description lnie 2020-07-22 10:10:48 UTC
Created attachment 1702046 [details]
screencast

Description of problem:
Boot Fedora-Server-dvd-x86_64-Rawhide-20200721.n.0.iso with virt-manager,
Set Device type to btrfs,and then try to set it back to LVM,but it fails all the time with"Device does not support RAID level selection single",please see the attached video for more information,thanks.


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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2020-07-22 10:12:12 UTC
Created attachment 1702047 [details]
storage.log

Comment 2 lnie 2020-07-22 10:12:37 UTC
Created attachment 1702048 [details]
anaconda.log

Comment 3 Ben Cotton 2020-08-11 13:48:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 4 Vladimír Slávik 2020-08-11 16:24:16 UTC
Confirmed with anaconda 33.24-1 + last master revision as of posting. This happens when switching from btrfs to anything else, and after the message pops up, the device type is changed back to btrfs. Further clicking around can lead to other wrong raid levels, such as RAID0 for standard partition etc. Guess the raid level isn't reset or synced properly, but I don't know enough about this to be sure.

Comment 5 Vendula Poncova 2020-08-12 11:24:50 UTC

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