## What changed
- Replace Pod deletion with Chaos Mesh `container-kill` in CDC
force-promote and source-down failover tests.
- Kill every regular container in matching Pods while preserving the Pod
objects.
- Verify that Pod UIDs remain unchanged and each container's restart
count increases.
- Clean up the generated `PodChaos` resources after fault injection.
## Why
Deleting Pods changes their identity and tests Pod recreation rather
than container-level recovery. These scenarios need to verify CDC
failover behavior when containers restart inside the existing Pods.
## Impact
CDC failover tests now exercise container failures while explicitly
validating that Kubernetes does not recreate the affected Pods.
## Validation
- `ruff check` passed for all modified files.
- `ruff format --check` passed for all modified files.
- Python compilation passed for all modified files.
- Full CDC E2E was not run locally because it requires a Kubernetes
environment with Chaos Mesh.
---------
Signed-off-by: zhuwenxing <wenxing.zhu@zilliz.com>
## What type of PR is this?
/kind test
## What this PR does / why we need it:
Adds RESTful import 2PC coverage for Milvus import lifecycle and
CDC-focused scenarios.
This PR adds:
- REST import job helpers for `/describe`, `/commit`, `/abort`, and
state polling
- pytest options for secondary CDC endpoint/object storage/topology
parameters
- a new REST test suite for import 2PC lifecycle, visibility,
commit/abort, delete semantics, TTL, compaction, formats, data types,
indexes, partitions, DML interleaving, CDC, and fault-tolerance gates
- xfail regression coverage for known issues:
- #50458 REST import commit/abort authorization gap
- #50459 NaN/Inf FloatVector import/query behavior
- #50460 REST `options.auto_commit=null` validation gap
## Which issue(s) this PR fixes:
N/A
## Special notes for your reviewer:
The CDC cases require passing secondary cluster REST/MinIO options and
topology arguments. Without those options, CDC-specific cases skip with
an explicit environment precondition message.
The manual compaction-after-commit case is marked non-strict xfail
because compaction may remain `Executing` on current import 2PC test
builds.
## Test result:
```text
python -m py_compile tests/restful_client_v2/conftest.py tests/restful_client_v2/api/milvus.py tests/restful_client_v2/testcases/test_import_2pc_operation.py
ruff check tests/restful_client_v2/api/milvus.py tests/restful_client_v2/conftest.py tests/restful_client_v2/testcases/test_import_2pc_operation.py
python -m pytest --collect-only -q testcases/test_import_2pc_operation.py
141 tests collected in 2.14s
```
---------
Signed-off-by: zhuwenxing <wenxing.zhu@zilliz.com>
## Summary
issue: #50320
Clean downstream-only collections created during CDC force-promote
verification before restoring the topology back to `upstream ->
downstream`.
The affected tests create `*_after` collections while downstream is
force-promoted primary. If teardown restores `A -> B` first, downstream
becomes a replica again and `drop_collection` is rejected, leaving
`test_fp_*_after` collections that fail the final upstream/downstream
diff.
## Changes
- Add targeted cleanup for downstream-only force-promote verification
collections.
- Remove those collections from the generic cleanup list after the
targeted cleanup attempt.
- Add a focused unit test for the cleanup helper behavior.
## Test Plan
- [x] `PYTHONPATH=tests/python_client conda run -n milvus2 python -m
pytest -c /tmp/empty-pytest.ini
--confcutdir=tests/python_client/cdc/testcases
tests/python_client/cdc/testcases/test_force_promote_cleanup.py -q`
- [x] `conda run -n milvus2 python -m py_compile
tests/python_client/cdc/testcases/test_force_promote.py
tests/python_client/cdc/testcases/test_force_promote_cleanup.py`
- [x] `git diff --check`
- [ ] `make static-check` could not complete locally because the CGo
core artifacts in this workspace do not match the latest master headers.
It first failed without `milvus_core.pc`; with
`PKG_CONFIG_PATH=/Users/yihao.dai/workspace/milvus/internal/core/output/lib/pkgconfig`,
it failed at `internal/util/initcore` with missing
`C.CArrowReaderConfig` / `C.InitArrowReaderConfig`.
Signed-off-by: Yihao Dai <yihao.dai@zilliz.com>
## Summary
- add `kubectl_helper` fixture in `tests/python_client/cdc/conftest.py`
for pod delete / readiness wait during failover tests
- add `tests/python_client/cdc/testcases/test_force_promote.py` with
force-promote failover scenarios:
- basic promote after source kill
- target restart during promote
- source restart during promote
- incomplete DDL during promote
- network partition then promote
- endurance loop test behind `RUN_ENDURANCE`
- include teardown restore and cleanup logic to return topology to a
known state after each case
## Test plan
- [x] `ruff` formatting/lint fixes included in commits
- [ ] `make static-check` (skipped per request)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Signed-off-by: Yihao Dai <yihao.dai@zilliz.com>
