#3194 Cannot install an ipa replica from existing ipa replica not running DNS
Closed: Fixed None Opened 11 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=867682 (Fedora)

Description of problem:
I was not able to install a new replica from an existing replica that was not
running DNS

Version-Release number of selected component (if applicable):
freeipa-admintools-3.0.0-2.fc18.x86_64
freeipa-server-selinux-3.0.0-2.fc18.x86_64
freeipa-python-3.0.0-2.fc18.x86_64
freeipa-client-3.0.0-2.fc18.x86_64
freeipa-server-3.0.0-2.fc18.x86_64

How reproducible:
Seems always, though I have only tried in one setup, I could not get around the
problem.

Steps to Reproduce:
1. Create an IPA Server (first replica) with --setup-dns
2. Run ipa-replica-prepare and set up another replica (second replica)
3. On the second replica run ipa-replica-prepare for yet another replica and
try to set another replica (third replica)

Actual results:
Installation on the third replica complains that the hostname of the second
replica is unresolvable.

Expected results:
Installation should complete.

Additional info:
I was trying to follow along with
https://fedoraproject.org/wiki/QA:Testcase_freeipav3_replication

There is nothing to indicate that the second replica must have DNS running, but
once it was the third replica installed without issue.

In my test I set up s01.ipa.montleon.intra with the --setup-dns option. Once
done I proceeded to run ipa-replica-prepare --ip-address=172.16.1.3
s02.ipa.montleon.intra

and then on s02.ipa.montleon.intra
ipa-replica-install /root/replica-info-s02.ipa.montleon.intra.gpg and
ipa-ca-install /root/replica-info-s02.ipa.montleon.intra.gpg
ipa-replica-prepare --ip-address=172.16.1.4 s03.ipa.montleon.intra

on s03.ipa.montleon.intra I continually tried to run:
ipa-replica-install /root/replica-info-s03.ipa.montleon.intra.gpg, which
continually failed with the message:
Connection check OK
ipa         : ERROR    Could not resolve hostname s02.ipa.montleon.intra using
DNS. Clients may not function properly. Please check your DNS setup. (Note that
this check queries IPA DNS directly and ignores /etc/hosts.)
Continue? [no]:

Until I went back to s02.ipa.montleon.intra and ran:
ipa-dns-install /root/replica-info-s02.ipa.montleon.intra.gpg

I verified prior to setting up DNS on s02 that the following worked:
[root@s02 ~]# ipa dns-resolve s02.ipa.montleon.intra
-------------------------------
Found 's02.ipa.montleon.intra.'
-------------------------------
as did host, dig, etc.

I also verified that name resolution was working on s03, and rebooted for the
heck of it to make sure no odd caching problems were occurring, even though I
did not have nscd installed.

cat /etc/resolv.conf
domain ipa.montleon.intra
search ipa.montleon.intra
nameserver 172.16.1.2

[root@s03 ~]# dig s02.ipa.montleon.intra

; <<>> DiG 9.9.2-RedHat-9.9.2-2.fc18 <<>> s02.ipa.montleon.intra
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26495
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;s02.ipa.montleon.intra.                IN      A

;; ANSWER SECTION:
s02.ipa.montleon.intra. 1200    IN      A       172.16.1.3

;; AUTHORITY SECTION:
ipa.montleon.intra.     86400   IN      NS      s01.ipa.montleon.intra.

;; ADDITIONAL SECTION:
s01.ipa.montleon.intra. 1200    IN      A       172.16.1.2

;; Query time: 1 msec
;; SERVER: 172.16.1.2#53(172.16.1.2)
;; WHEN: Thu Oct 18 00:07:18 2012
;; MSG SIZE  rcvd: 101

Metadata Update from @mkosek:
- Issue assigned to pviktori
- Issue set to the milestone: FreeIPA 3.0.1 (bug fixing)

7 years ago

Login to comment on this ticket.

Metadata