Created attachment 1079191 [details]
crash detailed info
Description of problem:
Observed this crash while executing B&R automated regression run.
Crash shows time that it occured at 08:45:45 AM but when i looked into the beaker logs, i found that at that time ipa installation was in progress. Point to note is that it was in second test case. In First test case, i did install/full backup/uninstall/install/full restore/uninstall.
snip from crash:
time: Thu 01 Oct 2015 08:54:45 AM EDT
cmdline: /usr/bin/python2 /usr/libexec/ipa/ipa-dnskeysync-replica
uid: 993 (ods)
runlevel: N 3
beaker log snip with timestamp:
:: [ 08:49:57 ] :: ipa-server-4.2.0-12.el7.x86_64
:: [ BEGIN ] :: Running ' /usr/sbin/ipa-server-install --setup-dns --forwarder=10.16.36.29 --hostname=ibm-dx360m4-01.testrelm.test -r TESTRELM.TEST -n testrelm.test -p xxxxxxxx -a xxxxxxxx --ip-address=10.16.67.102 -U'
Be sure to back up the CA certificates stored in /root/cacert.p12
These files are required to create replicas. The password for these
files is the Directory Manager password
:: [ PASS ] :: Command ' /usr/sbin/ipa-server-install --setup-dns --forwarder=10.16.36.29 --hostname=ibm-dx360m4-01.testrelm.test -r TESTRELM.TEST -n testrelm.test -p xxxxxxxx -a xxxxxxxx --ip-address=10.16.67.102 -U' (Expected 0, got 0)
:: [ 08:56:29 ] :: Check ldap_sasl_authid is not added to sssd.conf
:: [ 08:56:30 ] :: Verifying BZ 878420
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.See description section
Please find the attached crash detailed info
Kaleem, could you attach a DS error and access log from the time of the crash?
This is most likely caused by weirness in IPA ldap2 class - DS did not respond in 2 second limit for configuration refresh and that caused this error.
This issue will manifest itself randomly. To workaround that we can easily change DNSSEC daemons to use different code from IPA framework to avoid the problematic query from withing ldap2 class.
Patch was sent to the ipa-devel list.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
Verified using IPA version::
Done SanityOnly using automation.
Crash no more seen with automated test suite.
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.