From fceeee0519aa73d6d8af5b3493befbb911d0c818 Mon Sep 17 00:00:00 2001 From: Charlie Le Date: Mon, 28 Sep 2026 15:54:09 -0700 Subject: [PATCH] Wait for minio to initialize before running integration tests The e2e readiness probe for minio polled /minio/health/live, which minio answers with 200 as soon as its HTTP server is up, before the object layer, bucket metadata and IAM are initialized. /minio/health/ready does the same. A test that talks to S3 right after the probe passes can get "Server not initialized yet, please try again", as TestLoadRuntimeConfigFromCloudStorage did on the amd64 requires_docker job for #7863. Probe /minio/health/cluster instead, which returns 503 until all three are initialized. 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