From 218bd38aceb7513d053607b6fef4340183f36848 Mon Sep 17 00:00:00 2001 From: Charlie Le Date: Tue, 29 Sep 2026 10:51:01 -0700 Subject: [PATCH] Wait for minio to initialize before running integration tests (#7867) MinIO answers /minio/health/live (and /minio/health/ready) with 200 before it can serve S3 requests, so integration tests could hit "Server not initialized yet, please try again" right after the readiness probe passed. Probe /minio/health/cluster, which returns 503 until the object layer, bucket metadata and IAM are initialized. Signed-off-by: Charlie Le (cherry picked from commit 4a9cb51fcd722fa582c4c562f2e29470c3d8b123) Signed-off-by: Charlie Le --- integration/e2e/db/db.go | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/integration/e2e/db/db.go b/integration/e2e/db/db.go index 20cd63baab5..ac04266e1be 100644 --- a/integration/e2e/db/db.go +++ b/integration/e2e/db/db.go @@ -38,7 +38,9 @@ func newMinio(port int, envVars map[string]string, bktNames ...string) *e2e.HTTP images.Minio, // Create the "cortex" bucket before starting minio e2e.NewCommandWithoutEntrypoint("sh", "-c", strings.Join(commands, " && ")), - e2e.NewHTTPReadinessProbe(port, "/minio/health/live", 200, 200), + // /minio/health/live and /minio/health/ready return 200 before minio can + // serve S3 requests; /minio/health/cluster waits for it to initialize. + e2e.NewHTTPReadinessProbe(port, "/minio/health/cluster", 200, 200), port, ) envVars["MINIO_ACCESS_KEY"] = MinioAccessKey