mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2024-12-23 07:33:27 -06:00
6e8d38caa8
ipa-replica-manage force-sync --from <server> is performing a wrong check that may result in the tool looping on "No status yet". force-sync is adding a nsds5replicaupdateschedule attribute to the replication agreement in order to force replication to wake up. Note that this is not a re-initialization (re init drops the current db and reloads the entire db). In a second step, force-sync is checking the replication agreement by reading nsds5BeginReplicaRefresh, nsds5ReplicaLastInitStatus, nsds5ReplicaLastInitStart and nsds5ReplicaLastInitEnd. This is a wrong test as force-sync is not an init operation and does not touch these attributes. The tool should call wait_for_repl_update rather than wait_for_repl_init. This way, the check is done on the replication agreement attributes nsds5replicaUpdateInProgress, nsds5ReplicaLastUpdateStatus, nsds5ReplicaLastUpdateStart and nsds5ReplicaLastUpdateEnd. Fixes: https://pagure.io/freeipa/issue/7886 Reviewed-By: Christian Heimes <cheimes@redhat.com> |
||
|---|---|---|
| .. | ||
| certmonger | ||
| html | ||
| migration | ||
| oddjob | ||
| restart_scripts | ||
| share | ||
| tools | ||
| ui | ||
| updates | ||
| wsgi | ||
| Makefile.am | ||
| README.schema | ||
Ground rules on adding new schema Brand new schema, particularly when written specifically for IPA, should be added in share/*.ldif. Any new files need to be explicitly loaded in ipaserver/install/dsinstance.py. These simply get copied directly into the new instance schema directory. Existing schema (e.g. in an LDAP draft) may either be added as a separate ldif in share or as an update in the updates directory. The advantage of adding the schema as an update is if 389-ds ever adds the schema then the installation won't fail due to existing schema failing to load during bootstrap. If the new schema requires a new container then this should be added to install/bootstrap-template.ldif.