IPA server is upgraded by simply updating rpms, e.g. `yum update ipa-server`.
Upgrader, and especially between major updates, internally does data update, meaning it changes data and possibly schema in LDAP. Given that IPA is multimaster solution, this data is then replicated automatically to other IPA masters and they accept it just fine.
Trouble comes when two or more servers are updated at the same time or right after each other. In that case update might not be replicated to other servers and given that the servers are doing the same or similar changes it then create two conflicting replication events which might end in replication conflicts which in in the end might break IPA server functionality.
Therefore it is required to document that servers needs to be upgraded one at a time with enough time between each update to let replication to finish.
During the upgrade some updates will be done. Ideally we would like to wait all the upgrade updates to be replicated to all servers before attempting to upgrade the next server.
Under normal load, we could expect updates to be replicated in few seconds, let's say within 10sec.
If we want to be sure, we may check the operation in the access logs of the others servers. On the upgraded server, we can monitor access log looking for the last 'csn=xxx' value in the log (note the access log is flushed periodically so one may need to wait a bit to be sure all updates are in the access log).
Then a "grep 'csn=xxx' <non_upgraded_servers>:/var/log/dirsrv/slapd-<instance>/access" will indicate that this last update was replicated.
An other solution would be to monitor RUV, but likely more complex to interpret.
The update is now pending reviews.
The update was acked in peer and developer review.
The update is now available on the Customer Portal.