...

API call can be reissued once the service comes backup and application termination should complete

Cluster provider creation with CLM restarting

In this case, cluster provider creation fails followed by logical cloud and deployment intent instantiation failure:

Post "http://172.16.16.150:30461/v2/cluster-providers": dial tcp 172.16.16.150:30461: connect: connection refused
Apply: cluster-providers Error: Post "http://172.16.16.150:30461/v2/cluster-providers": dial tcp 172.16.16.150:30461: connect: connection refused

logical cloud and deployment intent instantiation returns code 500

POST --> URL: http://172.16.16.150:30477/v2/projects/gmsproj1/logical-clouds/default/instantiate
Response Code: 500
Response: The server encountered an internal error and was unable to complete your request.

 POST --> URL: http://172.16.16.150:30477/v2/projects/gmsproj1/logical-clouds/default/instantiate
Response Code: 500
Response: The server encountered an internal error and was unable to complete your request.

Once the CLM comes backup, reissue the provider, cluster, logical cloud, DIG instantiation calls and the application instantiation should complete