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

downsample: Downsample requires gcs_bucket even when using S3 #494

Closed
jdfalk opened this issue Aug 28, 2018 · 7 comments
Closed

downsample: Downsample requires gcs_bucket even when using S3 #494

jdfalk opened this issue Aug 28, 2018 · 7 comments

Comments

@jdfalk
Copy link
Contributor

jdfalk commented Aug 28, 2018

Thanos, Prometheus and Golang version used

docker improbable/thanos:v0.1.0-rc.2

What happened
Attempt to run thanos downsample with only s3 and thanos exits saying that the gcs_bucket hasn't been defined.

downsample --data-dir /prometheus --s3.endpoint ourserver:46214 --s3.bucket prometheus --s3.access-key stuff --log.level=debug
Error parsing commandline arguments: required flag --gcs.bucket not provided
usage: thanos downsample --gcs.bucket=<bucket> [<flags>]

What you expected to happen
Thanos downsample to run like compact minus the compact

How to reproduce it (as minimally and precisely as possible):
See command above

Environment:

  • OS (e.g. from /etc/os-release): amazon linux 2
  • Kernel (e.g. uname -a): 4.14.62-70.117.amzn2.x86_64
@jdfalk
Copy link
Contributor Author

jdfalk commented Aug 28, 2018

Happens even on the latest image:
Status: Downloaded newer image for improbable/thanos:master-2018-08-24-d5986d9
Error parsing commandline arguments: required flag --gcs.bucket not provided

@bwplotka bwplotka added the bug label Aug 29, 2018
@bwplotka
Copy link
Member

bwplotka commented Aug 29, 2018

Valid bug

@xphyr
Copy link

xphyr commented Aug 30, 2018

I have submitted #496 for this bug. It should fix this issue, however I do not have any google cloud storage to test against to verify. I also included a very small fix to the contributors guide, as the instructions for setting up the remote were backwards. ("git add remote", vs "git remote add".)

@bwplotka
Copy link
Member

@xphyr waiting for you to rebase and feel free to update contributor guide as well. Thanks!

@xphyr
Copy link

xphyr commented Sep 19, 2018

Oh, sorry. I will rebase and resubmit. Sorry for the delay.

@jojohappy
Copy link
Member

@bwplotka I guess this issue has been fixed with #500, could we close it?

@xjewer
Copy link
Contributor

xjewer commented Oct 17, 2018

should be closed

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

5 participants