Red Hat Bugzilla – Bug 833514
Check direct and reverse address on ipa-replica-install
Last modified: 2014-06-17 20:02:34 EDT
This bug is created as a clone of upstream ticket:
If A and PTR record for a replica are wrong as soon as we switch to GSSAPI agreements then replication will stop working.
We should probably check that both replica resolve properly both direct and reverse and fail install with a clear message if they are not.
We should probably work ok if /etc/hosts is fine (as that what libgssapi would end up looking into), but we should probably still do lookup in DNS (if the master/replica has DNS installed) just to make sure clients will be able to work as well.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
This does a DNS/hosts file look up on the replica, it is double-checked via the conncheck we do, and finally if IPA is managing DNS we double-check that the host is there as well and prompt if not.
Verified against ipa-server-3.3.3-13.el7.x86_64
Verified that replica install outputs clear error messages when the A and PTR records differ on a SLAVE.
Running 'ipa-replica-prepare -p Secret123 --ip-address=10.8.60.64 zippyvm5.idm.lab.eng.rdu2.redhat.com &> cat /opt/rhqa_ipa/ipa-replica-prepare-output-6.txt' (Expected 0, got 2)
Add the --ip-address argument to create a DNS entry.
The host name zippyvm5.idm.lab.eng.rdu2.redhat.com does not match the reverse lookup zippyvm5.testrelm.com
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.