Skip to main content
NetApp Knowledge Base

Azure CVO's object store is unavailable after upgrading storage account from GPv1 to GPv2

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

Applies to

  • Microsoft Azure
  • Cloud Volumes ONTAP (CVO)

Issue

  • After upgrading the Azure storage account from GPv1 to GPv2, the Cloud Volumes ONTAP (CVO) cluster cannot connect to the object store .
  • All aggregates on the CVO show that object store is unavailable.

EMS logs : 
 Wed Jul 29 06:47:55 +0000 [CVO-01: wafl_junkd_exempt: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "StorageAccount" from node xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxx. Reason: Unknown provider error code.

sktrace logs :
2026-07-28T14:12:38Z [3:0] OSC_ERR: logDebugHeader:531 CmdId 52, Provider Error Code is 403, Op HEAD, x-ms-id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
2026-07-28T14:12:38Z [3:0] OSC_ERR: logCmd:371 HEAD CmdId 52 obj-name: failed with OSC error: Access denied

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.