| Previous | Next |
| ERROR_CLUSTER_CANT_CREATE_DUP_CLUSTER_NAME | ERROR_CLUSCFG_ROLLBACK_FAILED |
ERROR_CLUSCFG_ALREADY_COMMITTED
A committed cluster-configuration action is no longer a mutable transaction
ERROR_CLUSCFG_ALREADY_COMMITTED belongs to the ClusCfg configuration workflow used to apply or remove cluster membership state. It means the action object has already completed its commit phase. Calling commit again, attempting to add more changes, or treating the same object as reusable violates its one-shot lifecycle even when the original operation succeeded.
Track configuration actions with an explicit state machine: prepared, committed, rolled back, or failed. After commit, query the resulting node and cluster state using current FailoverClusters tools instead of replaying the object. If an automation process lost the original response, make the operation idempotent by detecting the committed system state; do not assume that repeating the commit is a safe way to discover whether it worked.
State to record around the commit boundary
- Unique configuration operation and target node.
- Last successful prepare, commit, or cleanup phase.
- Whether the node now appears in cluster membership.
- Original RPC result before a higher-level retry policy ran.
References
- Microsoft Open Specifications: ClusCfg protocol
- Microsoft: cluster configuration error definitions
- Microsoft: current cluster creation and membership workflow
Looking for a different code? Search another status or error code.