test minio, bad digest after start


> API: PutObject(bucket=s3test-1, object=foo)
Time: 06:39:06 UTC 04/13/2023
DeploymentID: b58da31a-8c5f-401d-8a75-93dbc8f88ecd
RequestID: 17556B3D2FEC59C0
RemoteHost: 127.0.0.1
Host: 127.0.0.1:9000
UserAgent: Boto/2.49.0 Python/3.11.3 Darwin/22.4.0
Error: Bad digest: Expected 37b51d194a7513e45b56f6524f2d51f2 does not match calculated d41d8cd98f00b204e9800998ecf8427e (hash.BadDigest)
8: internal/logger/logger.go:258:logger.LogIf()
7: cmd/erasure-encode.go:93:cmd.(*Erasure).Encode()
6: cmd/erasure-object.go:1190:cmd.erasureObjects.putObject()
5: cmd/erasure-object.go:954:cmd.erasureObjects.PutObject()
4: cmd/erasure-sets.go:767:cmd.(*erasureSets).PutObject()
3: cmd/erasure-server-pool.go:953:cmd.(*erasureServerPools).PutObject()
2: cmd/object-handlers.go:1865:cmd.objectAPIHandlers.PutObjectHandler()
1: net/http/server.go:2122:http.HandlerFunc.ServeHTTP()

Reproduce the PutObject case against MinIO and compare the expected and calculated digests shown in the report. Trace the reported path through cmd/object-handlers.go, cmd/erasure-server-pool.go, cmd/erasure-sets.go, cmd/erasure-object.go, and cmd/erasure-encode.go; the issue names no test file or expected fix, so completion criteria need clarification.

Written by the indexing model from the issue text.