search

minio / mint

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

mint fails minio-js for unknown option --exit #245

Closed poornas closed 6 years ago

poornas commented 6 years ago

➜ mint git:(master) ✗ docker run -e SERVER_ENDPOINT=192.168.1.8:9000 -e ACCESS_KEY=minio -e SECRET_KEY=minio123 -e ENABLE_HTTPS=0 minio/mint111 aws-sdk-go aws-sdk-php aws-sdk-ruby awscli mc minio-dotnet minio-java minio-js minio-py Running with SERVER_ENDPOINT: 192.168.1.8: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 73785ac49ab1:/mint/log /tmp/mint-logs' (1/9) Running aws-sdk-go tests ... done in 0 seconds (2/9) Running aws-sdk-php tests ... done in 40 seconds (3/9) Running aws-sdk-ruby tests ... done in 2 seconds (4/9) Running awscli tests ... done in 21 seconds (5/9) Running mc tests ... done in 5 seconds (6/9) Running minio-dotnet tests ... done in 40 seconds (7/9) Running minio-java tests ... done in 5 seconds (8/9) Running minio-js tests ... FAILED in 0 seconds

error: unknown option `--exit'

Executed 7 out of 9 tests successfully.

nitisht commented 6 years ago

@poornas what is the server config being tested here? I mean gateway or FS or XL

kannappanr commented 6 years ago

it must be distributed or xl mode

nitisht commented 6 years ago

Tried with xl setup

nitish@minio:~/go/src/github.com/minio/minio$ ./minio server /tmp/{1..10}

Initializing data volume for the first time.
[01/10] /tmp/1 - 221 GiB online
[02/10] /tmp/10 - 221 GiB online
[03/10] /tmp/2 - 221 GiB online
[04/10] /tmp/3 - 221 GiB online
[05/10] /tmp/4 - 221 GiB online
[06/10] /tmp/5 - 221 GiB online
[07/10] /tmp/6 - 221 GiB online
[08/10] /tmp/7 - 221 GiB online
[09/10] /tmp/8 - 221 GiB online
[10/10] /tmp/9 - 221 GiB online
Drive Capacity: 899 GiB Free, 1.1 TiB Total
Status:         10 Online, 0 Offline. 

Storage Class:
   Objects with Standard class can withstand [5] drive failure(s).
   Objects with Reduced Redundancy class can withstand [2] drive failure(s).

Endpoint:  http://192.168.86.129:9000  http://172.17.0.1:9000  http://172.18.0.1:9000  http://127.0.0.1:9000
AccessKey: minio 
SecretKey: minio123 

Browser Access:
   http://192.168.86.129:9000  http://172.17.0.1:9000  http://172.18.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://192.168.86.129: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

Mint response:

nitish@minio:~/go/src/github.com/minio/minio$ sudo docker run -e "SERVER_ENDPOINT=127.0.0.1:9000" -e "ACCESS_KEY=minio" -e "SECRET_KEY=minio123" -e "ENABLE_HTTPS=0" -e "MINT_MODE=full" --net=host minio/mint:edge minio-java minio-py minio-js minio-dotnet mc s3cmd aws-sdk-go aws-sdk-ruby aws-sdk-php awscli
Unable to find image 'minio/mint:edge' locally
edge: Pulling from minio/mint
50aff78429b1: Pull complete 
f6d82e297bce: Pull complete 
275abb2c8a6f: Pull complete 
9f15a39356d6: Pull complete 
fc0342a94c89: Pull complete 
ecfa5aa00f98: Pull complete 
Digest: sha256:ceafe207c65045a09ac55499acc5efa8e6730ef06c8c1c7b4bcc3c823a7ccbd2
Status: Downloaded newer image for minio/mint:edge
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:       full

To get logs, run 'sudo docker cp 792b5d4889e4:/mint/log /tmp/mint-logs'
(1/10) Running minio-java tests ... done in 53 seconds
(2/10) Running minio-py tests ... done in 11 seconds
(3/10) Running minio-js tests ... done in 21 seconds
(4/10) Running minio-dotnet tests ... done in 45 seconds
(5/10) Running mc tests ... done in 5 seconds
(6/10) Running s3cmd tests ... done in 7 seconds
(7/10) Running aws-sdk-go tests ... done in 0 seconds
(8/10) Running aws-sdk-ruby tests ... done in 1 seconds
(9/10) Running aws-sdk-php tests ... done in 41 seconds
(10/10) Running awscli tests ... done in 23 seconds

All tests ran successfully
harshavardhana commented 6 years ago

This looks like some local build issue with mint @poornas

poornas commented 6 years ago

I built the docker image from dockerfile.dev with latest master - when I run with minio/mint:edge this error doesn't show up.

nitisht commented 6 years ago

@poornas I tried with a locally built mint image, still couldn't reproduce the error

$ sudo docker build . -f Dockerfile.dev -t nitisht/mint:test
$ 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 nitisht/mint:test
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 e973dda9e26f:/mint/log /tmp/mint-logs'
(1/11) Running aws-sdk-go tests ... done in 0 seconds
(2/11) Running aws-sdk-php tests ... done in 41 seconds
(3/11) Running aws-sdk-ruby tests ... done in 1 seconds
(4/11) Running awscli tests ... done in 22 seconds
(5/11) Running mc tests ... done in 5 seconds
(6/11) Running minio-dotnet tests ... done in 45 seconds
(7/11) Running minio-go tests ... done in 21 seconds
(8/11) Running minio-java tests ... done in 6 seconds
(9/11) Running minio-js tests ... done in 21 seconds
(10/11) Running minio-py tests ... done in 9 seconds
(11/11) Running s3cmd tests ... done in 6 seconds

All tests ran successfully
harshavardhana commented 6 years ago

Must be docker layer issues.

poornas commented 6 years ago

Closing this - concur it is docker layer issues because mint/edge works ok