Skip to main content
NetApp Knowledge Base

Azure CVO becomes inaccessible after root storage account keys rotation from Azure portal

  1. Last updated
  2. Save as PDF
Views:
14
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • NetApp Console
  • Cloud Volumes ONTAP (CVO)
  • Microsoft Azure

Issue

  • After rotating the access keys for the root storage account directly from the Azure portal, the CVO cluster becomes inaccessible. ONTAP is stuck in a boot loop and below errors are seen on the serial console of both CVO VM's in Azure : 
    [xxxxxxxx:osc.signatureMismatch:error]: Object-store LIST operation server-calculated request signature does not match the signature sent to object-store server xxxxxxxxx.blob.core.windows.net for bucket or container "xxxxxxxx" on node xxxxxxxxxxxxxxxxxxxxxxxx. Check the keys and signing method.
    [xxxxxxxx:pha.obj.scanFailure:error]: ONTAP could not get a list of objects from the object store, "xxxxxxxx", at "xxxxxxxxx.blob.core.windows.net", using IP address "xxx.xxx.xx.xxx" with error: Server failed to authenticate the request.
    [xxxxxxxx:config.noPartnerDisks:error]: No disks were detected for the partner; this node cannot perform takeover correctly.
  • The CVO cluster is in a failed state in NetApp Console.

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.