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 2221935

Summary: [RHEL-9] Can't change iSCSI Initiator Name once "Start Discovery" has been hit once
Product: Red Hat Enterprise Linux 9 Reporter: Jan Stodola <jstodola>
Component: python-blivetAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.2CC: blivet-maint-list, japokorn, jfindysz, jikortus, jkonecny, jstodola, mfalz, release-test-team-automation, rmetrich, rvykydal, sbarcomb, tbzatek, vtrefny
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: python-blivet-3.6.0-9.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2083139
: 2223977 (view as bug list) Environment:
Last Closed: 2023-11-07 08:32:40 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: 2221932, 2223977    

Description Jan Stodola 2023-07-11 10:32:54 UTC
+++ This bug was initially created as a clone of Bug #2083139 +++

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:

--- Additional comment from Vojtech Trefny on 2023-03-27 15:25:14 CEST ---

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

Comment 5 Jan Stodola 2023-08-14 09:13:42 UTC
Checked that anaconda-34.25.3.8-1.el9 and python-blivet-3.6.0-9.el9 are in nightly compose RHEL-9.3.0-20230812.0.

Executed automated iSCSI tests using compose RHEL-9.3.0-20230812.0 and no regressions have been found.

Moving to VERIFIED.

Comment 7 errata-xmlrpc 2023-11-07 08:32:40 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 (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:6435