Skip to main content
NetApp Knowledge Base

PARTNER DOWN TAKEOVER IMPOSSIBLE Due to Delayed VM Status API 405 Error

  1. Last updated
  2. Save as PDF
Views:
16
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
not set
Last Updated:

Applies to

  • NetApp Cloud Volumes ONTAP (CVO) in Microsoft Azure
  • ONTAP version 9.16.1P7 and later
  • High Availability (HA) configurations
  • Environments using NetApp Console Agent (BlueXP/Connector) for VM lifecycle management

Issue

After a scheduled or manual power-on of a Cloud Volumes ONTAP (CVO) HA pair in Azure using the NetApp Console Agent, one VM (node) boots immediately, but the second VM does not start until 20–25 minutes later. During this delay, ONTAP reports a critical HA alert:

CLTFLT: HA Group Notification from <node>-01 (PARTNER DOWN, TAKEOVER IMPOSSIBLE) EMERGENCY
Log output:

BlueXP/Connector logs show the first VM’s status as “in progress” for an extended period, delaying the start of the second VM.
Azure API call to check VM operation status returns:
405 Azure Front Door was unable to process the request. Method Not Allowed - It looks like the method you're using is not allowed.

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.