-
Notifications
You must be signed in to change notification settings - Fork 671
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
Issue when trying to provision a new ibm_container_alb_cert #2067
Comments
ibmcloud ks alb certs -c buvlsclf0qcur3hjcrng
ibmcloud ks alb cert get -c buvlsclf0qcur3hjcrng --secret-name ingress-tls-cert
|
@ifs-pauljegouic As discussed on slack from last 2 days the customer is seeing an issue while provisioning a secret. The same code was working earlier. As a workaroud we tried to increase the retry call on the GET API even if we get an 404 response code. We are working on this fix ..We will update once the fix is availble in release |
Workaround observed on the provisionning. BUT now, error on the deletion. ➜ debug terraform state list Error: unexpected state 'deleting', wanted target 'deleted'. last error: %!s() |
➜ debug terraform version
Terraform v0.12.26
+ provider.ibm v1.16.0 |
@ifs-pauljegouic Can you please share me the complete log does the error was thrown out after 10s
|
Here is the successfull log from our end
|
Sure I have just reproduced. Collecting the DEBUG logs right now. @hkantare: does you ALB cert resources previsouly existed before the taint ? |
|
NB: the destroy actually works after a failure like this. Because the secret does not exist anymore (even after the error). Looks like the state provided by IKS is not handled |
fixed (much more a workaround, but as discussed) with 1.16.1 thanks team & @hkantare |
Hello,
Here is the issue i randomly encountered since yesterday night (sometimes it works sometimes not sometimes the secret is provisioned sometimes not and so sometimes tfstate is not synchronized with resources). When resources creation fail, the resource is present in tfstate with status tainted but can not be tainted as creation fail)
Terraform Version
terraform : 0.12.26
ibm tf provider : 1.14.0
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
Expected Behavior
The ibm_container_alb_cert should have been provisionned correctly
Actual Behavior
The ibm_container_alb_cert is not provisionned or provisionned after the crash error and the terraform state file contain a ressource marked as tainted (even if not provisionned)
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply -auto-approve
The text was updated successfully, but these errors were encountered: