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 1253592

Summary:	RFE: targetd add support to access group operations
Product:	Red Hat Enterprise Linux 7	Reporter:	Bruno Goncalves <bgoncalv>
Component:	targetd	Assignee:	Tony Asleson <tasleson>
Status:	CLOSED ERRATA	QA Contact:	Martin Hoyer <mhoyer>
Severity:	medium	Docs Contact:	Milan Navratil <mnavrati>
Priority:	medium
Version:	7.4	CC:	mhoyer, mthacker, tasleson
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	7.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 20:43:39 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:	1385242

Description Bruno Goncalves 2015-08-14 08:12:02 UTC

Description of problem:
Current targetd on RHEL-7.2 does not allow access group operations. 

Libstoragemgmt supports targetd, but it is not possible to perform volume-mask nor volume-unmask, because targetd does not support it.

# lsmcli  -u "targetd://admin@localhost" access-group-create --name test --init iqn.1994-05.com.redhat:cbc17c91e2b --sys targetd
NO_SUPPORT(153): Please upgrade your targetd package to support access_group_create() 


Version-Release number of selected component (if applicable):
targetd-0.7.1-1.el7.noarch

Additional info:
Version 0.8.3 from Fedora supports it.

tested using targetd-0.8.3-1.fc22.noarch

Comment 5 Bruno Goncalves 2017-03-29 14:55:06 UTC

It looks good. Tested with:
targetd-0.8.5-1.el7.noarch
libstoragemgmt-targetd-plugin-1.4.0-2.el7.noarch

# lsmcli  -u "targetd://admin@localhost" access-group-create --name=lsm-igroup --init=iqn.1994-05.com.redhat:lsm-test-iqn --sys=targetd
ID         | Name       | Initiator IDs                       | System ID
-------------------------------------------------------------------------
lsm-igroup | lsm-igroup | iqn.1994-05.com.redhat:lsm-test-iqn | targetd

Comment 6 Bruno Goncalves 2017-04-28 14:35:07 UTC

Tony,

When we use the targetd plugin LIO is configured to use "0.0.0.0:3260" as port IP address, this do not allow IPv6 to discover the target. Is this okay? "0.0.0.0:3260" is what targetcli creates by default.

libstoragemgmt-1.4.0-3.el7
targetd-0.8.5-1.el7
targetcli-2.1.fb46-1.el7


# targetcli ls
o- / ......................................................................................................................... [...]
  o- backstores .............................................................................................................. [...]
  | o- block .................................................................................................. [Storage Objects: 1]
  | | o- vg-targetd:lsm-lun-update .................................. [/dev/vg-targetd/lsm-lun-update (2.0GiB) write-thru activated]
  | |   o- alua ................................................................................................... [ALUA Groups: 1]
  | |     o- default_tg_pt_gp ....................................................................... [ALUA state: Active/optimized]
  | o- fileio ................................................................................................. [Storage Objects: 0]
  | o- pscsi .................................................................................................. [Storage Objects: 0]
  | o- ramdisk ................................................................................................ [Storage Objects: 0]
  o- iscsi ............................................................................................................ [Targets: 1]
  | o- iqn.2003-01.org.linux-iscsi.storageqe-72.lab.eng.brq.redhat.com:targetd ........................................... [TPGs: 1]
  |   o- tpg1 ............................................................................................... [no-gen-acls, no-auth]
  |     o- acls .......................................................................................................... [ACLs: 1]
  |     | o- lsm-igroup .................................................... [(iqn.1994-05.com.redhat:lsm-test-iqn), Mapped LUNs: 1]
  |     |   o- mapped_lun0 ............................................................. [lun0 block/vg-targetd:lsm-lun-update (rw)]
  |     o- luns .......................................................................................................... [LUNs: 1]
  |     | o- lun0 ............................ [block/vg-targetd:lsm-lun-update (/dev/vg-targetd/lsm-lun-update) (default_tg_pt_gp)]
  |     o- portals .................................................................................................... [Portals: 1]
  |       o- 0.0.0.0:3260 ..................................................................................................... [OK]
  o- loopback ......................................................................................................... [Targets: 0]

Comment 7 Tony Asleson 2017-04-28 16:50:54 UTC

(In reply to Bruno Goncalves from comment #6)
> Tony,
> 
> When we use the targetd plugin LIO is configured to use "0.0.0.0:3260" as
> port IP address, this do not allow IPv6 to discover the target. Is this
> okay? "0.0.0.0:3260" is what targetcli creates by default.

Please write up an enhancement BZ for ipv6 support.

Comment 10 Martin Hoyer 2017-05-29 10:15:55 UTC

Tested with targetd-0.8.5-1.el7
Access group operations works. No regression found.

Comment 11 errata-xmlrpc 2017-08-01 20:43:39 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, 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:1982