Bug 675938

Summary:	[RFE] [tgt-admin] - please extend the output provided by '-dump' option
Product:	Red Hat Enterprise Linux 6	Reporter:	Max Benenson <mbenenso>
Component:	scsi-target-utils	Assignee:	Andy Grover <agrover>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.0	CC:	agrover, ssaha
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-03 21:40:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	767187

Description Max Benenson 2011-02-08 10:48:53 UTC

Description of problem:
Executing 'tgt-admin -dump' does not display full target related information.

Version:
scsi-target-utils-1.0.4-3.el6.x86_64

Steps to Reproduce:
1. Run 'tgt-admin -dump'
  
Actual results:
Will display the target names and the backing store names only (in my case).

Expected results:
The output should include all relevant information for each target, like scsi_id, scsi_sn of the devices, write-cache mode, LUN number etc.

Additional info:
The implementation of this RFE will allow an advanced target configuration from within user's source code using tgadm and tgt-admin utilities. For example, right now I have few targets defined manually in targets.conf file and I want to remove one of them using my custom Python code. If I will just remove it using tgtadm or tgt-admin the changes won't be persistent since the targets.conf still contains the relevant information regarding the removed target and simple reload of tgtd service will restore the target. BUT, if 'tgt-admin -dump' will provide a detailed targets info it will make possible simple redirect its output into targets.conf file in order to make the changes persistent without any worries to wipe out any essential target info.

Another way to deal with the situation above is adding ability to execute all tgt-admin commands in persistent mode, e.g. deleting the target using 'tgt-admin --delete target_name --force' will remove it also from the targets.conf file.

Comment 2 Mike Christie 2011-02-14 21:00:14 UTC

Too late for 6.1. How about 6.2?

Comment 3 Suzanne Logcher 2011-03-28 20:29:46 UTC

Since RHEL 6.1 External Beta has begun, and this bug remains 
unresolved, it has been rejected as it is not proposed as an 
exception or blocker.  It has been moved to RHEL 6.2 since 
it is a FutureFeature request.

Comment 4 Sayan Saha 2011-05-24 20:04:03 UTC

No capacity in RHEL 6.2. Re-evaluate the request for RHEL 6.3.

Comment 6 Andy Grover 2012-02-03 21:40:54 UTC

Can't fix everything, sorry, closing.