Closed Aethylred closed 8 months ago
The inventory file above is not providing any information about ipa_replica
group. Are the ipareplica_setup_X
variables really set while promoting the client?
Added the inventory, I've cleaned out some stuff about configuring the network interfaces & mounting LVMs. Note that we're connecting via an IP address as we're installing the DNS these hosts are expecting to use. The hosts do have entries in /etc/hosts
so they can resolve their names to do the setup.
Are the ipareplica_setup_X variables really set while promoting the client?
I don't know that, it's why I'm here.
Since I'm a RedHat customer, I've created a support ticket as well.
Found it, there was a typo that I FIXED when creating the fake inventory.
In my actual code I'd used ipa_replica
and ipa_replicas
as a group inconsistently.
I've successfully deployed an IPA server, and an replica of that server.
However the deployed replica is not assigned any Server Roles and does not provide AD trust agent, AD trust controller, CA server, DNS server, or KRA server roles
i.e. It's not been promoted to those roles. This is the expected outcome when deploying a replica using
ipa-replica-install
I do not see a
ipaserver_promote
oripareplica_promote
module or a way of setting IPA server roles.I'm not sure if this is the correct method of making a full peer replica cluster where the replica is the failover of the first server.
Cleaned up inventory is:
The (cleaned up) variables are:
The playbook is: