Red Hat Bugzilla – Bug 978003
Ignores silently non existing paths
Last modified: 2018-01-24 14:20:14 EST
+++ This bug was initially created as a clone of Bug #910831 +++
Description of problem:
Write in the configuration file a path that don't exist:
First path exist, and the second one don't exist. If you start tgtd
with this configuration it will start correctly without giving a single warning. Neither it writes anything in /var/log/messages
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a config file like the one showed, with one existing path and another that don't exist.
tgtd is launched without any error/warning, and the backing store that don't exist just don't show up.
At least give a warning somewhere saying that the device don't exist. Notice that if the file exist, but tgtd is not able to access to it, it already gives an error on /var/log/messages:
Feb 13 17:23:31 trasno tgtd: tgtd: backed_file_open(92) Could not open /mnt/images/iscsi/f14_64.img, Permission denied
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: