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.
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.
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.