Description of problem:

Adding  ISCSI LUN's  via GUI creates target files under host directory with incorrect node.tpgt values. Later creates an entry for the original LUN ID and ends up with duplicate logins to the same ISCSI targets. 

Version-Release number of selected component (if applicable):

vdsm-4.19.28-1.el7ev.x86_64
iscsi-initiator-utils-6.2.0.874-4.el7.x86_64


How reproducible:

* Try to attach a direct LUN via ISCSI having LUN ID different to 1 from the RHV GUI and you end up with a default file under /var/lib/iscsi/nodes/*****/default that has the value as node.tpgt as 1.

Steps to Reproduce:

1. Use a target with LUN ID different from 1 for example as follows 
   
# iscsiadm -m session  
tcp: [166] 192.168.xx.xx:3260,2460 iqn.2007-11.com.xxxxxxxxx:xxxxxxxxxxxxxxxxxxxxxxxxx (non-flash)
                              ^^^^^

2. Add the disk as direct LUN via  RHV GUI for a VM with discovery and logging in. 

3. This creates a file under /var/lib/iscsi/nodes/xxxxxxx/default for as follows

drw-------. 2 root root 4096 Sep 20 13:42 192.168.xx.xx,3260,1


4.1  Starting/Migrating  the VM from host A to Host B and migrating back to A  ends up with another file for 

drw-------. 2 root root 4096 Sep 20 13:42 192.168.xx.xx,3260,2460

4.2 Shutting down the VM and doing a manual discovery and login creates another 2460 file resulting in multiple connections onto the host. 

Actual results:

* Creates a stale file for node.tpgt =1 
* Ends up with duplicate logins to the same target with node.tpgt =1 and node.tpgt = (original_hardware number) . eg : 2460 for Nimble Storage CS1000 

Expected results:

* Login to an ISCSI target with correct LUN number showing up on node.tpgt .

Additional info: