You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2022. It is now read-only.
If an HTTP 503 "server is temporarily unable to service your request" error occurs during database creation the provider immediately treats the error as failure event and tries to destory the instance, but the destroy fails as the instance is still actually provisioning.
The provider/sdk should tolerate multiple retries for 503 errors (e.g. max 10) to allow for transitive communication errors during provisioning.
2018-03-11T18:57:59.591Z [DEBUG] plugin.terraform-provider-oraclepaas: go-oracle-terraform: Service Instance is being created
2018-03-11T18:57:59.591Z [DEBUG] plugin.terraform-provider-oraclepaas: go-oracle-terraform: Waiting 60 seconds for service instance to be ready (1560/3600s)
oraclepaas_database_service_instance.database: Still creating... (26m31s elapsed)
oraclepaas_database_service_instance.database: Still creating... (26m41s elapsed)
oraclepaas_database_service_instance.database: Still creating... (26m51s elapsed)
oraclepaas_database_service_instance.database: Still creating... (27m1s elapsed)
oraclepaas_database_service_instance.database: Still creating... (27m11s elapsed)
oraclepaas_database_service_instance.database: Still creating... (27m21s elapsed)
2018-03-11T18:58:59.595Z [DEBUG] plugin.terraform-provider-oraclepaas: go-oracle-terraform: HTTP GET Req (/paas/service/dbcs/api/v1.1/instances/ptstest/my-terraformed-database-test3)
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: go-oracle-terraform: Encountered HTTP (503) Error: <HTML><HEAD>
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: <TITLE>Service Unavailable - Fail to connect</TITLE>
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: </HEAD><BODY>
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: <H1>Service Unavailable</H1>
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: The server is temporarily unable to service your request. Please try again
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: later.<P>
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: Reference #6.e7d3e743.1520794739.158609ad
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: </BODY></HTML>
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: go-oracle-terraform: 1/1 retries left
2018-03-11T18:58:59.833Z [DEBUG] plugin.terraform-provider-oraclepaas: go-oracle-terraform: HTTP DELETE Req (/paas/service/dbcs/api/v1.1/instances/ptstest/my-terraformed-database-test3)
2018-03-11T18:59:00.547Z [DEBUG] plugin.terraform-provider-oraclepaas: go-oracle-terraform: Encountered HTTP (409) Error: {"reason":"Resource Busy. Service ptstest\/my-terraformed-database-test3 has active jobs. active job: 22678492 when attempting to process request: ptstest\/my-terraformed-database-test3: serviceType = dbaas, namespace = dbaas, operation = delete-dbaas-service"}
2018-03-11T18:59:00.547Z [DEBUG] plugin.terraform-provider-oraclepaas: go-oracle-terraform: 1/1 retries left
2018-03-11T18:59:00.547Z [DEBUG] plugin.terraform-provider-oraclepaas: Error during delete, waiting 30s: Error on delete (409): {"reason":"Resource Busy. Service ptstest\/my-terraformed-database-test3 has active jobs. active job: 22678492 when attempting to process request: ptstest\/my-terraformed-database-test3: serviceType = dbaas, namespace = dbaas, operation = delete-dbaas-service"}
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If an
HTTP 503
"server is temporarily unable to service your request" error occurs during database creation the provider immediately treats the error as failure event and tries to destory the instance, but the destroy fails as the instance is still actually provisioning.The provider/sdk should tolerate multiple retries for 503 errors (e.g. max 10) to allow for transitive communication errors during provisioning.
The text was updated successfully, but these errors were encountered: