6856b17 ipa-replica-manage: fix force-sync

1 file Authored by frenaud 5 years ago, Committed by cheimes 5 years ago,
    ipa-replica-manage: fix force-sync
    
    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>