-
Notifications
You must be signed in to change notification settings - Fork 677
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
Error finding VLAN order: couldn't find resource (21 retries) #2613
Comments
@martinohansen Can you please share us the complete log ....We are not able to reproduce from our end
With below sample configuration
|
Interesting, here is the complete log. |
Can you please try to run this from a brower url and share us the outpur We should see someoutput like below (id will be different)
|
That works:
|
Also, this might be relevant. I tried importing the state after Terraform failed and the VLAN order went through. The subsequently apply has this diff:
So it seems the VLAN gets created but is missing the tag and name. |
When we googled we found simialr issues opend Similarly increased NotFoundChecks but not sure will it fix the issue from your end since we are not able to replicate it Can you please try with the latest release v1.25.0 |
Looks like 10m wasn't enough in the first run, but a 2nd run finished within ~3 minutes. Not sure what we can expect from the backend here, but I'm gonna play a little more with it to see how often it fails.
Thanks for pushing a version so quickly 🙏 Edit: it took 15 min for the first VLAN to get approved. |
FYI I just tested another deployment, it took 82 minutes for the VLAN to get approved and during that period the API call returned an empty response. It was order #79096162 and #79095256. |
@martinohansen May be can you raise ticket on softlayerAPI why are the provisioning taking too long |
Will do 🙏 Update: ticket number CS2311670 |
Could we make the timeout adjustable by the consumer at runtime? |
yes we have customizable timeout user can define in templates (https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/resource_instance#timeouts)
|
But they don't change the |
Yes those timeout can't change the NotFoundChecks...we are still looking into the code how can we control these NOtFoundChecks..Meanwhile did you get any update from Classic Infrastructure team why it takes around 80 mins for vlan approval |
Ticket is still in-progress, no real reply yet. |
Community Note
Terraform CLI and Terraform IBM Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Expected Behavior
We would expect the resource to get created within an adjustable timeout.
Actual Behavior
The resource never get created and the timeout/retries for it are not adjustable. I've tried adjusting the following timeout and retries:
IBMCLOUD_TIMEOUT=300 IAAS_CLASSIC_TIMEOUT=300 MAX_RETRIES=30
Using the IBM Cloud CLI i can indeed replicate the behavior,
Steps to Reproduce
Execute
terraform apply
with the aboveibm_network_vlan
resource.The text was updated successfully, but these errors were encountered: