One of the HA node consistently fails to startup when trying to turn on the Working Environment from BlueXP
Applies to
Issue
- After shutting down both HA nodes, an issue was encountered when attempting to start up by turning on the Working Environment from BlueXP.
- One of the nodes in the HA configuration is consistently not started, the following error message is displayed in the working environment:
Degraded - Show Details
The HA cluster is not highly available.
Node instance xxxx-vm2 is in the 'stopped' state.
- When checking the
DEBUG-AZURE.LOG
in autosupport, it appears that the VM machine state of the first node is stuck in "InProgress" and never completes.
2023-09-28 03:34:22,521 UTC DEBUG [Start Vsa ] [xxxxxxxxx-xxx-xxx-yyyy-xxxxxxxxx] [ yyyyyy ] [xxxxxxx] (azure-identity-akka.actor.default-dispatcher-3518) [azure:34] [Response] AzureResponse(200,Map(Date -> Buffer(Thu, 28 Sep 2023 03:34:22 GMT), Pragma -> Buffer(no-cache), Expires -> Buffer(-1), X-Cache -> Buffer(CONFIG_NOCACHE), Retry-After -> Buffer(10), Content-Type -> Buffer(application/json; charset=utf-8), X-MSEdge-Ref -> Buffer(Ref A: xxxxxxx Ref B: xxxxxxxxx Ref C: 2023-09-28T03:34:22Z), Cache-Control -> Buffer(no-cache), Content-Length -> Buffer(141), x-ms-request-id -> Buffer(xxxxxxxxx-xxx-xxxx-xxx-xxxxxxxxx), X-Content-Type-Options -> Buffer(nosniff), x-ms-routing-request-id -> Buffer(KOREACENTRAL:xxxxxx:xxxxxxxxx-xxx-xxx-xxxx-xxxxxxxxx), Strict-Transport-Security -> Buffer(max-age=31536000; includeSubDomains), x-ms-correlation-request-id -> Buffer(xxxxxxxxx-xxx-xxx-xxx-xxxxxxxxx), x-ms-ratelimit-remaining-resource -> Buffer(Microsoft.Compute/GetOperation3Min;14998,Microsoft.Compute/GetOperation30Min;29763), x-ms-ratelimit-remaining-subscription-reads -> Buffer(11999)),{
"operationId": "xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx",
"startTime": "2023-09-28T03:34:22.2634849+00:00",
"status": "InProgress"