Replica Node addition passed with newer build , but data node addition fails with Error 412 in VCF Operations .

Products

• VCF Operations

Issue/Introduction

The scale-out task fails during the data node addition stage, unless it was successful when replica was added with new version.

The following symptoms are observed:

• The scale-out task fails during the data node addition stage.
• The SDDC Manager logs (operationsmanager.log) display error: 412 Precondition Failed.
• A build version mismatch exists between the Master node and the new Replica node.

Environment

VCF Operations 9.1

Cause

This issue is caused by a product gap where the VersionValidator logic is inconsistently applied. While the Data node addition path (POST /casa/cluster/add/nodes) correctly verifies version compatibility, the Replica node path (POST /casa/node/replica) does not. This allows a newer build version to join as a Replica without a version check, which later blocks additional Data nodes from joining because they are checked against the original older Master node build.

Resolution

This is targeted to be fixed in a future release. For updates on the fix status, Subscribe to this article.

Recommended Approach:

1. When scaling out a Simple Deployment, first verify that there are no pending Express Patches available.
2. If Express Patches are available, apply them to the existing node(s) before initiating the scale-out operation.
   • Note: If the Replica node has already been added and is running a different build version, use one of the following approaches.

Workaround:

To resolve the version mismatch and successfully complete the scale-out operation:

1. Force update the original Master node so that it matches the build version of the newly added Replica node.
2. Once both nodes are on the same build version, proceed with the Data Node scale-out operation.

Alternative Approach:

If upgrading the original Master node is not feasible and the Data Node scale-out needs to be unblocked:

1. Perform a manual failover of the VCF Operations cluster so that the Replica node running the newer build version becomes the Master.
2. Retry the Data Node scale-out operation.