Red Hat Bugzilla – Bug 1353841
ipa-replica-install fails to install when resolv.conf incomplete entries
Last modified: 2017-08-01 05:37:23 EDT
Description of problem: If you have wrong or incomplete entries in /etc/resolv.conf, ipa-replica-install fails with Stack trace. Version-Release number of selected component (if applicable): ipa-server-4.4.0-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Edit resolve.conf to add incorrect entries 2. /usr/sbin/ipa-replica-install -U --setup-ca --setup-dns --forwarder=10.68.5.26 --ip-address=10.65.211.136 -P admin -w Secret123 Actual results: Error with stack trace - IndexError: list index out of range Expected results: ipa-replica-install should suggest user to edit resolv.conf or get DNS ip using someother method or hide stack trace from user
Created attachment 1177549 [details] console.log
Created attachment 1177550 [details] ipa-replica-install.log
Please provide an example of the /etc/hosts file which is causing problems.
I am resolv.conf something like this [ server1 ] # cat /etc/resolv.conf # Generated by NetworkManager search testrelm.test nameserver 10.1.1.5 nameserver 10.1.1.6 nameserver 10.1.1.201 nameserver
Okay, that is certainly invalid file. We can improve this but it is sooo small corner case that I would not give it huge priority for now.
Upstream ticket: https://fedorahosted.org/freeipa/ticket/6070
Just a update : We can fix this issue by porting this change in current IPA code - https://github.com/rthalley/dnspython/blob/master/dns/resolver.py#L652
fixed in upstream python-dns, needs rebase to python-dns 1.15
Verified using IPA version :: # rpm -qa ipa-server python-dns python-dns-1.12.0-4.20150617git465785f.el7.noarch ipa-server-4.5.0-13.el7.x86_64 Steps taken for verification :: 1. Modify /etc/resolv.conf such that it contains incomplete entry 2. Try install IPA server and IPA master. Installation in both cases should succeed. Marking BZ as verified.
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. https://access.redhat.com/errata/RHBA-2017:2304