Closed holgpar closed 2 months ago
The adjustment we made was for the CREATE, UPDATE and DELETE operations which explains why the error occurs now during the READ.
[-parallelism=n](https://developer.hashicorp.com/terraform/cli/commands/plan#parallelism-n)
)? The adjustment we made was for the CREATE, UPDATE and DELETE operations which explains why the error occurs now during the READ.
yeah, that figures.
Did you make any changes with respect to the parallelism.
Nope, did not touch that.
Is it canary or live landscape?
It happens on live landscapes (but we also have much more regions on live landscapes).
Attempts to reproduce the error on prod landscape with identical set of entitlements as well as leveraging the module sap-btp-entitlements:
terramate
orchestrating the Terraform CLI -> no errorterramate
orchestrating the OpenTofu CLI -> no error terramate
orchestrating the Terraform CLI -> no error (link)terramate
orchestrating the OpenTofu CLI -> no error (link)For reference see: https://github.com/lechnerc77/tf-btp-loadtest
Update: Parallel execution of apply and destroy with same setup in region eu10 -> the destroy has 10 parallel reads on the entitlements. Execution was successful see https://github.com/lechnerc77/tf-btp-loadtest/actions/runs/10843825292
Update: Parallel execution of apply and destroy with same setup in region AP10 -> the destroy has 10 parallel reads on the entitlements. Execution was successful see https://github.com/lechnerc77/tf-btp-loadtest/actions/runs/10850499262
@holgpar we had the ver 1.7.0 of Terraform provider for BTP released yesterday which contains the fix
Is there an existing issue for this?
What version of the Terraform provider are you using?
1.6.0
What version of the Terraform CLI are you using?
tofu v1.7.2
What type of issue are you facing
bug report
Describe the bug
We still see failing plan commands with outputs like this from time to time:
I think this is unexpected, because there was a recent change in the provider to add some retry logic.
Expected Behavior
Rate Limits are handled by the provider via back-off and retrying.
Steps To Reproduce
Execute a "plan" against a subaccount with a configuration containing about 20 entitlements. We currently execute three such plans in parallel.
User's Role Collections
No response
Add screenshots to help explain your problem
No response
Additional context
No response