Bug 784577

Summary: Plugin should not crash with empty records
Product: [Fedora] Fedora Reporter: Martin Kosek <mkosek>
Component: bind-dyndb-ldapAssignee: Adam Tkac <atkac>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: atkac, jkuncar, ovasik, pspacek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: bind-dyndb-ldap-1.1.0-0.8.a2.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-01 09:28:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin Kosek 2012-01-25 12:42:13 UTC
Description of problem:
Plugin crashes when an empty DNS record (an LDAP record with just idnsName attribute filled) is requested.

Record in LDAP:

# ldapsearch -Y GSSAPI -b idnsname=baz4,idnsname=example.com,cn=dns,SUFFIX
...
# baz4, example.com, dns, SUFFIX
dn: idnsname=baz4,idnsname=example.com,cn=dns,SUFFIX
objectClass: top
objectClass: idnsrecord
idnsName: baz4

# search result
search: 4
result: 0 Success

# numResponses: 2
# numEntries: 1


Version-Release number of selected component (if applicable):
bind-9.8.1-4.P1.fc16.x86_64
bind-dyndb-ldap-1.1.0-0.6.a1.fc16.x86_64

How reproducible:

Steps to Reproduce:
1. Create empty record in configured LDAP zone for bind-dyndb-ldap
2. Ask for this record, for example via `dig' tool
  
Actual results:
Bind crashes:

Jan 25 07:32:11 vm-068 named[25232]: cache.c:196: INSIST(!(((*rdatalist).head == ((void *)0)) ?        isc_boolean_true : isc_boolean_false)) failed, back trace
Jan 25 07:32:11 vm-068 named[25232]: #0 0x7fbe5feb84ab in ??
Jan 25 07:32:11 vm-068 named[25232]: #1 0x7fbe5e15d7ba in ??
Jan 25 07:32:11 vm-068 named[25232]: #2 0x7fbe5a6c5b34 in ??
Jan 25 07:32:11 vm-068 named[25232]: #3 0x7fbe5a6cec9a in ??
Jan 25 07:32:11 vm-068 named[25232]: #4 0x7fbe5a6c83f4 in ??
Jan 25 07:32:11 vm-068 named[25232]: #5 0x7fbe5fec0967 in ??
Jan 25 07:32:11 vm-068 named[25232]: #6 0x7fbe5fec76c1 in ??
Jan 25 07:32:11 vm-068 named[25232]: #7 0x7fbe5feaf38e in ??
Jan 25 07:32:11 vm-068 named[25232]: #8 0x7fbe5e17c948 in ??
Jan 25 07:32:11 vm-068 named[25232]: #9 0x7fbe5db32d90 in ??
Jan 25 07:32:11 vm-068 named[25232]: #10 0x7fbe5d06e48d in ??
Jan 25 07:32:11 vm-068 named[25232]: exiting (due to assertion failure)

Expected results:
Bind does not crash and returns a negative result for the requested record.

Comment 1 Petr Spacek 2012-02-07 15:40:03 UTC
(In reply to comment #0)
Described error appears only with psearch enabled.

Comment 3 Fedora Update System 2012-02-13 17:46:23 UTC
bind-dyndb-ldap-1.1.0-0.8.a2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/bind-dyndb-ldap-1.1.0-0.8.a2.fc16

Comment 4 Fedora Update System 2012-02-13 17:46:42 UTC
bind-dyndb-ldap-1.1.0-0.8.a2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/bind-dyndb-ldap-1.1.0-0.8.a2.fc15

Comment 5 Fedora Update System 2012-02-14 09:00:32 UTC
Package bind-dyndb-ldap-1.1.0-0.8.a2.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing bind-dyndb-ldap-1.1.0-0.8.a2.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1601/bind-dyndb-ldap-1.1.0-0.8.a2.fc15
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2012-03-01 09:28:51 UTC
bind-dyndb-ldap-1.1.0-0.8.a2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2012-03-01 09:34:43 UTC
bind-dyndb-ldap-1.1.0-0.8.a2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.