Skip to main content
NetApp Stage KB

Migrating Trident volumes between storages looses the PVC to PV information on import

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

 

 

Applies to

  • Trident for Kubernetes
  • Trident for Openshift
  • Openshift 3.11 or higher
  • Kubernetes 1.11 or higher

Issue

When exporting the PVC from the original nas-economy PV, and using that PVC YAML unchanged to import the mirrored volume as a PV, the PVC connection is lost, which will subsequently leave the PV Pending and unusable for the pod.

 

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.

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Reference
    Confidence
    Validated
    Flag
    Not Flagged
    Governance
    Experience
    KCS Enabled
    Yes
    Visibility
    Public
  2. Tags
    This page has no tags.