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.

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

Created attachment 1859561 [details]
screenshot

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.