Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Test Fail] awscli tests fail on Minio Server XL mode #240

Closed
nitisht opened this issue Dec 15, 2017 · 3 comments
Closed

[Test Fail] awscli tests fail on Minio Server XL mode #240

nitisht opened this issue Dec 15, 2017 · 3 comments
Assignees
Milestone

Comments

@nitisht
Copy link
Contributor

nitisht commented Dec 15, 2017

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).

awscli Mint tests fail. Logs:

$ 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 awscli
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 64a9a3bc0395:/mint/log /tmp/mint-logs'
(1/1) Running awscli tests ... FAILED in 6 seconds
{
  "name": "awscli",
  "duration": 2232,
  "function": "aws --endpoint-url http://127.0.0.1:9000 s3api head-object --bucket awscli-mint-test-bucket-14439 --key prefix/directory/\n",
  "status": "FAIL",
  "error": "An error occurred (404) when calling the HeadObject operation: Not Found"
}

Executed 0 out of 1 tests successfully.
@poornas
Copy link
Contributor

poornas commented Dec 15, 2017

@nitisht, creating empty directories is supported only in FS mode as per this PR. So this test will fail in XL mode.

@harshavardhana
Copy link
Member

@nitisht, creating empty directories is supported only in FS mode as per this PR. So this test will fail in XL mode.

@poornas is correct we do not have a way to selectively turn on off certain tests for specific backend only environments, for now i don't think we can fix this for erasure coded backend.

@nitisht
Copy link
Contributor Author

nitisht commented Dec 16, 2017

for now i don't think we can fix this for erasure coded backend.

Shall we remove this test then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants