HCP System Management Help


User account collisions

Each user account you create in an HCP system has an internal ID that uniquely identifies it. As a result, two user accounts created on different systems are different from each other, even if they have the same username and are defined for the same HCP tenant.

A user account collision occurs when the replication service tries to replicate a user account from one system to another system that already has a different user account with the same username, where both user accounts are defined for the same tenant.

Here’s a scenario that shows how a user account collision can cause the replication service to pause replication of a tenant. In this scenario:

System A and system B replicate to each other over active/active link AB.

Link AB includes tenant T1, so T1 exists on both systems.

These events occur in the order shown:

1.On system A, you create a user account with username U1 for T1.

2.Before U1 is replicated to system B, you create a user account with username U1 for T1 on system B.

3.The replication service tries to replicate U1 to system B. The replication is unsuccessful because a different user account with username U1 already exists on system B. As a result, the service automatically pauses replication of T1 on link AB.

To recover from a user account collision, you can take either of these actions:

Change the username for the user account on either of the systems involved in the link.

Delete the user account on either of the systems involved in the link.

© 2017 Hitachi Vantara Corporation. All rights reserved.