mirror of
https://github.com/pgsty/minio.git
synced 2026-08-09 15:53:28 +03:00
test: pin the external fixtures and run the suites against the silo binary
The test and verification scripts invoked ./minio and pulled their tooling from upstream infrastructure with no integrity check. Every `curl | tar` of a client or an old server binary was an unverified execution path in a script that regularly runs as a privileged user, and several fetched a floating "latest". Two installers replace all of it: - install-mcli.sh resolves a pinned pgsty/mc release, downloads the archive and its checksum manifest, requires exactly one valid manifest entry for the asset, verifies it, and installs. MCLI_BIN with a mandatory MCLI_SHA256 lets an offline or air-gapped run supply its own binary, still checksum-checked. - install-verified-fixture.sh takes source, expected SHA-256 and target, and refuses anything that does not match. Sources may be a URL or a local file. Every script that previously downloaded mc now calls install-mcli.sh. The three places that genuinely need an upstream artifact - the old MinIO server binary for the LDAP IAM upgrade-import test, the 2021 mc for the three-site replication test, and the functional-tests.sh fixture - go through install-verified-fixture.sh with the digest recorded inline. Those dl.min.io URLs remain on purpose: they are historical upstream artifacts needed to prove upgrade compatibility, and they are now pinned and verified rather than trusted. The scripts otherwise switch to ./silo, silo.service, the silo container and compose service names, and SILO_CONFIG_DIR. run-multi-site-minio-idp.sh is renamed to run-multi-site-silo-idp.sh with the Makefile target following. buildscripts/minio-upgrade.sh keeps its name and its `minio server` argv - it exists to test the MinIO-to-Silo upgrade, so the old side must stay old - but it is now pinned to an image digest rather than a tag, and its `docker system prune` and `docker volume prune` calls are removed. Those ran unfiltered against the developer's whole Docker installation; the resiliency tests had the same problem and lose their prune and `docker ps -q` sweeps too. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -9,7 +9,7 @@ export CI=1
|
||||
|
||||
make || exit 255
|
||||
|
||||
killall -9 minio || true
|
||||
killall -9 silo || true
|
||||
|
||||
rm -rf /tmp/xl/
|
||||
mkdir -p /tmp/xl/1/ /tmp/xl/2/
|
||||
@@ -26,39 +26,39 @@ for i in $(seq 1 $NODES); do
|
||||
done
|
||||
|
||||
for i in $(seq 1 $NODES); do
|
||||
./minio server --address "127.0.0.1:$((9000 + i))" ${args1[@]} & # | tee /tmp/minio/node.$i &
|
||||
./minio server --address "127.0.0.1:$((9100 + i))" ${args2[@]} & # | tee /tmp/minio/node.$i &
|
||||
./silo server --address "127.0.0.1:$((9000 + i))" ${args1[@]} & # | tee /tmp/minio/node.$i &
|
||||
./silo server --address "127.0.0.1:$((9100 + i))" ${args2[@]} & # | tee /tmp/minio/node.$i &
|
||||
done
|
||||
|
||||
sleep 10
|
||||
|
||||
./mc alias set myminio1 http://localhost:9001 minioadmin minioadmin
|
||||
./mc alias set myminio2 http://localhost:9101 minioadmin minioadmin
|
||||
./mc alias set mysilo1 http://localhost:9001 minioadmin minioadmin
|
||||
./mc alias set mysilo2 http://localhost:9101 minioadmin minioadmin
|
||||
|
||||
./mc ready myminio1
|
||||
./mc ready myminio2
|
||||
./mc ready mysilo1
|
||||
./mc ready mysilo2
|
||||
sleep 1
|
||||
|
||||
./mc mb myminio1/testbucket/ --with-lock
|
||||
./mc mb myminio2/testbucket/ --with-lock
|
||||
./mc mb mysilo1/testbucket/ --with-lock
|
||||
./mc mb mysilo2/testbucket/ --with-lock
|
||||
|
||||
./mc encrypt set sse-s3 my-minio-key myminio1/testbucket/
|
||||
./mc encrypt set sse-s3 my-minio-key myminio2/testbucket/
|
||||
./mc encrypt set sse-s3 my-minio-key mysilo1/testbucket/
|
||||
./mc encrypt set sse-s3 my-minio-key mysilo2/testbucket/
|
||||
|
||||
./mc replicate add myminio1/testbucket --remote-bucket http://minioadmin:minioadmin@localhost:9101/testbucket --priority 1
|
||||
./mc replicate add myminio2/testbucket --remote-bucket http://minioadmin:minioadmin@localhost:9001/testbucket --priority 1
|
||||
./mc replicate add mysilo1/testbucket --remote-bucket http://minioadmin:minioadmin@localhost:9101/testbucket --priority 1
|
||||
./mc replicate add mysilo2/testbucket --remote-bucket http://minioadmin:minioadmin@localhost:9001/testbucket --priority 1
|
||||
|
||||
sleep 1
|
||||
|
||||
cp README.md internal.tar
|
||||
|
||||
./mc cp internal.tar myminio1/testbucket/dir/1.tar
|
||||
./mc cp internal.tar myminio2/testbucket/dir/2.tar
|
||||
./mc cp internal.tar mysilo1/testbucket/dir/1.tar
|
||||
./mc cp internal.tar mysilo2/testbucket/dir/2.tar
|
||||
|
||||
sleep 1
|
||||
|
||||
./mc ls -r --versions myminio1/testbucket/dir/ >/tmp/dir_1.txt
|
||||
./mc ls -r --versions myminio2/testbucket/dir/ >/tmp/dir_2.txt
|
||||
./mc ls -r --versions mysilo1/testbucket/dir/ >/tmp/dir_1.txt
|
||||
./mc ls -r --versions mysilo2/testbucket/dir/ >/tmp/dir_2.txt
|
||||
|
||||
out=$(diff -qpruN /tmp/dir_1.txt /tmp/dir_2.txt)
|
||||
ret=$?
|
||||
|
||||
Reference in New Issue
Block a user