Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

S3 bucket policy is timing out while waiting for "s3-full-access" become "success" #267

Closed
devgnx opened this issue Oct 15, 2019 · 6 comments

Comments

@devgnx
Copy link

devgnx commented Oct 15, 2019

S3 bucket policy is timing out while waiting for s3-full-access become success.
Maybe is related to:
hashicorp/terraform-provider-aws#9414
hashicorp/terraform-provider-aws#9435

Steps to reproduce

ᐅ cd ./examples/gitlab-simple-ha
ᐅ make generate-ssh-key
ᐅ make render-tfvars
ᐅ make network
ᐅ make plan
ᐅ make apply "tf.out"

module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Creating...
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [10s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [20s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [30s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [40s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [50s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [1m0s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [1m10s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [1m20s elapsed]

Error: Error putting S3 policy: timeout while waiting for state to become 'success' (timeout: 1m0s)

  on ../../modules/s3-remote-state/main.tf line 94, in resource "aws_s3_bucket_policy" "s3-full-access":
  94: resource "aws_s3_bucket_policy" "s3-full-access" {


Makefile:65: recipe for target 'apply' failed
make: *** [apply] Error 1

Version

Terraform v0.12.2
Terraform AWS Foundation branch 241-Missing-ASG-IAM-output-variables

@mcgirr
Copy link
Contributor

mcgirr commented Feb 20, 2020

@ketzacoatl is this potentially related to #286?

@mcgirr
Copy link
Contributor

mcgirr commented Feb 21, 2020

I think this will be resolved when #286 is resolved. I've run into something similar recently and setting the principals input on the s3-remote-state module resolved the issue for me.

@mcgirr
Copy link
Contributor

mcgirr commented Mar 7, 2020

@ketzacoatl I think this issue is good to close now that we've addressed #286 with #297

@mcgirr
Copy link
Contributor

mcgirr commented Mar 7, 2020

@devgnx can you please confirm if you're still encountering the same issue when using the module with the changes from #297? If you provide a non-empty list of principals I believe the issue you described will go away.

@mcgirr
Copy link
Contributor

mcgirr commented Apr 12, 2020

Closing this as resolved. Please re-open if needed.

CC @ketzacoatl

@mcgirr mcgirr closed this as completed Apr 12, 2020
@ketzacoatl
Copy link
Contributor

Looks great, thanks Mike!

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

No branches or pull requests

3 participants