Description of problem: Two drives, intended workflow is a raid1 installation that can be booted with one drive missing. "Selected Disk and Boot Loader" doesn't allow two drives to be selected. Version-Release number of selected component (if applicable): anaconda-34.15-1 How reproducible: Always Steps to Reproduce: 1. BIOS qemu-kvm, two blank virtio drives 2. Installation Destination, select both drives 3. Full disk summary and bootloader to get to the Selected Disk and Boot Loader dialog 4. Choose both drives Actual results: UI disallows this. Only one can be selected. Bootloader is only installed on one drive. Expected results: I should be able to select both. Additional info: Happens whether the blank drives are 100G each, i.e. MBR is indicated. And when using inst.gpt. A similar problem happens in Custom partitioning where I can't create two BIOS Boot partitions. The left side UI with "mountpoint" suggests it's only on vdb1, but the Devices>Modify "Configure Mount Point" dialog for this BIOS boot shows two devices selected, and yet the Installation Summary shows only one BIOS Boot created, on vdb1.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This is still a bug and relates to bug 2088113 and is arguably a dup.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.