mirror of https://github.com/rustfs/rustfs.git synced 2026-08-17 10:17:55 +00:00

Files

T

overtrue 2aa4e411e5 test(interop): fix the fixture lab's all-cases and SSE-C capture paths

Two defects kept most of the fixture matrix uncapturable, both found by actually running the lab rather than reading it.

`./capture_via_docker.sh all` never worked. With no case ids to forward, `case_args` is an empty array, and `${arr[@]}` under `set -u` aborts on bash 3.2 — still the default /bin/bash on macOS — with "case_args[@]: unbound variable". The build_args array this branch added has the same shape and would have hit it on the CI path, where no mirror overrides are set. Both now use ${arr[@]+"${arr[@]}"}, which is empty-safe on 3.2.

The SSE-C cases could not be captured at all: MinIO refuses SSE-C over a plain-HTTP connection, and the script pinned the lab to its default http endpoint with no way to override. lab.py already provisions a self-signed certificate and speaks https end to end, so this only needed an endpoint passthrough — MINIO_LAB_ENDPOINT, documented alongside the requirement.

With both fixed, one command captures the full six-case matrix (SSE-S3 / SSE-KMS / SSE-C x singlepart / multipart), which is what backlog#1638's D4 matrix has to be measured against.

Refs rustfs/backlog#1638.

2026-08-16 22:25:27 +08:00

fixtures

feat(rio): rio_v2 is compatible with minio for storing data. (#3115 )

2026-06-08 11:59:14 +00:00

minio_fixture_lab

test(interop): fix the fixture lab's all-cases and SSE-C capture paths

2026-08-16 22:25:27 +08:00

minio_generated_fixtures.rs

fix(rebalance): converge multipart data movement retries (#6057 )

2026-08-13 06:12:26 +00:00

README.md

chore(build): pin Rust toolchain configs to 1.97.1 (#5350 )

2026-07-28 03:53:32 +00:00

README.md

rio-v2 Fixture Tests

This directory holds interoperability tests for rustfs-rio-v2.

Generated MinIO fixtures

The integration test minio_generated_fixtures.rs reads raw MinIO backend data generated by crates/rio-v2/tests/minio_fixture_lab/lab.py.

Default fixture root:

crates/rio-v2/tests/fixtures/minio-generated

The generated MinIO fixture data is intentionally not checked in and these tests are ignored by default, so they are not part of automated CI runs.

To generate or expand fixtures locally, use:

uv run python .\minio_fixture_lab\lab.py capture-matrix `
  --root .\rustfs\crates\rio-v2\tests\fixtures\minio-generated `
  --minio-binary .\rustfs\tmp\minio.darwin-arm64.RELEASE.2025-09-07T16-13-09Z `
  --endpoint https://127.0.0.1:19000 `
  --disk-count 1

Or point the tests at another generated root:

$env:RUSTFS_MINIO_FIXTURE_ROOT = '.\rustfs\tmp\minio-fixture-lab-smoke'
cargo +1.97.1 test -p rustfs-rio-v2 --test minio_generated_fixtures -- --ignored

Scope

The current fixture test covers the full default capture matrix:

sse-s3-singlepart-64k
sse-s3-multipart-8m
sse-kms-singlepart-64k
sse-kms-multipart-8m
sse-c-singlepart-64k
sse-c-multipart-8m

It checks that:

raw xl.meta can be parsed through rustfs-filemeta
singlepart and multipart fixture structures are recognized
SSE-S3, SSE-KMS, and SSE-C metadata markers survive capture
KMS key ids are derived from each fixture's own manifest.json, so local static-KMS runs are not tied to one hard-coded key name
SSE-C HEAD responses round-trip the expected customer algorithm and customer-key MD5

These tests do not yet validate full plaintext reconstruction from MinIO-written encrypted data.