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:

After having hit "Start Discovery" button in "ADD iSCSI STORAGE TARGET" panel, it's not possible to change the "iSCSI Initiator Name" because it's grayed out.
This is an issue when a configuration mistake has been done (e.g. Network didn't get configured at that time the configuration was attempted).


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

anaconda RHEL 8.5.0


How reproducible:

Always

Steps to Reproduce:
1. Boot a system on the DVD for installation
2. Add "Target IP Address" but don't change "iSCSI Initiator Name"
3. Hit "Start Discovery"

  Discovery will fail because there is no network configured at that time

4. Configure the network and go back to "ADD iSCSI STORAGE TARGET" panel

Actual results:

No way to change "iSCSI Initiator Name"

Expected results:

Can change "iSCSI Initiator Name"

Additional info:

Created attachment 1878084 [details]
Initial "ADD iSCSI STORAGE TARGET"

In this initial configuration I changed Target IP Address but "forgot" to change the initiator

Created attachment 1878085 [details]
After clicking the "Start Discovery"

Because network is down, "Start Discovery" failed. Starting now, initiator field is always grayed out.

Created attachment 1878086 [details]
Field grayed out

Can't change Initiator after having brought the network up

upstream PR: https://github.com/storaged-project/blivet/pull/1112

rhel-9 clone: bug 2221935

upstream PR for RHEL 8: https://github.com/storaged-project/blivet/pull/1146

updates image for RHEL 8.8 (blivet + anaconda changes): https://vtrefny.fedorapeople.org/img/rhbz2084043_8-8.img

Checked that anaconda-33.16.9.4-1.el8 and python-blivet-3.6.0-7.el8 are in nightly compose RHEL-8.9.0-20230812.18.

Executed automated iSCSI tests using compose RHEL-8.9.0-20230812.18 and no regressions have been found.

Moving to VERIFIED.

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 (python-blivet 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:7004