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

acctest: TestAccS3Bucket_Tags_ignoreTags has an intermittent failure #22953

Closed
gdavison opened this issue Feb 4, 2022 · 2 comments
Closed

acctest: TestAccS3Bucket_Tags_ignoreTags has an intermittent failure #22953

gdavison opened this issue Feb 4, 2022 · 2 comments
Labels
service/s3 Issues and PRs that pertain to the s3 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@gdavison
Copy link
Contributor

gdavison commented Feb 4, 2022

The acceptance test TestAccS3Bucket_Tags_ignoreTags has an intermittent failure. Errors are either

After applying this test step and performing a `terraform refresh`, the plan was not empty.
stdout
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# aws_s3_bucket.bucket will be updated in-place
~ resource "aws_s3_bucket" "bucket" {
id                          = "tf-acc-test-2558770563211572070"
~ tags                        = {
- "ignorekey1" = "ignorevalue1" -> null
}
~ tags_all                    = {
- "ignorekey1" = "ignorevalue1"
} -> (known after apply)
# (11 unchanged attributes hidden)
# (1 unchanged block hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.

or

Step 2/2 error: Check failed: Check 2/6 error: aws_s3_bucket.bucket: Attribute 'tags.%' expected "3", got "4"
@github-actions github-actions bot added the service/s3 Issues and PRs that pertain to the s3 service. label Feb 4, 2022
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Jan 26, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 25, 2024
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/s3 Issues and PRs that pertain to the s3 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

1 participant