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.

iscsid is doing automatic rescans on startup, login, and reception of AEN/AER packets from the target node, and this is problematic for some deployments where this is not desired.

Such is the case of Cinder, the block storage service in OpenStack, were we may have very lively targets that are constantly changing exposed LUNs, and the autoscan mechanism is just polluting our systems with paths that are being added and removed, because we have multiple systems accessing different LUNs in the same target, and they will only cleanup the ones they are actually interested in, and not the ones that are unexpectedly added to the system.

Ideally we would want to be able to configure the autoscan on a per session basis.

There's a proposal in progress upstream: https://github.com/open-iscsi/open-iscsi/pull/40

Patches from Gorka have been merged upstream

Fixing target release to 7.4 and setting z-stream request flags for customer issues

Martin, can QA cover this for 7.4?

(In reply to Chris Leech from comment #4)
> Martin, can QA cover this for 7.4?
I can, qe_ack+

Unfortunately the initial code had a bug, so we need to wait for the new pull request [1] to merge.

[1] https://github.com/open-iscsi/open-iscsi/pull/49

Tested by creating new session with 'node.session.scan = manual' set in '/etc/iscsi/iscsid.conf' and also by setting scan option for each session by 'iscsiadm -m session -r 1 -o update -n node.session.scan -v manual'.
Both 'auto' and 'manual' options worked as expected after reboot and login.

Tested with iscsi-initiator-utils-6.2.0.874-3.el7

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, 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-2017:2010