Skip to main content
NetApp Knowledge Base

Importing a storage volume with a replacement PVC fails in Trident as Bad Request

  1. Last updated
  2. Save as PDF
Views:
469
Visibility:
Public
Votes:
1
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

Trident for Kubernetes or Openshift

Issue

When trying to change the definition of the Persistent Volume Claim (PVC) for existing Persistent Volumes (PVs) in Trident, the import command fails with:
Error: could not import volume: frontend failed to import volume:
PV <PV_NAME> already exists for volume <VOLUME> (400 Bad Request)
command terminated with exit code 1

 

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.