Can you please add steps to reproduce this issue? Thanks

(In reply to comment #2)
> Can you please add steps to reproduce this issue? Thanks

Of course. Details are written in upstream ticket:

1) IPA started
2) /etc/named.conf:

Add/modify those parameters in named.conf:

dynamic-db "ipa" {
        ...
        arg "uri ldap://127.0.0.1";
        arg "psearch yes";
        ...
};

3) service named stop
4) iptables-save > /tmp/iptables.backup; iptables -I INPUT -p tcp --dport 389 -j REJECT; iptables -I INPUT -p tcp --dport 636 -j REJECT
5) service named start
6) rndc reload

And now named crashes.

Thanks Adam!

Persistent search feature postponed to 6.4, as discussed with Dmitri Pal and Jenny Galipeau.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When persistent search was in use, the plugin sometimes terminated unexpectedly due to an assertion failure when the "rndc reload" command was issued and the LDAP server was not reachable. With this update, the code has been improved so that connection failures and reconnects are now handled more robustly. As a result, the plugin no longer crashes in the scenario described.

Verified using: 

Test output:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: 767496 assertion failure when using persistent search
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   PASS   ] :: File '/etc/named.conf' should contain 'psearch yes'
version: 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6
CPUs found: 2
worker threads: 2
number of zones: 22
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid  23140) is running...
:: [   PASS   ] :: get named status
:: [   PASS   ] :: make a copy of named.conf
Stopping named: .[  OK  ]
:: [   PASS   ] :: stop named
:: [   PASS   ] :: save iptables
:: [   PASS   ] :: add rule for port 389
:: [   PASS   ] :: add rule for port 636
Starting named: [  OK  ]
:: [   PASS   ] :: start named
:: [   PASS   ] :: set up rndc.conf
:: [   PASS   ] :: add rndc key to named.conf
:: [22:12:33] ::  end1 - 63
:: [22:12:34] ::  end - 62
:: [22:12:34] ::  start - 54
:: [22:12:34] ::  Executing: sed "54,62 s/^#//g" /etc/named.conf
:: [   PASS   ] :: updated named.conf with rndc key
Stopping named: .[  OK  ]
Starting named: [  OK  ]
:: [   PASS   ] :: restart named
WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)
server reload successful
:: [   PASS   ] ::  rndc reload was successful
Stopping named: .[  OK  ]
Starting named: [  OK  ]
:: [   PASS   ] :: restart named
WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)
server reload successful
:: [   PASS   ] ::  rndc reload was successful
Stopping named: .[  OK  ]
:: [   PASS   ] :: stop named
:: [   PASS   ] :: restore iptables
:: [   PASS   ] :: Running 'cp -f /root/named.conf /etc/'
:: [   PASS   ] :: Running 'chgrp named /etc/named.conf'
Stopping named: [  OK  ]
Starting named: [  OK  ]
:: [   PASS   ] :: Running 'service named restart'

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-0359.html