Skip to main content
NetApp Knowledge Base

Trident Backend Fails on Azure Government Cloud: NoValidSubscriptionsInQueryRequest

  1. Last updated
  2. Save as PDF
Views:
7
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Trident
  • Azure NetApp Files (ANF) backend
  • Deployments in Microsoft Azure US Government Cloud
  • Kubernetes clusters using Trident for storage provisioning

Issue

  • When deploying a Trident backend for Azure NetAppFiles (ANF) in the Azure US Government Cloud, backend creation fails with thefollowing error:

Failed to create backend: problem initializing storagedriver 'azure-netapp-files': error initializing azure-netapp-files SDK client.POST https://management.azure.com/providers/Microsoft.ResourceGraph/resources

Backend creation fails with NoValidSubscriptionsInQueryRequest despite correct environment settings in the Trident BackendConfig.

  • Observed Behavior:
    • Trident attempts to connect to the commercial Azure endpoint (management.azure.com) instead of the required US Gov endpoint (management.usgovcloudapi.net).
    • The backend configuration includes environment: AzureUSGovernment, but this does not take effect.
    • Trident backend creation is unsuccessful, blocking ANF provisioning in the GovCloud region.

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.