RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1913035 - Only the last created Biosboot partition is visible in custom partitioning
Summary: Only the last created Biosboot partition is visible in custom partitioning
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Vendula Poncova
QA Contact: Release Test Team
Sagar Dubewar
URL:
Whiteboard:
: 1926108 2079710 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-05 19:27 UTC by Suraj Raskar
Modified: 2023-05-16 08:51 UTC (History)
10 users (show)

Fixed In Version: anaconda-33.16.8.5-1.el8
Doc Type: Bug Fix
Doc Text:
.Installer now lists all `PPC PreP Boot` or `BIOS Boot` partitions during custom partitioning Previously, when adding multiple `PPC PreP Boot` or `BIOS Boot` partitions during custom partitioning, the Custom Partitioning screen displayed only one partition of a related type. As a consequence, the Custom Partitioning screen did not reflect the real state of the intended partitioning layout, making the partitioning process difficult and non-transparent. With this update, the Custom Partitioning screen correctly displays all `PPC PreP Boot` or `BIOS Boot` partitions in the partitions list. As a result, users can now better understand and manage the intended partitioning layout.
Clone Of:
Environment:
Last Closed: 2023-05-16 08:15:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
See "biosboot1.png" where we see bios boot partition with bios boot is already created on vda1 and /boot is on vda2 (54.55 KB, image/png)
2021-01-05 19:27 UTC, Suraj Raskar 		no flags Details
refer "biosboot2.png" where additional biosboot is added and now it is on vda2 and /boot is on vda3, still we will be able to add new bios boot partition (54.31 KB, image/png)
2021-01-05 19:28 UTC, Suraj Raskar 		no flags Details
See "after_installation.png" for after installation status. (20.74 KB, image/png)
2021-01-05 19:29 UTC, Suraj Raskar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RTT-4937 0 None None None 2022-10-24 14:43:48 UTC
Red Hat Issue Tracker RTT-4938 0 None None None 2022-10-24 14:43:52 UTC
Red Hat Product Errata RHBA-2023:2748 0 None None None 2023-05-16 08:15:46 UTC

Description Suraj Raskar 2021-01-05 19:27:40 UTC 
Created attachment 1744694 [details]
See "biosboot1.png" where we see bios boot partition with bios boot is already created on vda1 and /boot is on vda2

Description of problem:
- Multiple bisboot partitions are getting created into the system at the time of installation in kvm environment.

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


How reproducible:
Always

Steps to Reproduce:

1. Attached RHEL 8 iso and proceed with the installation.

2. Select "Installation Destination"

3. Custom Configuration ---- > Select "Standard partition" from drop down list ---- > Create /boot partition (any size) ---- > Create "Bios Boot partition" (will be created of 2 MiB)

4. Try to create another "Bios Boot partition" it will be created but will not see under table where we see all the partitions ---- > similarly we can create more bios boot partitions.


Actual results:
- Multiple biosboot partition getting created.

Expected results:

1. It should not allow us to create another bios boot partition once we created one.

2. If it's getting created then we should see those partitions in the table where we see all the partitions.


Additional info:
Comment 1 Suraj Raskar 2021-01-05 19:28:38 UTC 
Created attachment 1744695 [details]
refer "biosboot2.png" where additional biosboot is added and now it is on vda2 and /boot is on vda3, still we will be able to add new bios boot partition
Comment 2 Suraj Raskar 2021-01-05 19:29:28 UTC 
Created attachment 1744696 [details]
See "after_installation.png" for after installation status.
Comment 3 Jan Stodola 2021-01-05 20:01:57 UTC 
I wonder if similar problem exists for the PrepBoot partition on ppc64le. Just a note to check when implementing/testing a fix for this bug.
Comment 4 Jan Stodola 2021-05-04 06:34:35 UTC 
*** Bug 1926108 has been marked as a duplicate of this bug. ***
Comment 5 Suraj Raskar 2021-12-10 18:11:39 UTC 
Hello Team,

Is there any updates on this BZ ? 

Any updates that we can share with the customer?
Comment 10 Jan Stodola 2022-05-09 15:16:08 UTC 
Just to clarify the expected result: The installer should allow to create multiple biosboot partitions (since each biosboot partition could be on a different disk), but the installer has to properly show every biosboot partition in the custom partitioning spoke. Currently only the last created biosboot partition is visible there.
Comment 11 Jan Stodola 2022-05-12 15:53:52 UTC 
*** Bug 2079710 has been marked as a duplicate of this bug. ***
Comment 15 Jan Stodola 2022-06-17 09:29:50 UTC 
related rhel-9 bug: bug 2093793
Comment 16 Jiri Konecny 2022-08-01 15:23:35 UTC 
Related Fedora bug 2088113
Comment 31 errata-xmlrpc 2023-05-16 08:15:29 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (anaconda bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2748
Note You need to log in before you can comment on or make changes to this bug.