SOLO-2009

ClusterReferenceAlreadyExistsError

Description

Thrown when a cluster reference that is already attached to the deployment is added again; the message names the duplicate reference. solo keeps each cluster reference attached to a deployment at most once, so it rejects a second add rather than creating a conflicting duplicate entry. If you intend to re-add it (for example to change its binding), disconnect it first and then connect it again.

Troubleshooting Steps

1. List current cluster references: solo cluster-ref config list
2. Disconnect it first if you want to re-add it: solo cluster-ref config disconnect