Skip to main content
NetApp Stage KB

PVC creation fails when using encryption in the Trident backend definition

Last Updated:

Applies to

  • NetApp Astra Trident 
  • NetApp ONTAP 9.x
  • Trident backend created with encryption enabled


When a PVC is submitted for creation, using a Trident backend which has been defined with encryption enabled, it fails with the error:

Normal   ProvisioningFailed    3s (x2 over 11s) encountered error(s) in creating the volume: [Failed to create volume pvc-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx on storage pool aggr1 from backend nas-backend: backend cannot satisfy create request for volume trident_pvc_yyyyyyyy_yyyy_yyyy_yyyy_yyyyyyyyyyyy: (ONTAP-NAS pool aggr1/aggr1; error creating volume trident_pvc_yyyyyyyy_yyyy_yyyy_yyyy_yyyyyyyyyyyy: API status: failed, Reason: Key manager is not configured on the cluster. Use the "security key-manager external enable" command to configure the external key manager or "security key-manager onboard enable" command to configure the Onboard Key Manager., Code: 13001)]


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.
Case Citation