Skip to main content
NetApp Knowledge Base

PVC Resize and Provisioning Operations Hang After Upgrade to Trident 26.02

  1. Last updated
  2. Save as PDF
Views:
30
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
cloud
Last Updated:

Applies to

  • NetApp Trident 26.02 (specifically with iSCSI ONTAP SAN backend)
  • OpenShift 4.x clusters (e.g., 4.18.34)
  • Environments using Trident for dynamic PVC provisioning and expansion

Issue

After upgrading to Trident 26.02, the following symptoms occur:

  • All PersistentVolumeClaim (PVC) resize operations hang, remaining in FileSystemResizePending or similar states.

  • Provisioning new PVCs from clones/templates (especially >100GB) fails, with PVCs stuck in Pending or PrepClaimInProgress.

  • Related pods (e.g., CDI prep pods) get stuck in ContainerCreating.

  • Trident node logs show repeated errors such as:

    Unable to expand volume devicePath=/dev/dm-29 error="rpc error: code=Internal desc=failed to remediate paths for LUN7; paths missing for LUN7; current paths: [...] ; expected portals: [...]"

  • Additional log entries may include:

    Retried locked snapshot delete, clone split timer not yet expired.

    and

    GRPC error: rpc error: code=Internal desc=failed to remediate paths for LUNx; paths missing for LUNx; current paths: [...] ; expected portals: [...]

  • Attempts to resize existing PVCs result in conditions stuck at FileSystemResizePending  with events like:

    Warning  ExternalExpanding  volume_expand  waiting for an external controller to expand this PVC

  • The issue begins immediately after upgrading Trident and affects production workloads.

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.