Bug 2051517

Summary: Provide information telling why it's not possible to start iSCSI discovery
Product: Red Hat Enterprise Linux 9 Reporter: Jan Stodola <jstodola>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team>
Severity: low Docs Contact:
Priority: unspecified    
Version: 9.0CC: jkonecny, tbzatek, tstaudt
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-07 07:28:19 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:
Bug Depends On:    
Bug Blocks: 1942219    
Attachments:
Description Flags
screenshot none

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.