Bug 2051517 - Provide information telling why it's not possible to start iSCSI discovery
Summary: Provide information telling why it's not possible to start iSCSI discovery
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: anaconda
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1942219
TreeView+ depends on / blocked
 
Reported: 2022-02-07 12:08 UTC by Jan Stodola
Modified: 2023-08-07 07:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-07 07:28:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (82.45 KB, image/png)
2022-02-07 12:09 UTC, Jan Stodola
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-111336 0 None None None 2022-02-07 12:11:43 UTC

Description Jan Stodola 2022-02-07 12:08:03 UTC
Description of problem:
The "Add iSCSI storage target" dialog window doesn't provide information why the "Start Discovery" button is inactive. When the user enters an invalid IP address or iSCSI initiator name, anaconda should point out what field is not correct.

Version-Release number of selected component (if applicable):
RHEL-9.0.0-20220206.3
anaconda-34.25.0.25-1.el9

How reproducible:
Always

Steps to Reproduce:
1. Start graphical installation
2. Proceed to the Installation Destination spoke
3. Add a disk...
4. Add iSCSI Target...
5. Enter an invalid iSCSI initiator name: "iqn.1994-5.com.redhat:fbd59e9de9f4"
6. Enter Target IP Address: "192.168.169.170"

Actual results:
The "Start Discovery" button is inactive (this is expected due to an incorrect initiator name), but there is no explanation why it is not possible to start iSCSI discovery.

Expected results:
The user is informed why it's not possible to start iSCSI discovery.
For example: "The iSCSI Initiator name is invalid."
Such information should also be displayed for an incorrect IP address.

Additional info:
* Rules for iSCSI names are defined at: https://datatracker.ietf.org/doc/html/rfc7143#section-4.2.7.4
* Reporting based on feedback in bug 2046654

Comment 1 Jan Stodola 2022-02-07 12:09:23 UTC
Created attachment 1859561 [details]
screenshot

Comment 4 RHEL Program Management 2023-08-07 07:28:19 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.