mirror of
https://github.com/pgsty/minio.git
synced 2026-08-09 07:43:29 +03:00
Feng Ruohang
6613c2a3cb
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>
50 lines
1.5 KiB
Bash
Executable File
50 lines
1.5 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
echo "script failed" >resiliency-verify.log # assume initial state
|
|
|
|
ALIAS_NAME=mysilo
|
|
BUCKET="test-bucket"
|
|
SRC_DIR="/tmp/data"
|
|
DEST_DIR="/tmp/dest"
|
|
|
|
./mc admin config set "$ALIAS_NAME" api requests_max=400
|
|
|
|
OBJ_COUNT_AFTER_STOP=$(./mc ls "${ALIAS_NAME}"/"${BUCKET}"/initial-data/ | wc -l)
|
|
# Count should match the initial count of 10
|
|
if [ "${OBJ_COUNT_AFTER_STOP}" -ne 10 ]; then
|
|
echo "Expected 10 objects; received ${OBJ_COUNT_AFTER_STOP}"
|
|
exit 1
|
|
fi
|
|
|
|
./mc ready "${ALIAS_NAME}" --json
|
|
|
|
OUT=$(./mc cp --quiet "${SRC_DIR}"/* "${ALIAS_NAME}"/"${BUCKET}"/new-data/)
|
|
RET=${?}
|
|
if [ ${RET} -ne 0 ]; then
|
|
echo "Error copying objects to new prefix: ${OUT}"
|
|
exit 1
|
|
fi
|
|
|
|
OBJ_COUNT_AFTER_COPY=$(./mc ls "${ALIAS_NAME}"/"${BUCKET}"/new-data/ | wc -l)
|
|
if [ "${OBJ_COUNT_AFTER_COPY}" -ne "${OBJ_COUNT_AFTER_STOP}" ]; then
|
|
echo "Expected ${OBJ_COUNT_AFTER_STOP} objects; received ${OBJ_COUNT_AFTER_COPY}"
|
|
exit 1
|
|
fi
|
|
|
|
OUT=$(./mc cp --quiet --recursive "${ALIAS_NAME}"/"${BUCKET}"/new-data/ "${DEST_DIR}"/)
|
|
RET=${?}
|
|
if [ ${RET} -ne 0 ]; then
|
|
echo "Get objects failed: ${OUT}"
|
|
exit 1
|
|
fi
|
|
|
|
# Check if check sums match for source and destination directories
|
|
CHECK_SUM_SRC=$(sha384sum <(sha384sum "${SRC_DIR}"/* | cut -d " " -f 1 | sort) | cut -d " " -f 1)
|
|
CHECK_SUM_DEST=$(sha384sum <(sha384sum "${DEST_DIR}"/* | cut -d " " -f 1 | sort) | cut -d " " -f 1)
|
|
if [ "${CHECK_SUM_SRC}" != "${CHECK_SUM_DEST}" ]; then
|
|
echo "Checksum verification of source files and destination files failed"
|
|
exit 1
|
|
fi
|
|
|
|
echo "script passed" >resiliency-verify.log
|