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

Regression: massive slowdown on planning since 2.39 #11203

Closed
lifeofguenter opened this issue Dec 9, 2019 · 2 comments
Closed

Regression: massive slowdown on planning since 2.39 #11203

lifeofguenter opened this issue Dec 9, 2019 · 2 comments
Labels
stale Old or inactive issues managed by automation, if no further action taken these will get closed. waiting-response Maintainers are waiting on response from community or contributor.

Comments

@lifeofguenter
Copy link

lifeofguenter commented Dec 9, 2019

Since 2.39 we are hitting massive slowdown issues on every plan causing them to run for 5min vs. 22 seconds before.

Downgrading to 2.38 immediately solves the issue - without any other changes.

Adds 2 minutes:

[2019-12-09T11:23:04.383Z] 2019-12-09T11:23:04.186Z [DEBUG] plugin.terraform-provider-aws_v2.40.0_x4: 2019/12/09 11:23:04 [INFO] No assume_role block read from configuration
[2019-12-09T11:23:04.404Z] 2019-12-09T11:23:04.186Z [DEBUG] plugin.terraform-provider-aws_v2.40.0_x4: 2019/12/09 11:23:04 [INFO] Building AWS auth structure
[2019-12-09T11:23:04.404Z] 2019-12-09T11:23:04.186Z [DEBUG] plugin.terraform-provider-aws_v2.40.0_x4: 2019/12/09 11:23:04 [INFO] Setting AWS metadata API timeout to 100ms
[2019-12-09T11:23:04.404Z] 2019-12-09T11:23:04.186Z [DEBUG] plugin.terraform-provider-aws_v2.40.0_x4: 2019/12/09 11:23:04 [INFO] Attempting to use session-derived credentials
[2019-12-09T11:24:40.837Z] .task" is waiting for "module.app.var.name"
[2019-12-09T11:25:07.327Z] 2019-12-09T11:25:06.710Z [DEBUG] plugin.terraform-provider-aws_v2.40.0_x4: 2019/12/09 11:25:06 [INFO] Successfully derived credentials from session
[2019-12-09T11:25:07.327Z] 2019-12-09T11:25:06.710Z [DEBUG] plugin.terraform-provider-aws_v2.40.0_x4: 2019/12/09 11:25:06 [INFO] AWS Auth provider used: "AssumeRoleProvider"
[2019-12-09T11:25:07.327Z] 2019-12-09T11:25:06.711Z [DEBUG] plugin.terraform-provider-aws_v2.40.0_x4: 2019/12/09 11:25:06 [DEBUG] Trying to get account information via sts:GetCallerIdentity
[

Adds 2 minutes:

[2019-12-09T11:25:18.604Z] 2019-12-09T11:25:18.530Z [DEBUG] plugin.terraform-provider-aws_v2.40.0_x4: 2019/12/09 11:25:18 [INFO] Attempting to use session-derived credentials
[2019-12-09T11:25:45.077Z] roup_ids"
[2019-12-09T11:26:41.227Z] aws_security_group.main" is waiting for "module.app.var.tags"
[2019-12-09T11:27:27.824Z] 2019-12-09T11:27:21.924Z [DEBUG] plugin.terraform-provider-aws_v2.40.0_x4: 2019/12/09 11:27:21 [INFO] Successfully derived credentials from session

Update:

I went through: v2.38.0...v2.39.0 and can pin-point the following commit to have caused the slow-down:
b8ee7e6 - e.g. the upgrade of aws-sdk from 1.25.37 to 1.25.38

Seems like it is related to the following change: aws/aws-sdk-go#2958

There are already bugs reported upstream:

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Dec 9, 2019
@lifeofguenter lifeofguenter changed the title Regression: massive slowdown on planning since 2.40 Regression: massive slowdown on planning since 2.39 Dec 10, 2019
@justinretzolk
Copy link
Member

Hey @lifeofguenter 👋 Thank you for taking the time to file this issue. Given that there's been a number of AWS provider releases since you initially filed it, can you confirm whether you're still experiencing this behavior?

@justinretzolk justinretzolk added waiting-response Maintainers are waiting on response from community or contributor. and removed needs-triage Waiting for first response or review from a maintainer. labels Nov 18, 2021
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 Nov 24, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Old or inactive issues managed by automation, if no further action taken these will get closed. waiting-response Maintainers are waiting on response from community or contributor.
Projects
None yet
Development

No branches or pull requests

2 participants