Description of problem:
If single entry is made of discovery address, it works fine, and target is visible.
But if there is dual entry, then /var/log/messages gives a warning that
duplicate entry is ignored but this does not work fine.
/etc/iscsi.conf says, in case of duplicate entries, the last setting in the file
takes precedence. So this should have worked, but it doesn't.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make entry in the /etc/iscsi.conf with OutgoingUsername and OutgoingPassword
2. This OutgoingUsername and OutgoingPassword is also configured at the target end.
3. With the start of the driver on the host, the targets are visible, since the
access details are successful.
4. Now in the /etc/iscsi.conf file, just duplicate the single line:
5. Restart the driver.
6. Target discovery fails
Target discovery fails, though /var/log/messages tells that duplicate entry is
/etc/iscsi.conf file says:
"If more that one entry exists for any given parameter (either global or
# local), the last entry has precedence."
With this, the first discovery address should have been ignored, but the second
one should have taken the precedence and the discovery should have gone through.
If this is not the case, then the documentation needs a change about the
statement mentioned above.
Contents of /etc/iscsi.conf file:
[root@cnitin-linux-6 linux-iscsi]# grep -v "#" /etc/iscsi.conf
Settings on MDS:
- chap authentication on interface gige 2/1
Jul 19 15:45:55 cnitin-linux-6 iscsid: Connected to Discovery Address
Jul 19 15:45:55 cnitin-linux-6 iscsid: ignoring duplicate discovery
address 10.1.1.80 in the config file
Jul 19 15:45:55 cnitin-linux-6 iscsid: Login failed to authenticate with
Jul 19 15:45:55 cnitin-linux-6 iscsid: Discovery login to 10.1.1.80
rejected: initiator error (02/01), non-retryable, giving up
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.