Created attachment 987994 [details]
console output and httpd error log
Description of problem:
Saw following error on console while doing "ipa host-del" using "--updatedns" on RHEL-7.1 based machine which was enrolled as replica to RHEL-6.6 based master.
[root@vm-idm-004 ~]# ipa host-del --updatedns testhostBZ910468.testrelm.test
ipa: ERROR: an internal error has occurred
Same command works fine on RHEL-7.1 based IPA Master
[root@master ~]# ipa host-del --updatedns testhostBZ910468.testrelm.test
Deleted host "testhostbz910468.testrelm.test"
Version-Release number of selected component (if applicable):
[root@vm-idm-004 ~]# rpm -q ipa-server
Steps to Reproduce:
1. Install a RHEL-6.6 based IPA master
2. Enroll a RHEL-7.1 based replica from step(1) Master
3. Promote replica of step(2) as Master
4. Add a host using ipa host-add
ipa host-add testhostBZ910468.testrelm.test --ip-address='10.65.206.140'
5. Delete host added in step(5)
ipa host-del --updatedns testhostBZ910468.testrelm.test
"ipa: ERROR: an internal error has occurred" shown on console
host should have been deleted successfully.
(1)Please find the attached snippet from /var/log/httpd/error_log for assertion error seen.
Martin, can you please investigate this one?
if zone in IPA 3.x was created without trailing dot, dnszone commands will fail
This fix should prevent this type of errors.
Martin, Kaleem did not create a zone. His steps indicate he installed 6.6 server, 7.1 replica, and added a host, then deleted this host. So any zones created - are from what ipa-server install added. Why should a host-del error out in this case?
Kaleem, what bind-dyndb-version on 6.6 did you use? Were you using the build from 6.6.z - bind-dyndb-ldap-2.3-6.el6_6 ?
Adding a zone by dnszone-add on RHEL-6.x or using the default zone installed together with IPA server does not matter - both are dotless and both will cause this issue on RHEL-7.1 replicas.
Moving to POST, since we have a patch ready.
Created attachment 1068564 [details]
Verify log for bz
Verified as per c14
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.