Description of problem: Advanced Custom (blivet-gui), upon choosing raid1, while the setting does stick and seems to be accepted, the overview shows 2x the expected space. And when I go to 'display info about selected device' it shows data and metadata as 'none' which is not a valid profile for btrfs. The actual layout created is raid0. The problem does not happen in Custom. The actual layout created is raid1 as expected. Version-Release number of selected component (if applicable): anaconda-33.20-1.fc33.x86_64 blivet-data-3.2.2-2.fc33.noarch python3-blivet-3.2.2-2.fc33.noarch blivet-gui-runtime-2.1.14-2.fc33.noarch How reproducible: Always Steps to Reproduce: 1. Two vda devices chosen as targets 2. Advanced Custom (blivet-gui) path 3. Click + Device Type = Btrfs + check both vda and vdb + RAID level set to raid1 4. name=fedorap, mount point = /, click OK. Actual results: "display information about selected device" says data level none and metadata level none. Proceeding with the installation it uses raid0 for data and raid1 for metadata (mkfs.btrfs default) Expected results: raid1 for data and metadata Additional info:
Created attachment 1699053 [details] anacondalog
Created attachment 1699054 [details] program.log
Created attachment 1699055 [details] storage.log
Proposed as a Blocker for 33-final by Fedora user chrismurphy using the blocker tracking app because: final release criterion: The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration.
upstream PR: https://github.com/storaged-project/blivet-gui/pull/199
FEDORA-2020-7525f4fdf7 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-7525f4fdf7
FEDORA-2020-3cfdf1a75e has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3cfdf1a75e
FEDORA-EPEL-2020-82cc3846a3 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-82cc3846a3
FEDORA-2020-3cfdf1a75e has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3cfdf1a75e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3cfdf1a75e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-82cc3846a3 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-82cc3846a3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-7525f4fdf7 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-7525f4fdf7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7525f4fdf7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-7525f4fdf7 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-3cfdf1a75e has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-82cc3846a3 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.