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

es_repo_mgr creation of s3 repo succeeds AND fails #389

Closed
lbjay opened this issue May 26, 2015 · 2 comments · Fixed by #411
Closed

es_repo_mgr creation of s3 repo succeeds AND fails #389

lbjay opened this issue May 26, 2015 · 2 comments · Fixed by #411

Comments

@lbjay
Copy link

lbjay commented May 26, 2015

Creation of an s3 snapshot repo succeeds (i.e., the repo is created), but the process still fails with exit code 1, complaining 'Missing required parameter --repository'.

Example output:

/ # /usr/bin/es_repo_mgr --host $ELASTICSEARCH_PORT_9200_TCP_ADDR create s3 \
>                      --repository $ES_SNAPSHOT_REPO \
>                      --bucket $ES_SNAPSHOT_BUCKET \
>                      --access_key $AWS_ACCESS_KEY \
>                      --secret_key $AWS_SECRET_KEY
2015-05-26 17:08:41,077 INFO      Checking if repository my_s3_repository already exists...
2015-05-26 17:08:41,080 ERROR     Repository my_s3_repository not found.
2015-05-26 17:08:41,080 INFO      Repository my_s3_repository not in Elasticsearch. Continuing...
2015-05-26 17:08:41,739 INFO      Repository my_s3_repository creation initiated...
Missing required parameter --repository
/ # 

Elasticsearch logs indicate creation of the repo with no associated errors.

@untergeek
Copy link
Member

Thanks for reporting this. Can you run this with the --debug flag and attach the output? I am not able to test s3 repositories very easily.

@untergeek
Copy link
Member

Hi, @lbjay. It's been a bit. Have you been able to run this with the --debug flag and attach the output?

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

Successfully merging a pull request may close this issue.

2 participants