This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 180
Workflow helm install hangs if S3 bucket name has dots (.) in it #700
Comments
greglearns
added a commit
to greglearns/workflow
that referenced
this issue
Jan 14, 2017
…t-storage.md Related to deis#700
greglearns
added a commit
to greglearns/postgres
that referenced
this issue
Jan 14, 2017
RELATED ISSUES deis/workflow#700 deis/workflow#701 (documentation fix) Note: this bug also exists for https://github.com/deis/registry/blob/master/rootfs/bin/create-bucket#L27 REPRODUCING THE BUG Using a period in BUCKET_NAME causes `helm install -f values.yaml deis/workflow --namespace=deis` to fail with this error: ``` ssl.CertificateError: hostname 'deis.subdomain.domain.com-registry.s3-us-west-2.amazonaws.com' doesn't match either of 's3-us-west-2.amazonaws.com', '*.s3-us-west-2.amazonaws.com', 's3.us-west-2.amazonaws.com', '*.s3.us-west-2.amazonaws.com', 's3.dualstack.us-west-2.amazonaws.com', '*.s3.dualstack.us-west-2.amazonaws.com', '*.s3.amazonaws.com' 2017/01/14 07:20:04 Error creating the registry bucket: exit status 1 ``` A POSSIBLE FIX Not sure how to create a test for this (I just started using Deis 4 days ago), but, a hacky test is this: ``` echo "a.bad.thing-mixed-with-a-good-thing" | sed "s/[.]/-/g" # a-bad-thing-mixed-with-a-good-thing ``` THOUGHTS
I think the dot-in-bucket-name issue is something S3 doesn't enjoy in certain accounts. Some work, some don't. I agree and think it's fair to say just use other separators. Thanks! |
Oh, I should clarify: S3 doesn't complain about the dot in the bucket name... instead, the ssl cert creation has a problem. Full stack trace here from doing
|
greglearns
added a commit
to greglearns/postgres
that referenced
this issue
Jan 14, 2017
Using a period in an S3 BUCKET_NAME causes `helm install -f values.yaml deis/workflow --namespace=deis` to fail. REPRODUCING THE BUG Using a period in BUCKET_NAME causes `helm install -f values.yaml deis/workflow --namespace=deis` to fail with this error: ``` ssl.CertificateError: hostname 'deis.subdomain.domain.com-registry.s3-us-west-2.amazonaws.com' doesn't match either of 's3-us-west-2.amazonaws.com', '*.s3-us-west-2.amazonaws.com', 's3.us-west-2.amazonaws.com', '*.s3.us-west-2.amazonaws.com', 's3.dualstack.us-west-2.amazonaws.com', '*.s3.dualstack.us-west-2.amazonaws.com', '*.s3.amazonaws.com' 2017/01/14 07:20:04 Error creating the registry bucket: exit status 1 ``` A POSSIBLE FIX Not sure how to create a test for this (I just started using Deis 4 days ago), but, a hacky test is this: ``` echo "a.bad.thing-mixed-with-a-good-thing" | sed "s/[.]/-/g" ``` RELATED ISSUES deis/workflow#700 deis/workflow#701 (documentation fix) Note: this bug also exists for https://github.com/deis/registry/blob/master/rootfs/bin/create-bucket#L27
greglearns
added a commit
to greglearns/workflow
that referenced
this issue
Jan 14, 2017
Warn users not to use periods in S3 bucket names in installing-workflow/configuring-object-storage.md. Related to issue deis#700
greglearns
added a commit
to greglearns/workflow
that referenced
this issue
Jan 16, 2017
Warn users not to use periods in S3 bucket names in installing-workflow/configuring-object-storage.md. Related to issue deis#700
closed via #701 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
TL;DR: Workflow's helm chart should validate that the S3 database_bucket and registry_bucket do not have periods (.) in them.
THIS BREAKS THINGS
Modifying Deis Workflows basic chart values to include these changes break the deployment, and Workflow will hang on the deploy:
The builder bucket gets created in S3, but not the registry or database buckets.
The database logs include this at the end:
THIS FIXES THINGS
Modifying Deis Workflows basic chart values to include these changes works, and Workflow will deploy:
Versions:
THOUGHTS
One could argue that this is a user-error (I should have known not to use dots, especially since the examples in the
https://github.com/deis/workflow/blob/master/charts/workflow/values.yaml
template clearly show hyphensregistry_bucket: "your-registry-bucket-name"
; however, as a well-intentioned learner of Deis (after taking 3 days of training), I cut and pasted the Kubernetes recommended name for the cluster into the bucket name fields since that seemed to make sense at the time, and I can see how others could make a similar mistake.p.s.: Loving Deis, Workflow, Helm, and Kubernetes. Thank you for all of your hard (and awesome) work Deis and everyone!
The text was updated successfully, but these errors were encountered: