Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2063288

Summary: Make it clear that one device/partition will be created even when multiple disks are selected
Product: Red Hat Enterprise Linux 8 Reporter: Jan Stodola <jstodola>
Component: anacondaAssignee: Ondřej Zobal <ozobal>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.6CC: jikortus, jkonecny
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-33.16.8.7-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2133046 (view as bug list) Environment:
Last Closed: 2023-05-16 08:15:29 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
screenshot none

Description Jan Stodola 2022-03-11 17:45:34 UTC
Created attachment 1865509 [details]
screenshot

Description of problem:
The window for selecting the disks to be used for a mount point doesn't say clearly that only one of the selected devices will be used.
This could be confusing to the users, especially when configuring mount points/partitions that the user would like to have on multiple drives, like the biosboot partition. See bug 1956573.

Version-Release number of selected component (if applicable):
RHEL-8.6
anaconda-33.16.6.6-1.el8

How reproducible:
Always

Steps to Reproduce:
1. Run graphical installation on a system with multiple disks
2. Proceed to the custom partitioning
3. Create for example a biosboot partition
4. Click the "Modify" button to select the device the partition will be placed on

Actual results:
The window says:
"Select one or more disks this device may reside on."
This could be understood that the device might be created on all of them.

Expected results:
It would be helpful to add a note that only one of the selected devices will be used for the device.

Comment 2 Jan Stodola 2022-10-07 16:11:03 UTC
RHEL-9 clone - bug 2133046

Comment 4 Jan Stodola 2023-01-10 16:17:54 UTC
PR: https://github.com/rhinstaller/anaconda/pull/4440

Comment 8 Jan Stodola 2023-02-14 12:53:41 UTC
Checked that anaconda-33.16.8.7-1.el8 is in nightly compose RHEL-8.8.0-20230209.2

Moving to VERIFIED

Comment 10 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