Version: 25.8.15.10001

Description

The failure occurs in the scenario /zero copy replication/add remove one replica, where the test validates that no data is lost after removing and re-adding a replica during inserts.

At the end of the scenario, at least one node reports a row count mismatch (expected 2,000,000, actual 1,000,000), causing an AssertionError in assert_row_count().

As a result, multiple related S3 MinIO zero-copy replication tests fail, and the /s3/minio and /s3 suites fail in the regression run.

Failing tests

✘ [ Fail ] '/s3/minio/part 2/zero copy replication/add remove one replica' (2m 42s)
✘ [ Fail ] '/s3/minio/part 2/zero copy replication/add remove replica parallel' (2m 37s)
✘ [ Fail ] '/s3/minio/part 2/zero copy replication/bad detached part' (1m 18s)

Issue Created in Altinity/Clickhouse

Altinity/ClickHouse#1338

CI Run

https://github.com/Altinity/ClickHouse/actions/runs/21256316599/job/61175407521

Artifacts and Reports

https://altinity-build-artifacts.s3.amazonaws.com/index.html#REFs/1331/merge/80a50080a2dddad4ef2fc02d90e0ef1d2d5182d5/regression/x86_64/with_analyzer/zookeeper/without_thread_fuzzer/s32/minio/