That may be an issue after they're added to DNS. The current error is that
the primary can't resolve the hostnames for the replicas. I have checked
the primary and they are added as hosts, not added to the proper group
(although that may happen later in the process) and not added to DNS. I'll
try adding the primary as the only resolver and see what happens though.
On Wed, Dec 2, 2020, 11:14 AM <rainer(a)ultra-secure.de> wrote:
Am 2020-12-02 17:59, schrieb Mark Potter via FreeIPA-users:
> I am attempting to deploy a cluster using ansible-freeipa:
> CentOS 8.2
> Ansible 2.10.2
> The ipaserver role successfully deploys the server but I have a
> question about dns specifically: What is the format for
> "ipaserver_reverse_zones". I haven't seen an example. We have a LOT
> reverse zones and would like to get them all set out out the gate
> using vars.
> Server is mostly alright and I think I have it figured out but
> replicas fail to deploy.
> They specifically fail at Install - Replica preparation connection
> check, if I set it to ignore the connection check they simply fail
> later for the same reason. I have managed to suss out that the
> replicas aren't added to DNS on the primary server however I cannot
> seem to get them to add during deployment. They show up in Hosts on
> the primary but not in DNS. I could add them manually but I will be
> handing this over for multiple regions to use to deploy FreeIPA so
> everything needs to work from the ansible-freeipa collection and
I found I have to specify the master server as resolver in resolv.conf
(of the replicas) so they can find the srv records.
There was an error-message somewhere that hinted at this.