Bug 2001346

Summary:	Blivet-gui in installer will default to MBT instead of selected GPT if layout error occurs
Product:	[Fedora] Fedora	Reporter:	Stephen Snow <s40w5s>
Component:	blivet-gui	Assignee:	Vojtech Trefny <vtrefny>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	34	CC:	mkolman, vtrefny
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-08 01:05: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:

Description Stephen Snow 2021-09-05 16:14:53 UTC

Description of problem:During installation of Fedora Linux F34 Silverblue using the Blivet-gui of the installer to setup disk/volume/subvolume layout on a BIOS based system with multiple physical disks; If an error is caught by blivet upon pressing done, the partition type (MBR or GPT) selected previously defaults to MBR  for all drives, not just the one with the error. A user must then review every option for all devices to ensure GPT is still selected for example.


Version-Release number of selected component (if applicable):Fedora Linux F34 Silverblue


How reproducible:Every time


Steps to Reproduce:
1.Start installation as per normal using Silverblue installation ISO
2.Use Advanced Blivet-gui to setup multiple devices for storage.
3.Make an error in your setup, like forget to format the BiosBoot partition, or don't create an ext4 partition to mount at /boot

Actual results:When reviewing and correcting the error caught, the partition choice for devices changes to the default MBR scheme instead of the selected GPT


Expected results:Maintain user selected partition layout


Additional info:This has burnt me in the past so I wanted to share. Since I am running a BIOS system, I thought it was possibly related to expecting to use MBR instead of GPT.

Comment 1 Ben Cotton 2022-05-12 16:41:35 UTC

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.

Comment 2 Ben Cotton 2022-06-08 01:05:50 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.