Bug 715312

Summary: iscsiadm: cannot login to node when db exceeds 190 nodes
Product: Red Hat Enterprise Linux 6 Reporter: Dafna Ron <dron>
Component: iscsi-initiator-utilsAssignee: Andy Grover <agrover>
Status: CLOSED WORKSFORME QA Contact: Storage QE <storage-qe>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: coughlan, cpelland, czhang, danken, ddumas, dron, hateya, iheim, mchristi, syeghiay, yeylon, zliu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 715327 (view as bug list) Environment:
Last Closed: 2011-09-18 13:25:14 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: 636013, 682015, 715327    
Attachments:
Description Flags
log none

Description Dafna Ron 2011-06-22 14:21:24 UTC
Created attachment 506014 [details]
log

Description of problem:

working with the rhevm and iscsi I was trying to connect my host to my iscsi lun. 
I was getting an error for command: /sbin/iscsiadm -m node -T Dafna-blonds-Linux -l -p 10.35.64.10:3260

after some digging we found that we have exceeded 190 targets on the same connection and there for were unable to login. 
 
after removing the nodes under /var/lib/iscsi/nodes/*/*/default and discover again -  we were able to connect again to the storage. 

why are we limited to 190 targets? 


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

iscsi-initiator-utils-6.2.0.872-21.el6.x86_64

How reproducible:


Steps to Reproduce:
1. exceed 190 targets under same connection and try to login to lun
2.
3.
  
Actual results:

you cannot login

Expected results:

exceed 190 nodes limit 

Additional info: vdsm log which can show the error we were getting

Comment 1 Dan Kenigsberg 2011-06-22 20:34:15 UTC
On a second thought, it does not seem to be that the db size puts the limit per se.

Thread-1245::DEBUG::2011-06-22 12:33:11,118::iscsi::372::Storage.Misc.excCmd::(addiSCSIPortal) '/usr/bin/sudo -n /sbin/iscsiadm -m discoverydb -t sendtargets -p 10.35.64.10:3260 --discover'

prints to stderr multiple lines like

iscsiadm: Could not add/update [tcp:[hw=,ip=,net_if=,iscsi_if=default] 10.35.64.10,3260,1 iqn.2010-03.com:server.target.moran-50g-07]
iscsiadm: Could not stat /var/lib/iscsi/nodes//,3260,-1/default to delete node: No such file or directory

reports success (rc=0) but presumably does not updates the discoverydb.

Does this make any sense?

Comment 2 Mike Christie 2011-06-22 21:33:29 UTC
(In reply to comment #1)
> iscsiadm: Could not add/update [tcp:[hw=,ip=,net_if=,iscsi_if=default]
> 10.35.64.10,3260,1 iqn.2010-03.com:server.target.moran-50g-07]
> iscsiadm: Could not stat /var/lib/iscsi/nodes//,3260,-1/default to delete node:
> No such file or directory

This is a bug in the iscsi tools. We have been chasing this in another bz (https://bugzilla.redhat.com/show_bug.cgi?id=656284), but have not been able to replicate it lately. Is this a system in red hat, and if so can I login (send me the login info to mchristi).

Comment 3 Dafna Ron 2011-06-26 17:02:41 UTC
it happened again on one of my hosts - sending the connection details to Mike.