CSE cluster status in "Error" state after Cloud Director cell service crash

Products

• VMware Cloud Director

Issue/Introduction

• CSE cluster status is in "Error" state after Cloud Director cell services crash.
• Cloud director services are restored however CSE cluster does not recover and remains in "Error" state.

Environment

VMware Cloud Director 10.x

Cause

CSE clusters went in error status due to Cloud Director Cell services crash and did not recover once the Cloud Director services were restored.

Resolution

To resolve this issue, update the cluster status via API using Postman or any other REST API client:

1. Perform a GET on the URL  https://{{VCD_URL}}/cloudapi/1.0.0/entities/{{ENTITY_ID}} . Note down the response JSON body and the value for the response header "ETag" .
   
   Note: Replace 'Entity_ID' with affected cluster's ID.
   
   
2. In the response body, update the value for the field `entity.status.vcdKe.state` from "error" to "provisioned"
   
   
3. Use the updated response body to perform a PUT on the URL https://{{VCD_URL}}/cloudapi/1.0.0/entities/{{ENTITY_ID}} . Please make sure to set the request header "If-Match" to the "ETag" value from Step.1.

The PUT request from Step.3 might fail with the status code 412 and with a message saying that the ETag did not match. In such a case, retry again from Step.1.
Please do not update just the ETag in the PUT request if you hit 412. Please retry steps 1 & 2 to update BOTH the request body and the "If-Match" header for the PUT request.

Once the PUT request returns a 200 response status code, the UI should show that the cluster status is "Available" .

Additional Information

Get Defined Entity