minio / mint

Collection of tests to detect overall correctness of MinIO server.
Apache License 2.0
81 stars 50 forks source link

[Test Fail] minio-go tests fail on Minio Server XL mode #241

Closed nitisht closed 6 years ago

nitisht commented 6 years ago

Using latest minio/mint:edge image, and minio server binary built from current master

$ ./minio server /tmp/{1..8}

Initializing data volume.
[01/08] /tmp/1 - 221 GiB online
[02/08] /tmp/2 - 221 GiB online
[03/08] /tmp/3 - 221 GiB online
[04/08] /tmp/4 - 221 GiB online
[05/08] /tmp/5 - 221 GiB online
[06/08] /tmp/6 - 221 GiB online
[07/08] /tmp/7 - 221 GiB online
[08/08] /tmp/8 - 221 GiB online
Endpoint:  http://172.20.10.2:9000  http://172.17.0.1:9000  http://127.0.0.1:9000
AccessKey: minio 
SecretKey: minio123 

Browser Access:
   http://172.20.10.2:9000  http://172.17.0.1:9000  http://127.0.0.1:9000

Command-line Access: https://docs.minio.io/docs/minio-client-quickstart-guide
   $ mc config host add myminio http://172.20.10.2:9000 minio minio123

Object API (Amazon S3 compatible):
   Go:         https://docs.minio.io/docs/golang-client-quickstart-guide
   Java:       https://docs.minio.io/docs/java-client-quickstart-guide
   Python:     https://docs.minio.io/docs/python-client-quickstart-guide
   JavaScript: https://docs.minio.io/docs/javascript-client-quickstart-guide
   .NET:       https://docs.minio.io/docs/dotnet-client-quickstart-guide

Drive Capacity: 721 GiB Free, 885 GiB Total
Status:         8 Online, 0 Offline. We can withstand [4] drive failure(s).

minio-go tests fail. Log:

$ sudo docker run -e "SERVER_ENDPOINT=127.0.0.1:9000" -e "ACCESS_KEY=minio" -e "SECRET_KEY=minio123" -e "ENABLE_HTTPS=0" --net=host minio/mint:edge minio-go
Running with
SERVER_ENDPOINT: 127.0.0.1:9000
ACCESS_KEY:      minio
SECRET_KEY:      ***REDACTED***
ENABLE_HTTPS:    0
SERVER_REGION:   us-east-1
MINT_DATA_DIR:   /mint/data
MINT_MODE:       core

To get logs, run 'sudo docker cp fc9d063f8dc6:/mint/log /tmp/mint-logs'
(1/1) Running minio-go tests ... FAILED in 2 seconds
{
  "args": {
    "bucketName": "minio-go-test-zou9fzqkdyutvss2",
    "ctx": {
      "Context": 0
    },
    "objectName": "j549lhol0g1itymld54kmjdmlrpzg0"
  },
  "duration": 5,
  "function": "GetObjectWithContext(ctx, bucketName, objectName)",
  "message": "GetObjectWithContext should fail on short timeout",
  "name": "minio-go: testGetObjectWithContextV2",
  "status": "FAIL"
}

Executed 0 out of 1 tests successfully.
harshavardhana commented 6 years ago
docker run --net=host -e SERVER_ENDPOINT=127.0.0.1:9001 -e ACCESS_KEY=minio -e SECRET_KEY=minio123 -e ENABLE_HTTPS=0 -e MINT_MODE=full minio/mint:edge minio-go
Running with
SERVER_ENDPOINT: 127.0.0.1:9001
ACCESS_KEY:      minio
SECRET_KEY:      ***REDACTED***
ENABLE_HTTPS:    0
SERVER_REGION:   us-east-1
MINT_DATA_DIR:   /mint/data
MINT_MODE:       full

To get logs, run 'sudo docker cp 87c097adb84e:/mint/log /tmp/mint-logs'
(1/1) Running minio-go tests ... done in 30 seconds

All tests ran successfully

Runs fine on a distributed setup @nitisht

ebozduman commented 6 years ago

@nitisht, Just like @harshavardhana, I also cannot reproduce this issue. Could you try it again in your environment/setup and send me the specific steps, if there is any, to reproduce the issue?

nitisht commented 6 years ago

sure, will do @ebozduman