So this issue seems to have cleared up for us. For others who hit this validate your
replication setup.
We noticed others who had a similar issue had some type of replication issue going on
underneath. We decided to validate all our ipa nodes were replicating properly. We
discovered that we had a replication node that was listed but didn't exist. We
removed it from the list of known servers. We also went through the remaining machines
and reinitialized replication. After doing that things started working normally again.