Red Hat Bugzilla – Bug 1001705
Failure when adding new record: "Error while adding record: no available memory"
Last modified: 2014-08-21 21:41:50 EDT
Created attachment 791017 [details] tar file of /var/lib/iscsi Description of problem: when vdsm attempts to add a new record to the iscsi database it fails with the following error, and rc = 3: iscsiadm: Error while adding record: no available memory. The commands that were run: /usr/bin/sudo -n /sbin/iscsiadm -m discoverydb -t sendtargets -I default -p <server> --discover (succeeds) /usr/bin/sudo -n /sbin/iscsiadm -m node -T <target> -I default -p <server> --op=new (fails) Version-Release number of selected component (if applicable): vdsm-4.12.0-72.git287bb7e.el6ev.x86_64 iscsi-initiator-utils-6.2.0.873-5.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Add second host to existing iscsi datacenter on rhevm Actual results: Host becomes non-operational due to error when connecting to storage Additional info: tar file of /var/lib/iscsi attached
Created attachment 791018 [details] vdsm logs
This looks like a regression caused by a problem in the fix for #884427. The GLOB_NOMATCH return code is being passed along in idmb_rec_write_old, and later taken to be ISCSI_ERR_NOMEM as they are the same value. A no-match in glob here is not an error, and the return code needs to be reset to 0.
Reproduced the same issue on iscsi-initiator-utils-6.2.0.873-6 iscsiadm -m discoverydb -t sendtargets -I default -p <server> --discover [ OK ] iscsid: [ OK ] [root@storageqe-17 ~]# iscsiadm -m node -T <target> -I default -p <server> --op new iscsiadm: Error while adding record: no available memory ---- Fixed on iscsi-initiator-utils-6.2.0.873-8.el6 iscsiadm -m discoverydb -t sendtargets -I default -p <server> --discover [ OK ] iscsid: [ OK ] [root@storageqe-17 ~]# iscsiadm -m node -T <target> -I default -p <server> --op new New iSCSI node [tcp:[hw=,ip=,net_if=,iscsi_if=default] <server>,3260,-1 <target>] added
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1700.html