Skip to main content
NetApp Knowledge Base

One of the HA node consistently fails to startup when trying to turn on the Working Environment from BlueXP

Views:
40
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
bluexp
Last Updated:

Applies to

Cloud Volumes ONTAP(CVO) for Azure

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"

Note:
Enabling verbose API logging allows for the recording of API call events.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.