1001705 – Failure when adding new record: "Error while adding record: no available memory"

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1001705 - Failure when adding new record: "Error while adding record: no available memory"

Summary: Failure when adding new record: "Error while adding record: no available memory"

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	iscsi-initiator-utils
Sub Component:
Version:	6.5
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	high
Target Milestone:	rc
Target Release:	---
Assignee:	Chris Leech
QA Contact:	Bruno Goncalves
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1049922 1066116
TreeView+	depends on / blocked

Reported:	2013-08-27 14:40 UTC by Gadi Ickowicz
Modified:	2014-08-22 01:41 UTC (History)
CC List:	9 users (show)
Fixed In Version:	iscsi-initiator-utils-6.2.0.873-8.el6
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Clones:	1049922 1066116 (view as bug list)
Environment:
Last Closed:	2013-11-21 23:10:33 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
tar file of /var/lib/iscsi (30.00 KB, application/x-tar) 2013-08-27 14:40 UTC, Gadi Ickowicz	no flags	Details
vdsm logs (1.23 MB, application/x-gzip) 2013-08-27 14:44 UTC, Gadi Ickowicz	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2013:1700	0	normal	SHIPPED_LIVE	iscsi-initiator-utils bug fix and enhancement update	2013-11-20 21:52:07 UTC

Description Gadi Ickowicz 2013-08-27 14:40:44 UTC

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

Comment 1 Gadi Ickowicz 2013-08-27 14:44:25 UTC

Created attachment 791018 [details]
vdsm logs

Comment 5 Chris Leech 2013-08-27 21:01:05 UTC

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.

Comment 12 Bruno Goncalves 2013-09-12 13:59:46 UTC

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

Comment 13 errata-xmlrpc 2013-11-21 23:10:33 UTC

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

Note You need to log in before you can comment on or make changes to this bug.