#504 gateway time out - Terraform

1 messages · Page 1 of 1 (latest)

novel axle
#

Hi Team, I am deploying a CVO using Terraform in GCP, Deployment and deletion is successful but getting this below error.
"504 gateway time out from Azure application gateway"
approximately after 12 mins of deployment, however the cluster is getting created. We get 504/ongoingasyncoperation exception error while destroying the cluster but it gets deleted completely from the console.

<html>

  <head>

          <title>504 Gateway Time-out</title>

  </head>

  <body>

         <center>

                <h1>504 Gateway Time-out</h1>

         </center>

         <hr>

         <center>Microsoft-Azure-Application-Gateway/v2</center>

  </body>

</html>

Please find the terraform provider that we are using.

terraform {
required_providers {
netapp-cloudmanager = {
source = "NetApp/netapp-cloudmanager"
version = "23.7.0"
}
}
}

fickle cobalt
#

"504 gateway time out from Azure application gateway" is not part of resource cvo GCP in the BlueXP/cloudmanager provider. Maybe something with your other Azure related resource?

novel axle
#

@fickle cobalt Thank you for the reply.
We are not using any Azure-related resources. All the systems are in GCP. When we check the BlueXP timeline we can see the CVO deployment is successful and we can see in the GCP as well the CVO is deployed. However, in Terraform, we see 504 errors. I suspect the BlueXP does not seem to send the completed signal back to Terraform in a timely fashion, hence the timeout?

Can we add a timeout temporarily to verify the API to return safely and see whether it’s a timing issue or not?

Is there a way we can check if the customer is using the Azure resource and causing the "504 gateway time out from Azure application gateway" error?

fickle cobalt
#
  1. Is it intermittent issue?
  2. Do you use terraform enterprise/cloud or local?
  3. Can you turn on the debug flag and share the log? TF_LOG="DEBUG" terraform apply
    There are some retries added already. Since there are a couple interactions, we would like to know where the issue happened. The debug log will help us to understand this.
novel axle