Bug 2149425

Summary: [RFE] iSCSI remove 256 LUNs limit in targetcli/rtslib
Product: Red Hat Enterprise Linux 8 Reporter: Sam Wachira <swachira>
Component: python-rtslibAssignee: Maurizio Lombardi <mlombard>
Status: CLOSED MIGRATED QA Contact: Martin Hoyer <mhoyer>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.7CC: mhoyer, sostapov
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-23 12:55:51 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sam Wachira 2022-11-29 20:59:49 UTC
Description of problem:
- The RHEL 7.5 and later kernels no longer have a 256 LUNs limit for iSCSI after rebasing LIO on a later version.
- However, the 256 LUNs limit remains set in the userspace utilities targetcli/rtslib.
- This RFE is a request for this limit to be removed.

Version-Release number of selected component (if applicable):
targetcli-2.1.53-2.el8
python3-rtslib-2.1.75-4.el8

Actual results:
- Unable to create and manage more than 256 LUNs using the targetcli/rtslib utilities.

Expected results:
- Ability to create and manage more than 256 LUNs.

Additional info:
- Kernel patch backported to kernel-3.10.0-862.el7 to remove the 256 LUNs limit - private BZ#1366062.
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=196e2e2aa362850bf45bcb14b9517124b23b921e)

Comment 2 Maurizio Lombardi 2022-12-01 14:43:19 UTC
Changing the component to rtslib

Comment 3 Maurizio Lombardi 2022-12-01 14:44:59 UTC
Patch submitted to upstream: https://github.com/open-iscsi/rtslib-fb/pull/191

Comment 5 RHEL Program Management 2023-09-23 12:55:33 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-23 12:55:51 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.