Directory synchronization fails with "Failed to complete sync. Please check safeguards."
search cancel

Directory synchronization fails with "Failed to complete sync. Please check safeguards."

book

Article ID: 406222

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Directory synchronization in VMware Identity Manager (vIDM) fails across all tenants with the following error message:

  • Failed to complete sync. Please check safeguards.
  • All Directories are configured using the same sync connector.
    • The sync connector may appear degraded with messages similar to:
      Connector Communication failed...

Environment

VMware Identity Manager 3.3.7

Cause

The configured sync connector, Node01, was in a degraded or unhealthy state, preventing changes to the directory such as moving the synchronization connector.

vIDM supports only one active sync connector per directory. If the selected connector is unhealthy, all associated sync operations will fail.

Resolution

Prerequisites

  • You have valid backups or snapshots for the appliances.
  • You have SSH access to the appliances using the root user.

Procedure

Reconfigure each affected directory to use Node02 or Node03 as the sync connector. This action bypasses the unhealthy Node01 connector and restores synchronization capability.

  1. Determine how many tenants are used in the environment by logging into Aria Suite Lifecycle's product UI and navigating to Tenants Management page to see the named tenants.
  2. For each tenant, login to the respective tenant and using the drop-down box in the Directory configuration, change the sync connector from the problematic connector to a working connector.

If vIDM is not in a cluster, and Node01's connector is failed, contact Broadcom support.