In production we currently have 3 IPA servers whereas we have only 1 in staging. We should add a second instance in staging to more closely mirror prod.
This would allow for testing updates with no downtime as well as testing replication etc..
Metadata Update from @mobrien: - Issue assigned to mobrien
Metadata Update from @mohanboddu: - Issue tagged with: high-gain, medium-trouble, ops
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review)
There's 2 bugs you might hit, that are related to each other. :)
If the initial playbook run/replication fails, it may print out a error telling you to look at ipa-replica-manage. Please record this error so we can file a bug on it, as ipa-replica-manage is depreciated and shouldn't be used anymore.
The reason for the initial replication crash is some max packet size issue. See: https://access.redhat.com/solutions/374063 The IPA folks wanted us to try and do a tcpdump of this initial packet and see if we could help them see why/what is so large for our install?
ipa02.stg exists now, but it doesn't seem to be in the cluster. You may need to re-add the replication/cluster?
This should all be running now, ipa02 is installed and replicating
Metadata Update from @mobrien: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.